Skip to content

Fail hypermutated flag in cancer report #44

@qclayssen

Description

@qclayssen

As pointed out in this slack thread
there is issue with hypermutated flag in cancer report. it was introduce in gpgr PR#83

option point out by stephen here

Conceptually the ‘sage’ variants would be more complete since that includes rescue variants, though this may still not be the best representation of mutational load since it also includes non-passing DRAGEN variants at that point iirc
Some options to consider:
-modify the status check wrt which variants are considered
-possibly reverting the flag conditional to how I initially implemented (less explicit but does not rely on re-inferring status)
-moving the status check in gpgr Cancer Report to bolt where this already happens (personally preferred approach)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions