Emrah Kırdök
06/04/2026, 1:10 PM--binning_map_mode own to calculate ancient DNA damage parameters
• Now I would like to use binning_map_mode all parameter and resume the pipeline to get cross sample depths.
• The question is: Will the pipeline redo all the binning steps? Sometimes pipeline redo some of the steps and I don't want to change the current results
Thanks for your replies.James Fellows Yates
06/04/2026, 1:12 PMall will break assumptions with pyDamage and give you dodgy damage statistics.James Fellows Yates
06/04/2026, 1:19 PMEmrah Kırdök
06/04/2026, 1:28 PM--binning_map_mode all just to get cross sample depths, I am sure ancient DNA parameters will fail.
But I still don't understand why pipeline redo the binning steps? I thought binning only works for sample-wise assembly. So you assemble one sample or group (let's say sample1), and align only reads from sample1 to the contigs assembled from sample1.
Is there a way to get cross sample depth without re-triggering binning step using the pipeline?James Fellows Yates
06/04/2026, 1:38 PMall myself), but it's about the way Nextflow handles cache invalidation.
From a Nextflow point of view: binning map mode tells the Nextflow how to generate the depth files. If you now say 'align reads from all samples' against the contigs', this will change the depth file itself because it follows a different route in an if_else statement (can send the palce in the code if you're interested). The depth file is then sent to a binner. Nextflow will go 'ok this input file is not the same as the one I had the first time I ran this binner, therefore the original results are no longer valid, and I need to regenerate them'.
Note that Nextflow's -resume is rather mysterious , so ti's my conservative prediction taht it will resume - you could try anyway and hope it doesn't re-do the binning if it successfully finished the first time around.James Fellows Yates
06/04/2026, 1:39 PMEmrah Kırdök
06/04/2026, 4:57 PMJames Fellows Yates
06/04/2026, 5:22 PMEmrah Kırdök
06/04/2026, 8:05 PM