You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When poor quality data are used as input into nf-core/funcscan, the initial annotation step might not return a single annotation but produce an empty FastA file. Currently, the workflow attempts to profile this empty FastA file in the subsequent workflows, leading to a failure of a task. After the whole pipeline has finished, there is an overview of the execution of the pipeline and it will list the number of failed tasks. However, from this report it is not apparent that it failed because there were no input data available from the start.
It would be great, if either
a) there is a test after the annotation step that discards such samples and doesn't attempt to profile them
or
b) provides a more informative error message that indicates that the tasks failed due to insufficient input data.
The text was updated successfully, but these errors were encountered:
Description of feature
When poor quality data are used as input into nf-core/funcscan, the initial annotation step might not return a single annotation but produce an empty FastA file. Currently, the workflow attempts to profile this empty FastA file in the subsequent workflows, leading to a failure of a task. After the whole pipeline has finished, there is an overview of the execution of the pipeline and it will list the number of failed tasks. However, from this report it is not apparent that it failed because there were no input data available from the start.
It would be great, if either
a) there is a test after the annotation step that discards such samples and doesn't attempt to profile them
or
b) provides a more informative error message that indicates that the tasks failed due to insufficient input data.
The text was updated successfully, but these errors were encountered: