-
Notifications
You must be signed in to change notification settings - Fork 9
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
Some enhancements! #1
Comments
|
|
We should also make the Summary outputs include the actual codons at each position, since L and I (?) have two possible codons and that can very possibly make a difference in activity. (Or, if we don't use the 22c trick, it would be more critical.) |
Moved the 3rd issue here to a new stand-alone issue (#3). |
Closing for next round of updates. |
First off just reiterating this is so amazing. I love it.
Okay down to business, in order of decreasing priority/increasing complexity:
In the README, be more specific about how the reverse RefSeq is literally just as easy as it sounds (the 5' to 3' direction of the gene itself). I can make this change, just putting it here for reference.
Output a third file in Summary, which is just the stats for the max in each well. (Easy code, can do it after, but also would be nice to just have.) Then if >95%, feel confident. If lower, check on a case-by-case basis if acceptable or meaningful.
Add more automation in the sequence generation for the RefSeq.csv file. For example, if doing a single plate, allow passing 'all' in the well position, which would specify applying the ref sequences for all wells in a plate (A–H, 1–12). Or pass a list of plates if doing more than one.
Let the parser read zipped files. (This may be as simple as just changing the function used for reading... https://stackoverflow.com/questions/12902540/read-from-a-gzip-file-in-python. It also might not...)
The text was updated successfully, but these errors were encountered: