Closed selkamand closed 1 year ago
Actually can't do this from palette function where mutation type is classified. If SO, type, we should check for '&' characters, and if we find any throw an error - telling the user to run mutationtypes::select_most_severe_consequence_so(consequence)) on the consequence types before use.
Alternatively we must rework function structure, and test type in main function - then we can edit the data itself.
Lets start by throwing the appropriate error, but can revisit if this proves annoying
Currently if there are & separated multi consequences - it throws off multi-hit palette.
We should automatically run:
mutationtypes::select_most_severe_consequence_so(consequence))
on these samples to simplify the consequence field before plotting