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
Originally reported by: Reece Hart (Bitbucket: reece, GitHub: reece)
If a user fetches accessions from relevant_transcripts(), they may including coding and non-coding.
When using those transcripts, users should call g_to_c with coding transcripts and g_to_n with non-coding transcripts. Calling g_to_c with a non-coding transcript results in an exception.
This proposal is to add g_to_t, with a call signature identical to g_to_c/n, that will transparently project to the correct type.
Conversely, a general t_to_g method would project from either transcript type to genomic coordinates.
Originally reported by: Reece Hart (Bitbucket: reece, GitHub: reece)
If a user fetches accessions from relevant_transcripts(), they may including coding and non-coding.
When using those transcripts, users should call g_to_c with coding transcripts and g_to_n with non-coding transcripts. Calling g_to_c with a non-coding transcript results in an exception.
This proposal is to add g_to_t, with a call signature identical to g_to_c/n, that will transparently project to the correct type.
Conversely, a general t_to_g method would project from either transcript type to genomic coordinates.
The text was updated successfully, but these errors were encountered: