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
Currently, insertions in the consensus relative to the reference are reported in nuc.csv and amino.csv as counts in the insertions column, but the actual insertion sequence is not included. Users have reported back that it would be useful to have access to the sequence of the consensus insertion in these files as well.
Add the consensus insertion sequence in nuc.csv and amino.csv, with their respective consensus coordinates and blank reference coordinates - this is equivalent to how deletions are treated, with blank consensus positions. Think about how to use the insertions column in these cases - should it report the total insertions count for the insertion positions only (in contrast to reporting insertions after a certain position right now)?
This could be implemented in the same way that insertions are handled for the stitched consensus, by adding them into the region nucleotides and aminos with non-integer positions, so they end up between the correct reference positions.
The text was updated successfully, but these errors were encountered:
Currently, insertions in the consensus relative to the reference are reported in nuc.csv and amino.csv as counts in the insertions column, but the actual insertion sequence is not included. Users have reported back that it would be useful to have access to the sequence of the consensus insertion in these files as well.
Add the consensus insertion sequence in nuc.csv and amino.csv, with their respective consensus coordinates and blank reference coordinates - this is equivalent to how deletions are treated, with blank consensus positions. Think about how to use the insertions column in these cases - should it report the total insertions count for the insertion positions only (in contrast to reporting insertions after a certain position right now)?
This could be implemented in the same way that insertions are handled for the stitched consensus, by adding them into the region nucleotides and aminos with non-integer positions, so they end up between the correct reference positions.
The text was updated successfully, but these errors were encountered: