Increase job time for FastQC and Fastq screen #59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves issue where slurm job for FastQC would be cancelled due to time limit. I increased the time for fastq screen as well, since these jobs also takes longer with larger data sizes.
It would be more optimal to have a solution like nf-core pipelines have, where processes failing with this error code are re-run with incrementally increasing compute resources. I do however see no reason to implement this in this pipeline, since the long-term plan is to use switch to the nf-core/seqinspector.