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
Thank you for the great tool!
It seems to be working perfectly for me but I would like to request a feature implementation.
Would it be possible to add a column of in-frame Ribo-seq (not TI-seq) count per ORF to the result of ribotish predict, like TISCount column for TI-seq?
I believe this would be useful from the following viewpoints (I'm detecting ORFs using Ribo-seq only, without TI-seq):
The current output includes ORFs with very low read counts. I understand that this is helpful for increasing sensitivity but in some cases users may want to apply filtering by CPM etc to extract highly-translated ORFs.
With --framebest option, one stop codon can have multiple TIS, when RiboPvalue has ties (especially when RiboPvalue = 0). One option for filtering is taking the longest ORF but it would be more helpful if users can take P-site read abundance into consideration to pick up the ORF with highest translation activity.
I would appreciate it if you could consider implementing this feature, only if it would not cause too much trouble for you.
Many thanks,
Sotta
The text was updated successfully, but these errors were encountered:
Thank you for the great tool!
It seems to be working perfectly for me but I would like to request a feature implementation.
Would it be possible to add a column of in-frame Ribo-seq (not TI-seq) count per ORF to the result of
ribotish predict
, likeTISCount
column for TI-seq?I believe this would be useful from the following viewpoints (I'm detecting ORFs using Ribo-seq only, without TI-seq):
--framebest
option, one stop codon can have multiple TIS, whenRiboPvalue
has ties (especially whenRiboPvalue
= 0). One option for filtering is taking the longest ORF but it would be more helpful if users can take P-site read abundance into consideration to pick up the ORF with highest translation activity.I would appreciate it if you could consider implementing this feature, only if it would not cause too much trouble for you.
Many thanks,
Sotta
The text was updated successfully, but these errors were encountered: