We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While running some tests with the SEPP placements in Qiita we noticed that the current code rewrites the placements as:
plcmnts['placements'].extend([{'p': placement, 'nm': [[sequence, 1]]} for sequence, placement in placements.items()])
which is currently not supported by bp so we had to rewrite them as:
bp
plcmnts['placements'].extend([{'p': placement, 'n': [sequence, ]} for sequence, placement in placements.items()])
Thus, wondering if this is enough or if there is any reason why bp should support both.
cc: @sjanssen2; BTW the current version can add all the Qiita 150bp deblur fragments into the GG/SEPP backbone in < 3.5hrs and ~200Gb.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While running some tests with the SEPP placements in Qiita we noticed that the current code rewrites the placements as:
which is currently not supported by
bp
so we had to rewrite them as:Thus, wondering if this is enough or if there is any reason why
bp
should support both.cc: @sjanssen2; BTW the current version can add all the Qiita 150bp deblur fragments into the GG/SEPP backbone in < 3.5hrs and ~200Gb.
The text was updated successfully, but these errors were encountered: