Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing output file(s) error when centroiding data #86

Closed
plashmore opened this issue Mar 19, 2024 · 3 comments
Closed

Missing output file(s) error when centroiding data #86

plashmore opened this issue Mar 19, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@plashmore
Copy link

plashmore commented Mar 19, 2024

Description of the bug

After centroiding first data file the workflow gives an error and stops, saying it can't find the centroided data file it just created.

It appears that changing line 48 in modules.config to be

ext.prefix = { " ${meta.id}.centroided " }

fixes the issue. The workflow appears to create a new centroided file with the original filename.mzML instead of filename.centroided.mzML which is what the workflow looks for in future steps

Command used and terminal output

No response

Relevant files

No response

System information

Nextflow version: 23.10.01
Metaboigniter version: 2.0.0
Hardware: Desktop
Executor: Local
Container Engine: Docker
OS: Linux (Fedora 39)

@plashmore plashmore added the bug Something isn't working label Mar 19, 2024
@plashmore
Copy link
Author

the above fix broke later steps in the pipeline, the proper fix was to change lin 14 of openms_peakpickerhires.nf to be

tuple val(meta), path("output/*.mzML"), emit: mzml

instead of the original

tuple val(meta), path("output/*.centroided.mzML"), emit: mzml

this both fixes the error during centroiding as well as prevents errors further down the pipeline without any adjustments to the modules.config file

@PayamEmami
Copy link
Contributor

Thanks for the report. Fixing now.

@PayamEmami
Copy link
Contributor

It has now been resolved.

@PayamEmami PayamEmami mentioned this issue Apr 12, 2024
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants