Skip to content
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

High proportion of "couldn't calibrate" for short RNA reads #953

Closed
kaltinel opened this issue Oct 27, 2021 · 10 comments
Closed

High proportion of "couldn't calibrate" for short RNA reads #953

kaltinel opened this issue Oct 27, 2021 · 10 comments

Comments

@kaltinel
Copy link

Hi,

I would like ask a question similar to issue #540.

I am having a very similar problem with my short RNA samples (they are 90 bp with polyA: so I am left with ~70 nt)

[post-run summary] total reads: 140905, unparseable: 0, qc fail: 0, could not calibrate: 135904, no alignment: 4986, bad fast5: 0

After nanopolish event-align scale-events, I am left with 18 reads..
I see that nanopolish has problems with calibrating and needs longer length: but then how do I ever work with my short length input?
Do I have to ligate them?
Should I use different parameters? Or a different tool you might suggest?

I would appreciate your comments!
Thank you.

@jts
Copy link
Owner

jts commented Oct 27, 2021

Unfortunately, these reads are too short for nanopolish currently. If possible ligating them would be a good thing to try.

Jared

@kaltinel
Copy link
Author

kaltinel commented Nov 1, 2021

Thank you for your reply.
May I ask, what would be the minimum length for nanopolish to work with direct RNA reads (1D + 1D2 )?
It would be a useful information for my ligation experiment.

@jts
Copy link
Owner

jts commented Nov 1, 2021

There isn't a hard threshold, I'd suggest at least 500bp but longer would be better (I think the typical length is about 1kb).

@kaltinel
Copy link
Author

kaltinel commented Nov 1, 2021

Hmm.. I use nanopolish for my 5S rRNA data which is ~120 bps, and it works okay..
Do you think these data would be faulty and I should not trust?

@jts
Copy link
Owner

jts commented Nov 1, 2021

I wouldn't say they are necessarily unreliable - if nanopolish was able to align and calibrate the signals the results are probably fine.

@kaltinel
Copy link
Author

kaltinel commented Nov 1, 2021

Thank you, I see.. And, do you have any suggestions for the maximum length?

@jts
Copy link
Owner

jts commented Nov 1, 2021

There's no maximum

@kaltinel
Copy link
Author

kaltinel commented Nov 1, 2021

Thanks for your reply.
However, I do not understand certain aspects..

I have my RNA data in various lengths, one set is 120 bp (5S), the other set is 2kb (18S) and the last one is 4.5kb (28S rRNA).
In my event align outputs, I can only see that 18S is aligned...
I have no alignments for others..

If 5S is too short, I don't understand what is the issue with 28S..

Can you elaborate on this please?

@jts
Copy link
Owner

jts commented Nov 17, 2021

Hi,

Sorry for the slow reply, Do you have reads aligned to 28S in the bam file?

Jared

@jts jts closed this as completed Jan 14, 2022
@kaltinel
Copy link
Author

kaltinel commented Jan 14, 2022

Hi,

Apologies for my late reply too!
Yes, my alignment file has lots of 28S reads ( and 18S, 5S and 5.8S). They are quite high in coverage as well.

However only 18S are seen in the nanopolish eventalign output..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants