Mpox pango aliases after two dots: so B.1.1 = C, and A.1.1 = B
For influenza, the system now uses flexible aliasing, so sometimes F = B.1.2.3.4, whereas G = B.1.2.3.4.5.6
It would be nice if SILO (and LAPIS) supported those more flexible interpretations of pango.
Currently, when you specify such an alias file, you get errors like:
{"instance":"lapisClient","level":"info","message":"Request failed with status code 500: Error from SILO: vector::_M_range_check: __n (which is 33) >= this->size() (which is 32)","timestamp":"2024-05-20T23:15:24.869Z"}
Mpox pango aliases after two dots: so B.1.1 = C, and A.1.1 = B
For influenza, the system now uses flexible aliasing, so sometimes F = B.1.2.3.4, whereas G = B.1.2.3.4.5.6
It would be nice if SILO (and LAPIS) supported those more flexible interpretations of pango.
Currently, when you specify such an alias file, you get errors like: