This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
Is end inclusive or exclusive? #202
Comments
The coordinate system that should be used throughout GA4GH standards is 0-based half open. So in a sequence of
... the exact match for
... due to interbase coordinates. I think we (...) have to fix this in the Wiki, which isn't correct for some of the positions... (edited the error after comments by @sdelatorrep and @antbro ...) |
mmmm I see. Then it's not clear at all in the spec. |
not 3-6?
T
…________________________________________
From: Michael Baudis <[email protected]>
Sent: 12 July 2018 16:09
To: ga4gh-beacon/specification
Cc: Subscribed
Subject: Re: [ga4gh-beacon/specification] Is end inclusive or exclusive? (#202)
The coordinate system that should be used throughout GA4GH standards is 0-based half open. So in a sequence of
ACCGTCGA
... the exact match for GTC would be
start: 4,
end: 7
... due to interbase coordinates.
I think we (...) have to fix this in the Wiki, which isn't correct for some of the positions...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#202 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AI_EVCFw31xpY3Pabo6sp4jeOvwKEX1Fks5uF2angaJpZM4VMk8a>.
|
@sdelatorrep & @antbro O.k.; can we roll this back, please? It is, obviously, counted base -1, when talking about the positions. I had shortened an example I was using & didn't shift ... Does the internet forget? |
sdelatorrep
added a commit
that referenced
this issue
Jul 30, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
One may assume it's inclusive because of this sentence in the spec (description of
start
parameter):but this assumption may be wrong. We must say it explicitly if it's inclusive or not.
The text was updated successfully, but these errors were encountered: