-
Notifications
You must be signed in to change notification settings - Fork 11
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
findEncodingDims Out-of-Memory Issues #40
Comments
Hi Laurenz, sorry for the late reply, can you tell us the number of genes and samples in your |
Dear @vyepez88, We have a total of 38 samples in our ods_Filtered object and around 350 000 "genes". The genes are actually intronic regions as we are currently collaborating with a lab of the Netherlands that used OUTRider to detect aberrant usage of introns and exons as well. Kind regards, |
I am currently not sure how our algorithm scales with samples and genes. @vyepez88 how much memory do you need for a similar amount of counts? What is the largest we fitted an how much memory did it require? You could try running:
with the Afterwards you could try to fit OUTRIDER for the optimal dimension. Let us know if that worked! |
Dear Laurenz, |
Dear Laurenz, |
Dear Gagneur Lab,
I'm currently trying to determine the optimal q-value for my OutRider analysis. For which I'm using the following code:
However, each time I submit this code on our HPC cluster, the node appears to go out-of-memory right at the end of the optimisation. I've tried with 50, 150 and even 715 GB of Ram. Do you by any chance have an idea what could be going wrong? I've also looked into the solutions mentioned under #11.
Kind regards,
Laurenz De Cock
The text was updated successfully, but these errors were encountered: