fixes sample fastq output bug in cellranger mkfastq

[julicudini]

PR checklist

Closes #6189

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[atrigila]

Hi @julicudini , thank you for this PR. Some checks are not passing, but this is due to the nf-test snapshot of mkfastq not being updated. Could you run nf-core modules test --update? Thank you :)

[apeltzer]

Would also be good to output the Undetermined in a separate channel, similar to what bcl2fastq/bclconvert do at the moment - that way would behave more consistently :)

[nschcolnicov]

I was working on the PR for the same changes at the same time and missed the notifications on this one. I have already been testing the module on my PR with a new version of demultiplex that handles these changes, so it would make things simpler for me if we can merge this one #6194. And @julicudini you can address the changes for the other cellranger modules on this PR

[SPPearce]

@julicudini , are you still working on this?

[apeltzer]

I think this was fixed in #6194 already

[SPPearce]

I think this was fixed in #6194 already

I think the comment chain above is suggesting there are other modules that need adjusting in a similar manner, that weren't done in #6194.

[apeltzer]

Fair point, lets wait for @julicudini