Skip to content

Set correct consequence priority for rank models using VEP CSQ instead of most_severe_consequence #133

@fellen31

Description

@fellen31

Since the consequences are ranked via priority (not score) for rank models using VEP CSQ instead of most_severe_consequence, we should set the correct priority to match score. Here for example, three different terms with different scores have the same priority, meaning the highest scoring term will not be the one chosen, rather the one appearing first in the rank model file:

[[non_coding_transcript_exon_variant]]
score = 3
priority = 2
string = 'non_coding_transcript_exon_variant'
[[synonymous_variant]]
score = 2
priority = 2
string = 'synonymous_variant'
[[start_retained_variant]]
score = 1
priority = 2
string = 'start_retained_variant'

I can find no documentation for this, either in genmod or atlas and genmod does not complain when multiple entries have the same priority. It should clear and easy for a users who wants to add or update rank models how they work, not a mystery.

Acceptance Criteria

  • Update rank models for Nallo with correct consequence priority
  • Add documentation on how to properly write this part of a rank model

Notes

  • Additional information.
  • Dependencies.
  • Related user stories.

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