-
Notifications
You must be signed in to change notification settings - Fork 45
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
Visualising f5c resquiggle output in UNCALLED4 #51
Comments
This should be possible via the
This is more work than it should be, and soon I'll push an update which will allow you directly visualize an eventalign file. Stay tuned! |
I think I was unclear in my question. Sorry about that. Some time ago I managed to get f5c eventalign results to correctly be loaded. This is about f5c resquiggle. It is a recent module I added to f5c, to output alignment of the signal to the base called read (where as, eventalign outputs the alignment of signal to reference). The output format is a TSV, but slightly different: |
Ah yes, sorry I forgot resquiggle refered to aligning to the basecalled reads. That will take some reworking to handle reads not aligning to a common reference, but it does sound useful. I will work on it and let you know when I make progress |
Cool. Also, now are you supporting BAM move tables - is there an example of the steps for that? |
I do support BAM move tables now. You just need to run Guppy with the "--moves_out" and "--align_ref" options, merge the resulting BAM files with samtools, then input the merged bam file to "--bam-in" in the |
Primaries are enough for me. But loading takes so much time, are you still accessing the signal data from FAST5 when using this BAM method? Looks like most of the time is spent on IO (this is a promethION dataset on an NFS storage). |
Would it be possible to support f5c resquiggle output in UNCALLED4 visualisation? It would be quite useful for us to compare Guppy movetable-based alignment against the resquiggle?
The text was updated successfully, but these errors were encountered: