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
r10 branch nanopolish train Error: unknown model: #761
Comments
oooooooooooh, and that seemed to work. James |
Yes, that is the right format for the model, not the .inl file.
Jared
… On Apr 14, 2020, at 5:29 AM, James Ferguson ***@***.***> wrote:
oooooooooooh,
I used ~/nanopolish/etc/r9-models/r9.4_450bps.nucleotide.6mer.template.model
and that seemed to work.
Is that what I "should" be using for this?
James
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
And that, after a while, resulted in this
|
Is that in the first round, or after a few iterations? |
Hmm, not sure. |
Yea, dumped again.
Looks like at the same point too. Maybe it's a bad read? or maybe something else. |
If you make a bam with just that read, can you trigger the assertion right
away?
…On Tue, Apr 14, 2020 at 9:55 PM James Ferguson ***@***.***> wrote:
Yea, dumped again.
Inferring read 08138292-7d7e-4b51-a7bc-b14c2a9f527f chr7:51438571-51441928 0
nanopolish: src/nanopolish_raw_loader.inl:495: int EventBandedMatrix<StorageType>::get_offset_for_kmer_in_band(size_t, int) const [with StorageType = SimpleHMMFBStorage; size_t = long unsigned int]: Assertion `band_idx < this->band_origins.size()' failed.
Aborted (core dumped)
Looks like at the same point too. Maybe it's a bad read? or maybe
something else.
Should I remove that read and try again?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#761 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAC7DH6VCZE6I7MHEZYBNVTRMUHYZANCNFSM4MHSNWEA>
.
|
Yep, dies. Then I ran with 1 thread, but otherwise the same.
Here is the fastq and bam of the reads I ran. let me know if I need to extract the fast5 files for you |
Hi @jts I was asked to have a look into this by @Psy-Fer and it seems that the assertion is caused by get_by_event_kmer(event_idx + 1, start_trim_kmer_state + 1) at nanopolish/src/nanopolish_raw_loader.inl Line 813 in c248609
get_by_event_kmer(event_idx + 1, start_trim_kmer_state + 1) calls event_kmer_to_band(event_idx + 1, start_trim_kmer_state + 1) and this resultant band index gets equal to band_origins.size() triggering the assertion. It seems to be something to do with the band offset being off by 1 or something, but without actually knowing the context I couldn't be sure. Does it ring a bell to you? Anyway, given that the reads that trigger this assertion is rare, I just hacked to skip such reads as https://github.com/hasindu2008/nanopolish-arm/blob/995dafe291582e8a13497e57acef750be47d8c43/src/nanopolish_raw_loader.inl#L837-L842 for now. Hope it does not introduce errors to the final training result. Also, I grabbed the fast5s for Jame's extracted dataset. The zip file containing all the necessary files to reproduce the bu is attached. You may quickly replicate the problem by running the following inside the extracted folder. |
Hello Jared,
I'm running this to try and train a positive control (then a negative)
I've tried changing the
--input-model-filename
tor9.4_450bps
as well, but same error.Is there something i'm doing wrong?
Also, any help with the steps to build a methylation model to use with
nanopolish call-methylation
usingnanopolish train
would be appreciated.Cheers,
James
The text was updated successfully, but these errors were encountered: