-
Notifications
You must be signed in to change notification settings - Fork 6
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
GraffiTE stops at the tsd_prep step when bypassing SV discovery #31
Comments
Hello @SarahBailey1998, I'm sorry about the issue. It looks like it may be similar to this (related to your machine /tmp dir configuration). The first thing to try would be this. However if you think this is not the case, please send us the complete log, as well as the Nextflow process logs for the repeatmasker prosess. These should be located in Let me know! Clément |
It also happened to me in the past when RepeatMasker ran out of memory and was killed, leaving an empty annotation and therefore no input for the TSD steps. |
Hi, Thanks for your help. I have updated the singularity options and added more memory to the run but still get an error. I tried using 64 GB, would that be enough? Here are the logs from repeatmask_VCF:
.command.out:
|
Yes in your case, your singularity is not configured correctly:
Try unsetting SINGULARITYENV_TMPDIR
Also, please post your |
Thanks! I tried those suggestions and still get an error so I'm waiting on some help from our HPC team about the configuration problem. Here's my nextflow.config:
|
Hello @SarahBailey1998, Was your HPC team able to solve the issue? Thanks! Clément |
Hi,
I'm trying to run GraffiTE in the mode that bypasses the SV calling steps but it seems to get stuck at the tsd_prep step. I was wondering if you had any idea why?
I'm using a vcf file from Sniffles2. But we also saw the same error with a vcf from SVIM-asm.
My reads.csv contains:
The commands I tried:
The text was updated successfully, but these errors were encountered: