Charles Plessy
09/04/2024, 1:51 AM--input is mandatory and expects a samplesheet, but when the pipeline is used for just a single sample, it is inconvenient to have to write a samplesheet. I can think of two workarounds:
• make --input optional and create an alternative arguments that takes a data file directly. Drawback: users can now crash the pipeline by forgetting to provide either --input or its alternative.
• let --input accept other file formats than csv . Drawback: deviates from the nf-core template and makes the pipeline harder to maintain.
Any thoughts?Phil Ewels
09/04/2024, 3:53 AMPhil Ewels
09/04/2024, 3:54 AMPhil Ewels
09/04/2024, 3:55 AMCharles Plessy
09/04/2024, 5:16 AM--input is the most straightforward for the user. This is for the #C06TRU74N4D pipeline when the users have just one pair to analyse; in that case the metadata can be hardcoded to target and query (for the input) and I can have optional parameters like --targetName and --queryName to pass the metadata IDs in case the user wants (as they are used to construct output file names).Phil Ewels
09/04/2024, 6:58 AMPhil Ewels
09/04/2024, 6:58 AMPhil Ewels
09/04/2024, 6:58 AM