-
Notifications
You must be signed in to change notification settings - Fork 41
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
Compatibility with dorado summary #65
Comments
I'm having the same problem (and get the error message #66 received) when using a dorado-derived summary file (attached). It looks like maybe there were plans to eliminate the num_events_template in issue #51 ? Thanks much for any help on how to use this w dorado summary files. -Matt (base) xxxxx-MacBook-Pro-3:~ xxxxx$ Rscript MinIONQC.R -i /Library/MinKNOW/data/duplex_splitduplex_summary.txt -o /Library/MinKNOW/data/QC-Reports-simplex
Execution halted |
I'm realizing that it works if I add in a num_events_template column filled with zeroes... |
Hi there, I am having problems when trying to run minion_qc 1.4.2 with the sequencing summary generated by dorado (with the dorado summary command).
Normally, when the basecall is performed at sequencing time in the device, it returns a sequencing summary that works fine with minion_qc, having the following columns:
Nonetheless, when I perform the basecall after the sequencing in my own computer, the sequencing summary file I get from the
dorado summary
command contains a lower number of columns:A dorado user already asked about these differences here, but the dorado team said that they do not plan to implement the summary in a way that matches the sequencer output.
My question is if it would be possible to manipulate the sequencing summary returned by
dorado summary
to input it to minion_qc. I can try to create an script to do it, but I would need to know what are the columns required by minion_qc, as I do not know if all the information required by minion_qc can be extracted from that summary file.Thanks beforehand,
Fran
The text was updated successfully, but these errors were encountered: