forked from ave-dcd/dcd_mapping
-
Notifications
You must be signed in to change notification settings - Fork 0
Add per-variant mapping quality flags #87
Copy link
Copy link
Open
Labels
app: backendTask implementation touches the backendTask implementation touches the backendapp: databaseTask implementation requires database changesTask implementation requires database changesapp: mapperTask implementation touches the mapperTask implementation touches the mappertype: enhancementNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
app: backendTask implementation touches the backendTask implementation touches the backendapp: databaseTask implementation requires database changesTask implementation requires database changesapp: mapperTask implementation touches the mapperTask implementation touches the mappertype: enhancementNew feature or requestNew feature or request
A variant that maps cleanly onto a concordant alignment column is fundamentally different from one that sits on a mismatch or near a gap boundary — but currently they look identical in the output. Compute and store per-variant flags on the mapped variant record:
These flags should be exposed in the API response. The KSR1 case — where VP→DI was silently miscalled because the variant sat on a mismatch adjacent to a misplaced gap — is the motivating example. Depends on the mapping table (#86) being in place first.