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
Hi,
I am currently working on using bookend together with flair to generate transcriptomes of multiple samples and I am having a weird issue. For some samples, my bookend assemblies are way smaller than for other assemblies (around 100 KB instead of like 9 MB in other samples). What would be the reason for this, when the elrs are of similar size and no different parameters were chosen between the different samples? A quick reply would be appreciated
The text was updated successfully, but these errors were encountered:
hacaoe
changed the title
Hi,
Small size of certain samples assemblies
Apr 27, 2022
The difference in assembly sizes could have a variety of causes. Could you share the arguments you are using for assembly, as well as an example of an ELR file that produced a large vs. a small assembly?
It may be worthwhile to re-run ELR generation and assembly using the new major release version 1.0.1. You can see the release notes here, but I identified a number of bugs that were causing reads/assemblies to be lost, and I have corrected them in this release. You can either install from source code here or pip3 install bookend-rna --upgrade if you installed through pip.
Unfortunately multi-threading is not currently implemented, so Bookend utilities can only run on one core at the moment. This is on my to-do list to implement.
Hi,
I am currently working on using bookend together with flair to generate transcriptomes of multiple samples and I am having a weird issue. For some samples, my bookend assemblies are way smaller than for other assemblies (around 100 KB instead of like 9 MB in other samples). What would be the reason for this, when the elrs are of similar size and no different parameters were chosen between the different samples? A quick reply would be appreciated
The text was updated successfully, but these errors were encountered: