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
As a clinician I would like to see from which callers a variant has been called. Currently in release 16.0.0 of balsamic, when a variant is called by both TNscope and VarDict, only VarDict information remains. This is not correct, and leads to view of TNscope as primarily calling questionable / artefact variants as only those uniquely called by TNscope are labled as called by TNscope.
We need to update the merging method so at a minimum the information about which caller found the variant is retained.
Suggested approach
No response
Considered alternatives
No response
Deviation
No response
System requirements assessed
Yes, I have reviewed the system requirements
Requirements affected by this story
No response
Risk assessment needed
Needed
Not needed
Risk assessment
No response
SOUPs
No response
Can be closed when
No response
Blockers
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Need
As a clinician I would like to see from which callers a variant has been called. Currently in release 16.0.0 of balsamic, when a variant is called by both TNscope and VarDict, only VarDict information remains. This is not correct, and leads to view of TNscope as primarily calling questionable / artefact variants as only those uniquely called by TNscope are labled as called by TNscope.
We need to update the merging method so at a minimum the information about which caller found the variant is retained.
Suggested approach
No response
Considered alternatives
No response
Deviation
No response
System requirements assessed
Requirements affected by this story
No response
Risk assessment needed
Risk assessment
No response
SOUPs
No response
Can be closed when
No response
Blockers
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: