Thank you for your reply. I’ve been running the pipeline using a sample with both Class I and Class II HLA alleles supplied in the same format as your test dataset (one allele per line, including DR, DQ, and DP). However, I noticed that the canonical Class II neoantigen predictions (from pVACseq) included only DRB1 alleles, whereas other alleles like DPA1/DPB1 were found in the NeoFuse results.
Could you please clarify:
Whether nextNEOpi handles DQ/DP pairing internally when running pVACseq?
If so, is there any filtering or compatibility check that might be excluding certain combinations from showing in(*MHC_Class_II_all_epitopes_ccf_ref_match.tsv)?
What is the recommended format and content for the HLA input file to ensure full Class II coverage across pVACseq and NeoFuse?
Any insight would be greatly appreciated to ensure I’m following best practices.
Originally posted by @nemke333 in #64
@nemke333
Thanks for the catch, we missed updating the class II model file should be fixed now. See assets/hlaii_models.txt for the supported list.
Originally posted by @nemke333 in #64
@nemke333
Thanks for the catch, we missed updating the class II model file should be fixed now. See
assets/hlaii_models.txtfor the supported list.