Closed istvankleijn closed 6 months ago
I suppose it would also be nice if the report were generated on-the-fly rather than only at completion
Thanks for reporting this @istvankleijn, it is our intention that reports are generated on the fly, it looks like our dynamic reporting may not be working. We'll take a look at this for the next release.
Just to say that this seems to be fixed in v1.1.7, thanks! The final report includes all the data and the report is updated after each alignment process. There is no reporting on-the-fly during basecalling itself, so for the last few hours of the workflow running, the GPU is idle while alignment and reporting occurs. This way I can start a second iteration of wf-basecalling if I need to without the two iterations interfering with each other on the GPU, so I hope this is intentional :)
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
wf-basecalling v1.1.5
Workflow Execution
EPI2ME Desktop application
EPI2ME Version
EPI2ME V5.1.9
CLI command run
No response
Workflow Execution - CLI Execution Profile
None
What happened?
At completion of the workflow, the basecalling report only shows the results from the first chunk of reads (100k reads from 25 files of 4000 reads each). These are not very representative for the whole experiment, because initial fast basecalling was performed during sequencing and the first chunk consists of failed reads only.
I would expect to see the read quality and read length histograms for all reads when the workflow finishes. I suppose it would also be nice if the report were generated on-the-fly rather than only at completion.
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