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
We are facing some issues with the formatting for rows of type INV.
Based on the 4.2 spec (see section 5.4.7) it seems that if an INV is represented by a single row it should have an END value. However there is no such value provided in the output of Severus.
It may be as simple as adding the SVLEN value to the POS?
The text was updated successfully, but these errors were encountered:
Hello @awgymer,
Thank you for pointing this out. We will add the END field to the INFO column. But in the meantime, END is POS+SVLEN. Is this issue only related to INVs, or does it also affect DUPs/DELs?
Hello @awgymer,
In v1.2, we added the END field to INV entries. Regarding inversions, we now only report reciprocal inversions as INV and all other inverted junctions as BND.
We are facing some issues with the formatting for rows of type
INV
.Based on the 4.2 spec (see section 5.4.7) it seems that if an
INV
is represented by a single row it should have anEND
value. However there is no such value provided in the output of Severus.It may be as simple as adding the
SVLEN
value to thePOS
?The text was updated successfully, but these errors were encountered: