Closed mantczakaus closed 1 year ago
There are certain shared filesystems that seem to have inconsistent files timestamps, this is screwing up the caching invalidation of nextflow.
You could try to set the following parameter in conf/process.config
around https://github.com/icbi-lab/nextNEOpi/blob/aac260dbd5da701d22a09846045f3f42981cd4a1/conf/process.config#L10
// default caching
cache='lenient'
Let me know if this works
Setting cache to lenient worked - it now uses over 500 tasks from the cache instead of 15 - thank you!
resolved by 3f34b81da8c155e9b0f905a95aaca9c06710bb4b
Hi, I was wondering if there is anything that could be done to improve Nextflow's -resume functionality in the pipeline. I have resumed a run that failed on pVACseq but still the pipeline went all the way back to SplitIntervals, make_uBAM and Bwa. It used cached tasks only for some quality control processes and HLA typing (see below). Happy to provide more details if necessary. Best wishes, Magda