-
Notifications
You must be signed in to change notification settings - Fork 7
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
debugging "Error: Error during trajectory inference" #132
Comments
Hi @celinesin Sorry for the late reply, I was on holidays. Do you get the same type of error with other TI methods? It's a bit bizarre that This might also be a running out of memory issue. Does the memory usage spike when running the method? |
Hi @zouter, Thanks for your reply! I get the same error with ti_slice(), ti_monocle_ddrtree(), and ti_comp1(). Ah, running out of memory could be the culprit, since it's inside the Docker? How can I check this? Thanks again! |
Hello! Just an update, in case someone else runs into the same problem. I'm using MacOS Mojave. First, to check if i was running out of memory:
To increase the memory, I followed this: Now, I have a new error to follow :)
|
OK, another update: I now have a new error:
|
Hey Celine! Is there no more output than this, even when verbose is TRUE? Could you provide a minimum reproducible example? This reminds me of a problem that I thought I had fixed a long time ago.. I will try to remember what it was again. |
I'm having trouble running dynwrap::infer_trajectory() on my data.
My installation seems to be okay, the methods work fine on the toy data.
However, on my data (and verbose=TRUE), I get a lot of package loading messages and:
As my data was running as expected through Monocle in the past, I followed
https://github.com/dynverse/ti_monocle_ddrtree/blob/master/run.R
line by line, and everything runs up to line 79.
Do you have any tips on how I can debug this? (I tried several other ti_ methods as well, with similar results)
Thanks for this really cool package!
The text was updated successfully, but these errors were encountered: