Skip to content

Expose all parameters from individual tools in somatem #116

@ppreshant

Description

@ppreshant

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

  • Decide between these 2 organizations of the parameters
    • Have all parameters in one place for ease of access and understanding
    • Have current/key ones in the nextflow.config and put the rest of the parameters in a new parameters.config file. reduces clutter for those setting the pipeline manually?

Plan

  1. Setup the organization for the parameters.
    • (Start with a detailed_params.config file) Decide on a config file structure for major vs minor parameters.
    • make a scheme to translate tool's param into somatem's such as tool_param
  2. Work one module at a time to add all parameters included in the underlying tool to a config file.
    • Copy and load the README.md files from the omi-web-app repo to get help from AI.
    • Cut and paste the parameters into a parameters/tool.md file so we can organize it in omi-web-app at the same time!
  3. Wire it up to the tool's ext.arg in modules.config
  4. Test by running stub and checking log?
  5. Fix old parameters that don't abide by the naming convention: tool_param

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions