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.

Sign up for GitHub

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

Jump to bottom

Use 1-indexed exon numbers for the convert coordinates utility #340

Open
jarbesfeld opened this issue Oct 3, 2024 · 0 comments
Open

Use 1-indexed exon numbers for the convert coordinates utility #340

jarbesfeld opened this issue Oct 3, 2024 · 0 comments
Labels
priority:medium Medium priority

Comments

@jarbesfeld
Copy link

We currently report exon numbers using 0-indexing. We should be using 1-indexing instead to be consistent with the Transcript Segment Element output, which reports exon numbers using 1-indexing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority:medium Medium priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jarbesfeld