Pass in parameter in scientific notation without parameter validation failure

When I pass in a parameter on the CLI in scientific notation, I get the error “expected type: Number, found: String (1e-4)”

Is there a way to pass in a number in scientific notation and have parameter validation correctly identify the type?

For now you can set NXF_DISABLE_PARAMS_TYPE_DETECTION to true:

https://nextflow.io/docs/latest/reference/env-vars.html#nextflow-settings

In the future we will replace the current type casting with something more robust based on the parameter schema, to avoid issues like this one.

thanks! Does setting NXF_DISABLE_PARAMS_TYPE_DETECTION to true result in any less strict parameter validation? Or does it have no bad side effects?