You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem in existing functionality or a lack thereof? Please describe.
Filtering some amplicon schemes is tricky - for example an MPX scheme that does 1-2 and 5-7 kb amplicons - our approach at the moment does not allow for anything other than hard setting the minimum and maximum at 1kb and 7kb and allowing chimeras to sneak through the middle.
Describe the solution you'd like.
Paired coordinates - [(1000,3000), (5000,7000)] would allow anything between the two numbers in the tuple, with a structure of
[(Start, stop), (Start, Stop)]
It's also possible we may want to do something along the lines of Exclusion regions - something like
[(-3000, -5000)], where the minus signifies it's exclusionary?
Additional context
We may want to make this set able in a model per task - we will see. That's a bit more involved
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem in existing functionality or a lack thereof? Please describe.
Filtering some amplicon schemes is tricky - for example an MPX scheme that does 1-2 and 5-7 kb amplicons - our approach at the moment does not allow for anything other than hard setting the minimum and maximum at 1kb and 7kb and allowing chimeras to sneak through the middle.
Describe the solution you'd like.
Paired coordinates -
[(1000,3000), (5000,7000)]
would allow anything between the two numbers in the tuple, with a structure ofIt's also possible we may want to do something along the lines of Exclusion regions - something like
Additional context
We may want to make this set able in a model per task - we will see. That's a bit more involved
The text was updated successfully, but these errors were encountered: