The 'master_netmhcpan_4_1_alleles.tsv' is the only file that should matter and
be used for building the final allele file for allele-validator and allele-
autocomplete.

Here are some general steps taken to construct master_netmhcpan_4_1_alleles.tsv.

1. Combine these list of "available" alleles into a single file:
    a. MHC_allele_names.txt (from DTU)
    b. MHC_pseudo.dat (from package)
    c. allelenames (from package)
    d. model_list.txt (from package)
2. Subtract BoLA-NC* alleles (9 alleles).
   1. Found that there are 230 alleles not in autocomplete
   2. The list still contained duplicates
   3. 1085 alleles (tool label) that don't work with netmhcpan-4.1
3. Remove duplicates (add any synonyms before removal)
4. The standalone tool shows a separate list of netmhcpan-4.1 alleles. Save the
   list into a file "available_standalone_unique_alleles.tsv".
   We know that these alleles are valid for sure.
5. Check which one of the 230 alleles that are not found in the autocomplete
   can be identified and mapped to the MRO ID.
    1. Are we just missing it from the autocomplete?
    2. Are these alleles really not identifiable?
6a. From the 230 alleles, if they can be mapped, then save it into a file
    called 'verified_standalone_alleles.tsv' (157 alleles).
6b. From the 230 alleles, if they cannot be mapped, save them to
    'unknown_standalone_alleles_with_mroid.tsv' (72 alleles).
7. Integrate 'verified_standalone_alleles' to the master sheet.
8. Double check if any of 'unknown_standalone_alleles_with_mroid.tsv' already
   in the master file.
9. Double check the master file to see if there are alleles that has no MRO ID.
   1.  If so, remove them from the 'master_netmhcpan_4_1_alleles.tsv'.