[Bioperl-l] Bug? Features with similar ranges, different IDs are considered overlapping
cjfields at illinois.edu
Thu Aug 19 11:56:11 EDT 2010
On Aug 17, 2010, at 7:45 AM, Scott Cain wrote:
> Hi Dave and Chris,
> It seems to me that the genomic comparison is the thing people would do more often, so if you're going to create a flag, the default should be for the genomic comparison and if somebody is doing the protein space comparison and not getting the the expected results, they'll probably read the docs to find out why.
> Scott Cain, Ph. D.
> scott at scottcain dot net
> Ontario Institute for Cancer Research
> 216 392 3087
> Snet from my iPhone.
> On Aug 17, 2010, at 5:06 AM, Dave Messina <David.Messina at sbc.su.se> wrote:
>>> Good point; it's probably the context the methods are used that matters. So, maybe just a document clarification?
>> That's always good, but it really doesn't solve the issue you're describing.
>> I mean, who would expect to get overlaps for features on different chromosomes?
>> To me, that's a clear violation of reasonable user expectations. You shouldn't have to read the docs about something like that.
>> So what's the solution for these duelling use cases? I haven't thought about it much, but a first approximation might be to add a -genomic boolean flag that, when true, would do the right thing and check the ID when doing overlaps or other positional comparisons.
>> (Maybe -genomic is too obscure. Maybe it should be -same_id_for_overlaps or something like that.)
>> And maybe having to know to set a flag is effectively the same thing as having to read the docs to understand SeqFeature's overlap behavior.
>> What do the rest of you out there think?
>> Bioperl-l mailing list
>> Bioperl-l at lists.open-bio.org
> Bioperl-l mailing list
> Bioperl-l at lists.open-bio.org
More information about the Bioperl-l