[Treebase-guts] [ treebase-Bugs-2783200 ] Merge Algorithm classes

[SourceForge.net <no...@so...>]

Bugs item #2783200, was opened at 2009-04-28 16:59
Message generated for change (Tracker Item Submitted) made by mjdominus
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=2783200&group_id=248804

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Mark Dominus (mjdominus)
Assigned to: Nobody/Anonymous (nobody)
Summary: Merge Algorithm classes

Initial Comment:
Algorithm is an abstract class from which ParsimonyAlgorithm, DistanceAlgorithm, LikelihoodAlgorithm, and OtherAlgorithm are derived.  ParsimonyAlgorithm uses three other classes (GapMode, UserType, and PolyTCount) that are not used anywhere else.

These should be merged into a single class with a flag and some sort of associated string data; the GapMode, UserType, and PolyTCount tables should be eliminated.

Regarding this design, Jin Ruan, the original designer, says:

(04:48:42 PM) Jin Ruan: The algorithm design is not well reviewed. What is there was the first pass I had to model different algorithms into the system. The reason for different subclasses was to enable more interactions/relationships between generated trees with a particular algorithm. However we never actually design/ implment any use case to use that design in treebase2. That is why we have this first pass design but it is largely not used. Please feel free to redesign it. For example, as a starting point using a string instead of different subclasses. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126676&aid=2783200&group_id=248804