-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MHC allele supported by the original prediction method, but not recognized by pvacseq #1146
Comments
It seems you are right. We got our list from https://services.healthtech.dtu.dk/services/NetMHCIIpan-4.0/alleles_name.list, which doesn't include H2-IEd. Can you please let me know which list you were using so I can double check that we are supporting all possible alleles. |
@susannasiebert I was using https://services.healthtech.dtu.dk/services/NetMHCIIpan-4.3/alleles_name.list. I was initially concerned that this allele might be left out due to its predictions being problematic, but I saw your recent commit with the updated list so my question is answered. Thanks for taking care of this! |
That looks like a newer version than what is supported in IEDB (4.0 and 4.1). I will do some more research into the different versions and test which alleles actually work with IEDB. The IEDB lists aren’t always up date it looks like. I’m not sure why this allele wasn’t formally listed in the original 4.0/4.1 versions since it still seems to work. I don’t have any information about how reliable the predictions are under the older netmhciipan versions, unfortunately. |
I'm trying to use NetMHCIIpan to predict epitope binding to a mouse class II allele, H2-IEd. Output of
pvacseq valid_algorithms -a H2-IEd
suggests that it is not supported by NetMHCIIpan, yet it is in the list of supported alleles on NetMHCIIpan website.Turns out if I add H2-IEd to
iedb/mhc_ii/methods/allele-info/allele_info/pickles/mhcii_info_dict.p
andpvactools/tools/pvacseq/iedb_alleles/class_ii/NetMHCIIpan.tsv
, pvacseq is indeed able to generate NetMHCIIpan prediction for this allele. So I wonder if there is any particular reason that this allele is disabled in pvacseq configuration files?The text was updated successfully, but these errors were encountered: