-
Notifications
You must be signed in to change notification settings - Fork 85
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
DNA-mapping pipeline gets stuck at origFASTQ rule when using a custom cluster config yaml #887
Comments
Hi Tobi, I'll have a look if I can reproduce this. Best wishes, Katarzyna |
Hi Katarzyna, yes, when I start the pipeline with the following command it works: Only when using the cluster config yaml as stated above the pipeline gets stuck. Thanks for looking into this! Best |
Hi Tobi, thanks for submitting the issue. Indeed, I can reproduce it. Best, Katarzyna |
Hi Tobi, as an update, I will attempt to circumvent this and other slurm-related issues in snakePipes by implementing native slurm support available in more recent snakemake versions. This is now pending, as I need the IT to solve an issue related to the slurm folder on the package partition. Best, Katarzyna |
Using the following command, I tried running the DNA-mapping pipeline using a customized cluster config yaml to circumvent issues with one node on our server:
DNA-mapping --DAG --trim --trimmerOptions '-a nexteraF=CTGTCTCTTATA -A nexteraR=CTGTCTCTTATA' --dedup --mapq 2 -j 20 -i ./fastq/ -o ./mapping/ hg38 --clusterConfigFile custom-cluster-config.yaml
Apparently, the pipeline always got stuck at the execution of the first rules (origFASTQ1 and origFASTQ2), no matter what name I gave the custom config yaml and no matter what output folder I assigned. This was not the case when using the default cluster configuration.
Also, when I start the pipeline with the default and interrupt after the origFASTQ folder and its contents are created, I can restart with the custom config and it finishes.
Custom cluster config:
Edit: formatting
The text was updated successfully, but these errors were encountered: