-
Notifications
You must be signed in to change notification settings - Fork 22
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
Error: scheduled core X did not deliver a result #160
Comments
I tried running it with one core and it's still crashing, after being blocked for a few hours on
The command I ran:
From |
Thanks for reporting this. This shouldn't be happening unless you have extremely high coverage in those cells. If you share the input with me via email I can take a look |
I took a look. Please upgrade your numbat version to 1.3.2 or use the more recent docker image; I get more informative error message this way:
Notably:
|
Hi! I am running numbat using singularity, with 4 cores (128Gb each) on a <500 cells dataset, and it seems to be stuck at
Retesting CNVs..
for hours, then it throws an error:recycle_columns()
seems to be a problem with cores not communicating, I don't know aboutvctrs::vec_locate_matches
Any idea on how to solve this?
And how to improve speed in general? It's a small dataset so I guess it should be able to run on one core worst-case, but is it supposed to take >10 hours?
The text was updated successfully, but these errors were encountered: