Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the assignment of multiple quantification window coordinates #38
Fix the assignment of multiple quantification window coordinates #38
Changes from 13 commits
8b6d273
fa6848f
b3760bb
0ffd2cb
eac72d7
8a5f50d
7db87e0
3f00008
baf7561
e6b74ce
35c27da
59085a0
737db80
2938e81
70dc8d1
4b7745e
2246c1c
cc66985
f243d85
ffc8c32
9756e4a
298d3b1
5fc20ff
9ecd7f7
b847559
d21feb5
174b6c7
ffb31ce
85c28b0
6ce79b5
481333e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this be addressed in the PR? Or would it be better addressed in a separate PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PS, what would Uncle Bob think of this comment? ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left this as a reminder. It worked! haha
So, this touches on a key issue: QWC's are (supposedly) 1-indexed. All of these changes assume that downstream calculations correctly utilize 1-index-based coordinates as input by the user, i.e. the user inputs
'1-5' --> include_idxs == [1, 2, 3, 4, 5]
. The test cases verify that these indexes are selected correctly.So, I think the only necessary change to get the last char in the sequence would be to append one more index onto s1inds before we slice it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think technically they should be 0-indexed (but a value of 0 will disable the filter).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per the documentation "Indexes are 0-based, meaning that the first nucleotide is position 0." Thanks @kclem. So, there is no last bp bug.
However, including 0 in the qwc throws a
BadParameterException
, I'm assuming because 0 disables the filter. Should we keep this behavior as is?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbowcut2 I think it should behave such that if you have
-qwc 0-10_15-22,0
the first amplicon will have quantification windows0-10
and15-22
and then the second amplicon will have the quantification windo coordinates disabled (and therefore be set by where the sgRNA aligns).Also,
-qwc 0
will outright disable it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Colelyman okay, it works now.