[seqfan] Re: Policy on near-duplicates
peter.luschny at googlemail.com
Mon May 4 22:21:15 CEST 2009
Max Alekseyev wrote:
> I support this idea, assuming that the main entry in an "equivalence
> class" of near-duplicates is clearly indicated.
> I think that all information that is applicable to every sequence in
> the class should be concentrated in the main entry only (that would
> simplify editing/updating/extending this information in a single
> Ideally, the other (non-main) entries in each class should be kept
> minimalistic and marked with the "dead" or "dupe" keyword (indicating
> that they are permanent in their current form) - since their purpose
> is only referencing to the main entry.
So what is it good for then? This occurs to me as
a waste of time and space.
The only place an adaption is necessary is in the
search-algorithm which must be able to give the
correct answer in both cases.
This, however, necessitates a small change only in the
already very powerful search-algorithm implemented
(as far as I can judge from the outside).
More information about the SeqFan