-
Notifications
You must be signed in to change notification settings - Fork 27
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
model.fit hangs indefinitely #18
Comments
Hi there - Sorry for the delayed response. I wonder if your compute is running out of memory? We will shortly release a GPU version which should solve this too. |
I was running it on my laptop with only 16 gb of memory so might have been a memory issue. Do you have a sense for how much memory is recommended, or how memory usage scales with the size of the input dataset? |
Having the same problem....I was running it on lab sever with 200G memory with 17K cells. Any idea about how I could proceed? |
Thank you for the amazing tool! I'm excited to implement seacells in my workflow; however, I'm experiencing the same problem with 30k cells on the HPC cluster with 184 GB. |
This is a bit curious, as we were able to run 120k cells on a cluster with 200GB of memory, so memory-wise, you should be fine. It may be slow to run, though - 75k cells took 18 hours and 50k cells took 8 hours in our updated benchmarks. How long did you let the process run before killing it? |
That makes sense, thank you! I let it run for an hour before killing it since it did not complete a single iteration. I did not expect it to take 8+ hours. I'll submit the job again while supplying more time. Thank you! |
Gotcha - yes sorry it only prints every 10 iterations or so, which might be confusing! Let me know if it still does not work. A GPU sped up version is in the works to ease some of the runtime! |
That's amazing! I look forward to the GPU version. |
Hello @sitarapersad, I hope you are having a great day and thank you for the interesting tool! I submitted a job to compute ATAC seacells for my dataset of 30k cells. However, it has not completed the 10 iterations mark after 3 days on the HPC cluster. I supplied the job with 300 GB and 10 cores. Would you recommend I kill the job, increase the resources, or potentially wait for the GPU version to be released? There is 1 day and 21 hours left on the job. This is unexpected, especially since it took you 18 hours for 75k cells. Below is the output so far from the job.
Script:
|
Hi Sayyam! I think this is likely because there are too many SEACells. We recommend about 1 SEACell for every 100 cells, so for your dataset, something on the order of 300 SEACells (rather than 10k). At 10k it'll be very slow and the result will likely still be too sparse to gain robust states. |
Hello! That makes sense! Thank you. I'll try that! In #22, it was recommended to compute RNA metacells using the ATAC seacells. May you please explain the reasoning behind the recommendation since, according to my understanding, it is harder to identify robust cell states in ATAC because of the sparsity? I'm thinking of computing the ATAC seacells and then the RNA seacells using SEACells.genescores.prepare_multiome_anndata. From there, I'll feed both modalities into scenic+ to identify TFs. |
Hello, currently I have a very large single-cell RNA dataset with more than 5 million cells. I tested the seacell pipeline on some of the data and found that as other comments said, the running speed is very slow. We expect to use seacell to find the optimal metacell to reduce the amount of data in the entire project, but the time spent in this step cannot be estimated at present. I noticed that the GPU version is already available? How does the running speed compare to the cpu version? Or do you have a recommended workflow for such a large dataset? Thanks again for the excellent work you do. |
HI,
I was able to run this tutorial on the provided sample data. However, I am running into problems when using my own dataset (~58k cells and ~30k genes). Here is my SEACells code:
It hangs up after completing iteration 1 for several hours, and eventually I killed it. #7 references model.fit taking too long but this seems like a different issue. Please let me know if you have any insights!
The text was updated successfully, but these errors were encountered: