-
Notifications
You must be signed in to change notification settings - Fork 720
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
Helpful error message when strandedness cannot be infered #1390
Comments
I experienced the same error, for the first time after many successful runs. The error message, |
I just faced this problem as well while using the workflow. I checked the code and found that there is a variabled called
|
Ahh, thanks for flagging this everyone. I'll push a fix ASAP. |
Addressed in #1405 |
Description of feature
When running the rnaseq workflow wit the
infer_strandedness
step, it came to my attention that when neither thestranded_threshold
nor theunstranded_threshold
is reached, the workflow aborts with the following error message:This is because of the following code snippet in
rnaseq/subworkflows/nf-core/fastq_qc_trim_filter_setstrandedness/main.nf
:If neither threshold is reached, the strandedness variable isn't initialized, leading to the workflow crashing. I think a more helpful error message would be great here, or maybe even a standard value of the
strandedness
variable to prevent the workflow from crashing?PS: Not sure if this is a bug or a feature request.
The text was updated successfully, but these errors were encountered: