Charles Plessy
01/28/2025, 1:54 AMlast/mafconvert module, which I already use in my pipeline, can do MAF to SAM, and of course the samtools/view module can convert SAM to CRAM.
The problem is that if the MAF file takes too much space, the SAM file will too. (I am talking about multiple GB per file, which can add up to TB when the pipeline runs on a sample list of a hundred of entries). Therefore I wrote a local module that uses a sequera container where both LAST and samtools are installed, and that module basically does maf-convert sam foo.maf | samtools view -CT genome.fasta -o foo.cram.
My questions are:
⢠is there an interest for that module to be added to nf-core instead of being local,
⢠if yes, would last/mafcram be appropriate even if it does not use the same container?
⢠also, since adding samtools to the LAST container only increases size by ~5%, would it be fine to just add it to all the last/* submodules so that #pairgenomealign does not have to download two very similar containers, which would be a 100% increase, or can this be configured within the pipeline?Nicolas Vannieuwkerke
01/28/2025, 8:35 AMlast/mafconvert module and add samtools to it š. That way we don't have many similar modules doing basically the same thingNicolas Vannieuwkerke
01/28/2025, 8:35 AMlast module though since only one actually uses itCharles Plessy
01/28/2025, 8:39 AMCharles Plessy
01/28/2025, 8:39 AMmodules/nfcore via configuration ? This way I would be able to make the other last modules reuse the last+samtools container of last/mafconvert in #pairgenomealign if we go that direction.Nicolas Vannieuwkerke
01/28/2025, 8:41 AMcontainer configuration option per process to set the container: https://www.nextflow.io/docs/latest/process.html#directives