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
On the live flu builds, epitope mutations and other mutation metrics are defined as “ordinal” types in the auspice config JSON. These metrics get colors in the tree from a color ramp, but the frequencies panel shows gray for all values. This issue does not affect categorical or continuous values.
For example, epitope mutations appear like so in the frequencies panel:
While we would expect them to appear like the continuous distance to the future values:
The text was updated successfully, but these errors were encountered:
👍 I don't think this is an ordinal vs discrete issue, rather a problem of numeric values converted to strings when inserted into a dict (object). There was a similar (unrelated) issue a while ago which was fixed by storing the data in Map() objects which will preserve the type of the keys.
The underlying bug was a type-inconsistency whereby color-by values
can be numeric however the matrix was stored as an Object (where keys
are always stringified) and so `matrix[numeric_colorBy_value]=undefined`.
Switching to a Map() allows typed keys and fixes this bug.
Closes#843
On the live flu builds, epitope mutations and other mutation metrics are defined as “ordinal” types in the auspice config JSON. These metrics get colors in the tree from a color ramp, but the frequencies panel shows gray for all values. This issue does not affect categorical or continuous values.
For example, epitope mutations appear like so in the frequencies panel:
While we would expect them to appear like the continuous distance to the future values:
The text was updated successfully, but these errors were encountered: