-
Notifications
You must be signed in to change notification settings - Fork 4
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
pysam output issue #199
Comments
Interesting. Can you try running each step of longbow individually to see where exactly the error is happening (you can specify the output to go to a file rather than stdout)? That will help get to the bottom of this. Also, were you running this on a local disk or a distributed filesystem (e.g. nfs)? As for speed, right now it does take a while to run. You can try running with an explicit number of threads set ( |
It's running on local disk. Based on my troubleshooting below, it occurs when piping the input into either longbow filter or longbow extract. Thank you! Annotate alone works:
filter alone works:
Piping annotate into filter fails:
segment alone works:
Piping filter into segment works:
Piping segment into extract fails:
Extract alone works:
|
I think I see what is happening, the issue is here. The type of stdin is not I thought we had fixed this type of thing recently but perhaps introduced a different bug instead. |
Ah...I was mistaken in terms of what was broken. The thing that changed is that we now try to read the model before we start processing the file, and this causes a problem when The simple fix right now is to pass the model again to each command, e.g.
But obviously this is kind of clunky. The better fix is to go back to the old ordering, which will take a little bit of work but should be doable. |
There seems to be some issue in the 0.6.12 related to pysam, I've copied the output of the small test below. The same issue was observed both in the docker version and when building from source.
The 0.5.37 version on PyPI is working. Also curious what processing rates to expect? I'm seeing ~12reads/sec rate on a 64 core 256Gb machine. Thanks!
The text was updated successfully, but these errors were encountered: