You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 15, 2022. It is now read-only.
I was using guppy basecaller Version 5.0.11+2b6dbffa5, and trying to remap the basecalled sequence to the reference, I can roughly get a mapping with the Move matrix provided by Guppy, but I found that the length provided by the move matrix is not the exact same as the signal length.
For example this read, the move matrix has a length L_M 6965
And the signal length has a length L_S 76153
I was using the rna_r9.4.1_70bps_hac.cfg, according to the document, the stride is 10.
I was expecting the L_S = 10 * L_M, however, this is not the case here as 76153 / 6965 ~ 10.9
So I think guppy may chopping the adapter and polyA tail here, so does that mean the move matrix is aligned with the signal at the tail.
Where I may find this information in the fast5 file?
Thanks
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was using guppy basecaller Version 5.0.11+2b6dbffa5, and trying to remap the basecalled sequence to the reference, I can roughly get a mapping with the Move matrix provided by Guppy, but I found that the length provided by the move matrix is not the exact same as the signal length.
For example this read, the move matrix has a length L_M 6965
And the signal length has a length L_S 76153
I was using the rna_r9.4.1_70bps_hac.cfg, according to the document, the stride is 10.
I was expecting the L_S = 10 * L_M, however, this is not the case here as 76153 / 6965 ~ 10.9
So I think guppy may chopping the adapter and polyA tail here, so does that mean the move matrix is aligned with the signal at the tail.
Where I may find this information in the fast5 file?
Thanks
The text was updated successfully, but these errors were encountered: