-
Notifications
You must be signed in to change notification settings - Fork 38
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
How should we interpret SR
of the L
line in rGFA
#19
Comments
SR on L-lines plays the same role as SR on S-lines. Think about a deletion from the reference. If you don't keep SR on L-lines/links, you don't know how to traverse the reference path. |
What about L-lines that connects two segments of different ranks? |
A link shouldn't have a lower rank than the two segments. Think about the minigraph incremental graph construction procedure. SR on L-line is a natural outcome. |
Sorry, I meant a link that links together two segments having different ranks, e.g. a link that links together one segment from GRCh38 and one segment from CHM13 (T2T). If the rGFA file was built started with GRCh38 (hence rank 0) then with CHM13 (hence rank 1), |
Probably not. |
Hello Heng,
While I'm playing with the example assemblies on the FTP site, I noticed that (all) the L-lines in the rGFA file also have the
SR
tag, which isn't a required tag according to the rGFA format (only the S-Lines are required to).So how should we interpret them?
Thanks!
Steve
The text was updated successfully, but these errors were encountered: