Context:
Currently, we only implement a few (maybe important ones?) parameters for starters, but we want to provide the users with all parameters so that omi can help users set them with full flexibility.
Example
lemur has only these subset of parameters currently in nextflow.config
// LEMUR-MAGNET
lemur_db = "${params.db_base_dir}/lemur_221_db/"
lemur_db_zenodo_id = 10802546
lemur_taxonomy = "${params.lemur_db}/taxonomy.tsv"
rank = "species"
and modules.config
withName: 'LEMUR' {
ext.args = [
"--rank ${params.rank}",
// "--db-prefix ${params.lemur_db}", // using db-prefix directory as input
"--tax-path ${params.lemur_taxonomy}",
].join(' ') // Join converts the list here to a string.
}
And we need to include many more to make it comprehensive!
Questions
Plan
- Setup the organization for the parameters.
- Work one module at a time to add all parameters included in the underlying tool to a
config file.
- Wire it up to the tool's
ext.arg in modules.config
- Test by running stub and checking log?
- Fix old parameters that don't abide by the naming convention:
tool_param
Context:
Currently, we only implement a few (maybe important ones?) parameters for starters, but we want to provide the users with all parameters so that omi can help users set them with full flexibility.
Example
lemurhas only these subset of parameters currently innextflow.configand
modules.configAnd we need to include many more to make it comprehensive!
Questions
nextflow.configand put the rest of the parameters in a newparameters.configfile. reduces clutter for those setting the pipeline manually?Plan
Decide on a config file structure for major vs minor parameters.tool_paramconfigfile.parameters/tool.mdfile so we can organize it in omi-web-app at the same time!ext.arginmodules.configtool_param