Closed Andreas-Bio closed 3 months ago
Hi @Andreas-Bio!
Thanks for raising this; looks like the error occurs when all reads are in the same direction. The issue should be fixed in the next release. Once it has been published, I will come back to this thread and ask you to confirm that the fix indeed solved your problem. Thanks for your patience!
Hi @Andreas-Bio, I could reproduce the issue with FASTQ data containing only reads from the same strand. I'm somewhat confused as to how this happened in your case though. Would you mind sharing the raw FASTQ you used when you encountered the error? Thanks!
Hi @Andreas-Bio, with v1.1.2 the workflow no longer fails if all reads come from the same strand. Please re-open this issue if this does not fix the problem. Thanks!
Operating System
Windows 10
Other Linux
No response
Workflow Version
wf-amplicon v1.1.0
Workflow Execution
EPI2ME Desktop (Local)
Other workflow execution
No response
EPI2ME Version
v5.1.14
CLI command run
No response
Workflow Execution - CLI Execution Profile
standard (default)
What happened?
The error message is too cryptic. I dont know where to start with the debugging. "Process
pipeline:deNovoPipeline_spoa:spoa (1)
terminated with an error exit status (1)" report.html.txtCan you please provide me with some ideas where to start?
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response