Krešimir Beštak's new feature: markersheet columns can be in any order

[RobJY]

Co-authored-by: Krešimir Beštak [email protected]

Markersheet columns can be in any order.

Nice idea to grab the schema and make a map. Thanks!

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• Make sure your code lints (nf-core pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

Working through these remaining checklist tasks

Maybe we should use the same idea for the samplesheets?

[nf-core-bot]

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

[RobJY]

Hi @kbestak, when I started putting together this PR I was able to reproduce the error you mentioned, but that's no longer the case. Could you please provide a sample and marker sheet pair that cause the error when run on the dev branch?
@jmuhlich has pointed out that the updated nf-validation code should be able to handle any order for the input sheet columns and this seem to be working well. Maybe there was another issue causing the error you saw that has since been corrected?
Thanks for your help with this.

[kbestak]

This looks good regarding the marker sheet definition and backsub validation. I'm not entirely sure which error you're referencing to, if it's the default segmentation running on only ASHLAR outputs, that was fixed with the post_registation channel definition!