Context
We estimate frequencies for mutually exclusive clades/haplotypes in the MLR, but displaying the frequencies in this way causes ancestral named clades to appear at low frequency when their emerging haplotypes are at high frequency.
Description
We should display inclusive frequencies for named clades, summing frequencies like "K:80K", "K:88I", etc. into frequencies displayed for "K", for example.
Possible solution
We could calculate these inclusive frequencies in the visualization application or in the MLR JSONs in the workflow.
We might want to label the inclusive frequencies differently from other groups, to indicate that those frequencies are not the mutually exclusive values from the MLR. In the previous "flu_frequencies" workflow, inclusive frequencies had a * label like K*.
Context
We estimate frequencies for mutually exclusive clades/haplotypes in the MLR, but displaying the frequencies in this way causes ancestral named clades to appear at low frequency when their emerging haplotypes are at high frequency.
Description
We should display inclusive frequencies for named clades, summing frequencies like "K:80K", "K:88I", etc. into frequencies displayed for "K", for example.
Possible solution
We could calculate these inclusive frequencies in the visualization application or in the MLR JSONs in the workflow.
We might want to label the inclusive frequencies differently from other groups, to indicate that those frequencies are not the mutually exclusive values from the MLR. In the previous "flu_frequencies" workflow, inclusive frequencies had a
*label likeK*.