I'm in the process of adding the new release of SB...
# ampliseq
d
I'm in the process of adding the new release of SBDI-GTDB and GTDB and when I try to run the standard test case but with phyloplacement and skipping qiime, I get the below error. I've merged upstream
dev
, so it seems something crept in during the recent PRs.
Copy code
$ nextflow run . -resume --outdir results -profile docker,test --dada_ref_taxonomy sbdi-gtdb --run_pplace --skip_qiime
[...]

ERROR ~ Validation of pipeline parameters failed!

 -- Check '.nextflow.log' file for details
The following invalid input values have been detected:

* --run_pplace (true): Value is [string] but should be [boolean]
* --skip_qiime (true): Value is [string] but should be [boolean]
I will circumvent this for the time being, but will try to have a look as soon as I can unless someone knows what might have occurred and can point to what needs fixing/can provide a fix. (I tried the
--run_pplace true
syntax too -- same effect.)
d
I could imagine it has something to do with the template update or the nextflow version. I can confirm the issue with a fresh pull of dev with
NXF_VER=26.04.1 nextflow run ampliseq -resume --outdir results -profile test,singularity --dada_ref_taxonomy sbdi-gtdb --run_pplace --skip_qiime
, same with
NXF_VER=26.04.0
, using
NXF_VER=25.10.4
works however. So it appears to be the nextflow version.
I did have the impression that the pipeline worked at a certain point with 26.04.0 though. Will need to investigate (soon).
d
After I posted I also got the hunch that it might be Nextflow 26. You got to testing that before me. I will also do some testing and then maybe ask at the Nextflow Slack.
In a way the pipeline still works, it's just that you can't give boolean params on the command line.
We probably have enough for a post at the Nextflow Slack already. I can do that
I got the same error with 2.17.0, so it seems to be something with the new Nextflow version.
We got a quick reply: https://nextflow.slack.com/archives/C02T98A23U7/p1779350155196399?thread_ts=1779349529.646639&cid=C02T98A23U7. In summary, we need to upgrade nf-schema to 2.7.2. That would perhaps be best to do in a separate PR? (I'm not working so much until Tuesday, but can do it then if not today.)
d
I can open a PR to update nf-schema, parameter types can be added at a later stage I guess 😱