Skip to content

Consensus-Sequence-Block:sequence length #66

@bmatern-nmdp

Description

@bmatern-nmdp

For every consensus-sequence-block node, the child sequence node must have a length of (end - start).

This is a problem with the validator. Start and end attributes come from CSB nodes, and I currently compare them directly with the length of the CSB:sequence. Variants (esp. insert and delete) are disregarded, but shouldn’t be. Corresponds to rule #4.2.3.e.

Solution: This will take some programming. Variants are complicated, but it's important to get it right, so recipients know exactly what the indices are pointing to. How should I calculate expected CSB:sequence length? I suppose I can determine what variants are insertions/deletions based on comparisons with reference/alternate bases. Don’t care about substitutions.

Expected consensus-sequence-block length = (CSB:end – CSB:start) - “deletions” + “insertions”

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions