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
Dear developers,
I am trying to characterize a strain of Leptospira with Leptospira spp dataset 1, but when I run the prediction I got the following error: ERROR: gene names in config file do not match gene names in profile file
Checking config and profile files, I noticed that profile contains less columns than the number of genes included in the associated config, and moreover it seems to be identical to the profile file of Leptospira spp dataset 3.
Could you please check if there is any error in this profile file and eventually provide an updated version?
Thank you in advance!
Best Regards
Loris
The text was updated successfully, but these errors were encountered:
I just want to clarify your intended usage. While the database dumps are released under an MIT license, stringMLST is released under a non-commercial license. It seems you're using stringMLST in a commercial capacity at BMR Genomic. While we're happy to provide support gratis for non-commercial use, your employer would need to purchase a commercial license for stringMLST (as well as your prior unauthorized use). Please email king.jordan<@>biology.gatech.edu and myself (achande<@>ihrc.com) for more details.
Dear developers,
I am trying to characterize a strain of Leptospira with Leptospira spp dataset 1, but when I run the prediction I got the following error:
ERROR: gene names in config file do not match gene names in profile file
Checking config and profile files, I noticed that profile contains less columns than the number of genes included in the associated config, and moreover it seems to be identical to the profile file of Leptospira spp dataset 3.
Could you please check if there is any error in this profile file and eventually provide an updated version?
Thank you in advance!
Best Regards
Loris
The text was updated successfully, but these errors were encountered: