nf-core / nf-core/drugresponseeval
Boolean parameters don't work anymore
Open
Nobody has claimed this yet.
bug
- Dominant language
- Nextflow
- Stars
- 29
- Forks
- 11
- Avg merge
- 21h 44m
- Merged PRs (30d)
- 1
Description
Description of the bug
Boolean parameters don't work anymore because of new Nextflow
Command used and terminal output
nextflow run . -profile test_full --no_hyperparameter_tuning true --final_model_on_full_data
ERROR ~ Validation of pipeline parameters failed!
-- Check '.nextflow.log' file for details
The following invalid input values have been detected:
* --no_hyperparameter_tuning (true): Value is [string] but should be [boolean]
* --final_model_on_full_data (true): Value is [string] but should be [boolean]
Relevant files
No response
System information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with nextflow run . -profile test_full --no_hyperparameter_tuning true --final_model_on_full_data and inspect .nextflow.log for parameter validation details. Trace how these two parameters are declared and parsed, then verify the command accepts boolean values without validation errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100