-
Notifications
You must be signed in to change notification settings - Fork 2
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
runtime estimation #10
Comments
Update:
but the timing is very close with the start of another job on the same server, that was taking lots of memory. |
Update#2:
I wonder if the problem is due to the killed step above. |
Hi, As I just mentioned in a previous issue, it is a known issue that building the SR graph with PgSA is a blocking step for experiments on large dataset. This is mainly due to the fact the PgSA does not support parallel construction of the index. Replacing PgSA with a proper FM-index allowing parallel construction is on my TODOlist, but as I am currently writing my thesis, I can't promise you when it will be done. Another known issue it that BLASR does not support reference files (in this case, the LR file) larger than 4Go. You will thus have to split your LR file into multiple 4Go file, and run separate HG-CoLoR instances on each of them. This will not impact the results, as each LR is processed independently. However, I know that it is highly impractical to process this way, and investigating for a better aligner is also on my TODOlist. Moreover, you seem to be using a pretty old version of HG-CoLoR (still using GNU parallel). I do not maintain the conda versions myself, so I would recommand you to directly clone and compile the git repo if you can, in order to have the latest version. Best, |
Hi,
I am running HG-CoLoR on a local machine, and now it is running since about a week: is that normal?
It is using about 80 GB or RAM and 2 cores, the input files are 200 Gb (interlaced.fq) and 100 GB of ONT data. The genome is about 5.2 Gb, from a heterozygous plant.
I wonder if this long running time is acceptable or there is some issue going on and the computation is stuck.
Thanks
The text was updated successfully, but these errors were encountered: