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
Titer records define strain names for test and reference viruses, but we do not automatically cross-check these names with existing names in GISAID/GenBank records. As a result, there can be misspelled strain names in the titer records that lead us to omit these measurements from analyses when they do not match the corresponding sequence record's strain name.
Tal from the Bloom lab has helpfully provided a list of misspellings that he detected in our Crick titers:
Misspelled strains in the list above should match their sequence strain names.
Possible solution
In addition to manually correcting these records in our database, we should also consider flagging any titer records with potential misspellings. One easy check would be for records whose test or reference strains don't have corresponding records in the sequence database.
The text was updated successfully, but these errors were encountered:
Current Behavior
Titer records define strain names for test and reference viruses, but we do not automatically cross-check these names with existing names in GISAID/GenBank records. As a result, there can be misspelled strain names in the titer records that lead us to omit these measurements from analyses when they do not match the corresponding sequence record's strain name.
Tal from the Bloom lab has helpfully provided a list of misspellings that he detected in our Crick titers:
Expected behavior
Misspelled strains in the list above should match their sequence strain names.
Possible solution
In addition to manually correcting these records in our database, we should also consider flagging any titer records with potential misspellings. One easy check would be for records whose test or reference strains don't have corresponding records in the sequence database.
The text was updated successfully, but these errors were encountered: