-
Notifications
You must be signed in to change notification settings - Fork 18
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 in priorSum_m[, s]: incorrect number of dimensions #98
Comments
Offhand, no, I don't think I've seen this before. Did you try re-running it and see if it worked? Does it seem to be happening consistently for a given region? I often see weird errors driven by running out of memory in a multicore job but those error messages look different normally. Any chance that could be an issue here? |
Still not sure what caused this, but my guess is something to do with the container it ran in. |
Nope, I'm getting this error consistently for these data. Is there some kind of debugging information I can provide to help diagnose this? |
Hi, For debugging, please first show the I would also suggest
I am guessing there probably are NAs in |
@Zilong-Li here is the session info. In the meantime, I'm running it with a single core. Data's big, might take a while.
|
Can you re-try setting S=1, while S > 1 should be supported, perhaps there are some weird edge case going on? Maybe after that, can you re-try with the latest version of STITCH, just in case that fixes it? Since it crashed on iteration 4, and that is when the "shuffle haplotype" heuristic comes on, you might also want to change this |
When |
Okay. As Robbie said, the main focus is on S=1. Probably there are some edge case for S > 1. If you can send some data over, we may take a look at them |
The data I'm working with is quite large (380 samples). I'm not sure how I can feasibly share it. |
Apologies, I don't have a specific idea of why it's occuring. It's almost certainly some bug / edge case for S > 1 that doesn't occur for S = 1. If it's working for S = 1, I'd recommend that for now. S=1 is vastly better tested, S > 1 was more experimental, and while it can increase accuracy, it's generally of marginal to moderate importance. If you can remind me in a week or so I might have some time to come back and try to check / augment the tests and see if I can find anything. |
@rwdavies Hey, this is the reminder you requested. I should also note that I ran STITCH with S = 1 and received the same error:
|
Thanks. I'm very confused as to how this could throw an error. This code which contains
it's very hacky, but if you're willing, would you be able to add some print statements, then re-compile the code and re-run? For instance, you could replace the above with something like the below, or possibly even save priorSum_m in the loop before the error, and take a look afterwards
to re-compile STITCH hopefully this would work for you
|
Hello, I've been running stitch a bunch and this is the first time I'm seeing this particular error:
Is this something you have seen before?
For context, this is how STITCH was run:
The text was updated successfully, but these errors were encountered: