Bamt2fastq conversion has an non intuitive behavior:
- when reads are paired: it creates a temporary fast.gz which is actually a fastq uncompressed with both reads and then creates 2 fastq.gz with R1 and R2 separated
- when reads are single: it creates correctly a fastq.gz
Bamt2fastq conversion has an non intuitive behavior: