The way it is currently set up, the output of get_coding_ssm_status will always make hotspots non-redundant with SSM even in the samples that are actually multihit and contain both hot spot and non hot spot mutation. This is not always desirable and should be dictated by user.
This function needs an optional argument that will allow user to dynamically keep multihit samples annotated for both SSM and hot spots.
Kdreval
commented
1 year ago
The way it is currently set up, the output of
get_coding_ssm_statuswill always make hotspots non-redundant with SSM even in the samples that are actually multihit and contain both hot spot and non hot spot mutation. This is not always desirable and should be dictated by user.This function needs an optional argument that will allow user to dynamically keep multihit samples annotated for both SSM and hot spots.