modeller_usage April 2007

modeller_usage@salilab.org

9 participants
16 discussions

Add rigid bodies and CA-CA restraints
by Gregoire Depret 10 Apr '07

10 Apr '07

Hello, I have built a model and I want it to satisfy some CA-CA restraints. In order to do so, I've added some restraints with the command "rsr.add(forms.gaussian(group=physical.xy_distance,feature=features.distance(at['CA:893:C'],at['CA:184:B']),mean=10.0, stdev=0.1))" and some restraints on secondary structure to avoid unwinding of alpha helix. Actually these restraints caused kinks in alpha-helices that are known to span the membrane. To avoid that kind of kinks I want to treat the helices as rigid bodies. First I tried to add rigid bodies in the same script a = mymodel(env, alnfile = 'align.pir', # alignment filename knowns = '2OXS', # codes of the templates sequence = 'mytemplate ') # code of the target r = rigid_body(a.residue_range('180:B', '200:B')) s = rigid_body(a.residue_range('890:C', '900:C')) a.restraints.rigid_bodies.append(r) a.restraints.rigid_bodies.append(s) But in this case, MODELLER doesn't recognize the residue range, and raises the error "No such Residues 180:B". I have checked in previous models; the residues are there. I also tried to start from an existing model and applied molecular dynamics on it, like it is described in optimize.py. I have succeeded in defining the rigid body on my initial model but the applied restraints aren't strong enough to move my intitial model. In addition the MD partially unwinds the secondary structure of my model. Here is the script I used that differs from the manual. # Keep residues 1-10 rigid: r = rigid_body(mdl.residue_range('277:B', '318:B')) s = rigid_body(mdl.residue_range('972:C', '1014:C')) mdl.restraints.rigid_bodies.append(r) mdl.restraints.rigid_bodies.append(s) # Select all atoms: atmsel = selection(mdl) # Generate the restraints: mdl.restraints.make(atmsel, restraint_type='stereo', spline_on_site=False) mdl.restraints.write(file=code+'.rsr') a = mdl.atoms mdl.restraints.add(forms.upper_bound(group=physical.xy_distance, feature=features.distance(a['CA:343:B'], a['CA:986:C']), mean=18., stdev=0.1)) Thus I have two questions : Is it possible, in the same script, to add rigid body restraints and then do the modelling or applying rigid bodies is only possible on an already existing model? To satisfy my restraints which approach is the best : add my CA-CA restraint, my rigid body definition and make the homology modelling at the same time or do a MD on an existing model? Suggestions are welcome. Many Thanks, Depret Grégoire

2 1

Rigid ligand
by dimitry.a.suplatov 10 Apr '07

10 Apr '07

I have a big lignad (Oxidised penicillin G) I want to model with. Is there a special command to make it rigid during the modeling process? Thanks

2 1

User defined restraints
by Dimitry.A.Suplatov 09 Apr '07

09 Apr '07

Hello. I want to define restraints while modeling with ligand and I want to define different restraints. I use the following script --------------------------------------------------------------------------------------------- ... class mymodel(automodel): def special_restraints(self, aln): rsr = self.restraints for ids in (('OD1:282:B', 'CA:765:B'), ('OD2:282:B', 'CA:765:B'), ('OD1:285:B','CA:765:B'), ('OD2:460:B', 'CA:765:B'), ('OE2:152:A', 'CA:765:B')): atoms = [self.atoms[i] for i in ids] rsr.add(forms.upper_bound(group=physical.upper_distance, feature=features.distance(*atoms), mean=2.5, stdev=0.1)) def special_restraints(self, aln): rsr2 = self.restraints for ids1 in (('OE2:152:A', 'CA:765:B')): atoms = [self.atoms[j] for j in ids1] rsr2.add(forms.upper_bound(group=physical.upper_distance, feature=features.distance(*atoms), mean=2.3, stdev=0.1)) env = environ() env.io.hetatm = True env.io.water = True ... --------------------------------------------------------------------------------------------- Then I get this error -------------------------------------------------------------------------------------------- Traceback (most recent call last): File "model-ca.py", line 32, in ? a.make() File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", line 108, in make self.homcsr(exit_stage) File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", line 427, in homcsr self.mkhomcsr(selection(self), aln) File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", line 537, in mkhomcsr self.special_restraints(aln) File "model-ca.py", line 19, in special_restraints atoms = [self.atoms[j] for j in ids1] File "C:\Program Files\Modeller9v1\modlib\modeller\coordinates.py", line 127, in __getitem__ (self.offset, self.length, self.suffix)) File "C:\Program Files\Modeller9v1\modlib\modeller\util\modutil.py", line 76, in handle_seq_indx int_indx = lookup_func(*args) File "C:\Program Files\Modeller9v1\modlib\modeller\coordinates.py", line 40, in _indxatm newindx = _modeller.indxatm2(indx+suffix, self.modpt) - 1 - offset _modeller.error: indxatm_278E> No ":" in ATOM:RESID[:CHAINID] atom identifier: O --------------------------------------------------------------------------------------------- I am using python for the first time so that must be some problem with the script. Do you have any suggestions? Thank you!

2 1

Re: [modeller_usage] modeller_usage Digest, Vol 6, Issue 29
by Dimitry.A.Suplatov 08 Apr '07

08 Apr '07

Thank you. As you`ve said, the problem was with the alignment (I should have put "." instead of "-" in my seq) and with chain labeling. Modeller Caretaker wrote: > Dimitry.A.Suplatov wrote: >> I am having a great problem with modeller 9v1. >> My aim is to model 2 chain protein from a 2 chain template with a >> ligands. I want two ligands: Ca metal ion and SOX (Penicillin G >> sulphoxide). My template pdb file briefly looks like this: >> ---------------------------------------------------------------------------------------------------- >> >> ATOM 1 N SER A 3 27.496 31.222 28.262 1.00 >> 48.33 N ATOM 2 CA SER A 3 27.785 31.042 >> 26.803 1.00 43.97 C ... etc to the end of chain a >> TER 1679 ALA A 209 >> ATOM 1684 N SER B 1 14.845 1.596 -1.736 1.00 >> 6.93 N >> ATOM 1685 CA SER B 1 15.548 2.917 -1.659 1.00 >> 6.75 C ATOM 1686 C SER B 1 16.489 3.059 >> -2.844 1.00 8.04 C >> ..... >> ATOM 6113 NE ARG B 557 26.460 16.023 30.916 1.00 >> 23.74 N ATOM 6114 CZ ARG B 557 27.175 15.276 >> 30.094 1.00 19.20 C ATOM 6115 NH1 ARG B 557 >> 28.016 15.921 29.310 1.00 21.83 N ATOM 6116 NH2 ARG B >> 557 27.069 13.952 30.055 1.00 20.49 N ATOM 6117 >> OXT ARG B 557 23.973 18.664 34.656 1.00 29.98 O >> TER 6118 ARG B 557 >> .... Cutting useless HETATM >> HETATM 6159 CA CA B1568 23.187 -16.230 6.242 1.00 >> 10.86 CA << Ca ion >> HETATM 6160 O8 SOX B1569 13.279 0.047 0.037 1.00 >> 37.00 O << SOX ... >> HETATM 6161 C7 SOX B1569 13.688 -1.062 0.060 1.00 >> 38.52 C >> .. >> HETATM 6166 O12 SOX B1569 13.790 -4.072 -2.049 1.00 >> 54.27 O ...etc to the end of SOX (I guess resid for SOX = >> 569, chain B1, ?) > > No - see the definition of the PDB file format at > http://www.wwpdb.org/documentation/format23/sect9.html > > Your SOX residue is number 1569 in chain B. The PDB file format has > only one character for the chain ID, so chain "B1" is impossible. > >> My alignment looks like this: >> ----------------------------------------------------------------------------------------------------- >> >> >P1;1gm9 >> structureX:1gm9.pdb:3:A:569:B1:::: #Starting from A resid =3(because >> first two are missing) and finishing with SOX > > Consequently, this should also be 3:A:1569:B. > >> --SSSEIKIVRDEYG-PHIYANDTWHLFYGYGYVVAQDRLFQMEMARRSTQGTVAEVLGK >> DFVKFDKDIRRNYWPDAIRAQIAALSPEDMSILQGYADGMNAWIDKVNTNPETLLPKQFN >> TFGFTPKRWEPFDVAMIFVGTMANRFSDSTSEIDNLALLTALKDKYGVSQGMAVFNQLKW >> LVNPSAPTTIAVQESNYPLKFNQQNSQTA/ #Chain break = ending chain A >> SNMWVIGKSKAQDAKAIMVNGPQFGWYAPAY >> TYGIGLHGAGYDVTGNTPFAYPGLVFGHNGVISWGSTAGFGDDVDIFAERLSAEKPGYYL >> HNGKWVKMLSREETITVKNGQAETFTVWRTVHGNILQTDQTTQTAYAKSRAWDGKEVASL >> LAWTHQMKAKNWQEWTQQAAKQALTINWYYADVNGNIGYVHTGAYPDRQSGHDPRLPVPG >> TGKWDWKGLLPFEMNPKVYNPQSGYIANWNNSPQKDYPASDLFAFLWGGADRVTEIDRLL >> EQKPRLTADQAWDVIRQTSRQDLNLRLFLPTLQAATSGLTQSDPRRQLVETLTRWDGINL >> LNDDGKTWQQPGSAILNVWLTSMLKRTVVAAVPMPFDKWYSASGYETTQDGPTGSLNISV >> GAKILYEAVQGDKSPIPQAVDLFAGKPQQEVVLAALEDTWETLSKRYGNNVSNWKTPAMA >> LTFRANNFFGVPQAAAEETRHQAEYQNRGTENDMIVFSPTTSDRPVLAWDVVAPGQSGFI >> APDGTVDKHYEDQLKMYENFGRKSLWLTKQDVEAHKESQEVLHVQR/..* >> #Chain break = ending chain B and ".." for two HETATM > > That's fine except that there is no chain break between chain B and > your two HETATMs in your PDB. The HETATMs are also in chain B, so you > should leave out that last chain break. > >> >P1;1klc >> sequence:1klc: : : : ::: 0.00: 0.00 >> ASPPTEVKIVRDEYGMPHIYADDTYRLFYGYGYVVAQDRLFQMEMARRSTQGTVSEVLGK >> AFVSFDKDIRQNYWPDSIRAQIASLSAEDKSILQGYADGMNAWIDKVNASPDKLLPQQFS >> TFGFKPKHWEPFDVAMIFVGTMANRFSDSTSEIDNLALLTAVKDKYGNDEGMAVFNQLKW >> LVNPSAPTTIAARESSYPLKFDLQNTQTA/ >> SNMWVIGKNKAQDAKAIMVNGPQFGWYAPAY >> TYGIGLHGAGYDVTGNTPFAYPGLVFGHNGTISWGSTAGFGDDVDIFAEKLSAEKPGYYQ >> HNGEWVKMLSRKETIAVKDGQPETFTVWRTLDGNVIKTDTRTQTAYAKARAWAGKEVASL >> LAWTHQMKAKNWPEWTQQAAKQALTINWYYADVNGNIGYVHTGAYPDRQPGHDPRLPVP- >> DGKWDWKGLLSFDLNPKVYNPQSGYIANWNNSPQKDYPASDLFAFLWGGADRVTEIDTIL >> DKQPRFTADQAWDVIRQTSLRDL-LRLFLPALKDATANLAENDPRRQLVDKLASWDGENL >> VNDDGKTYQQPGSAILNAWLTSMLKRTVVAAVPAPFGKWYSASGYETTQDGPTGSLNISV >> GAKILYEALQGDKSPIPQAVDLFGGKPEQEVILAALDDAWQTLSKRYGNDVTGWKTPAMA >> LTFRANNFFGVPQAAAKEARHQAEYQNRGTENDMIVFSPTSGNRPVLAWDVVAPGQSGFI >> APDGKADKHYDDQLKMYESFGRKSLWLTPQDVDEHKESQEVLQVQR/--* > > The last chain break is thus also not necessary here. Plus, Modeller > won't build any ligands in your model because you aligned your ligands > with gaps in the model. Replace that final '--' with '..' to get the > ligands. > >> Modeller starts with this error: "import site' failed; use -v for >> traceback" > > That's a Python warning, which you can ignore: see > http://salilab.org/modeller/release.html#issues > >> KeyError: 'No such atom: O12:766:C' >> ---------------------------------------------------------------------------------------------------------- >> >> That means, that it can not see atom O12:766:C. > > It can't find the SOX residue because your alignment does not say to > build any ligands. To be sure of the residue numbers, look at the > initial model (.ini) file that Modeller generated. > >> If I remove user restraints and just use automodel, it output good >> model, but without ligands at all! >> And the latter is what I absolutely do no understand. > > Fix your alignment and everything should work correctly. > >> My log has this note about SOX: >> ----------------------------------------------------------------------------------------------------------- >> >> read_pd_459W> Residue type SOX not recognized. 'automodel' model >> building >> will treat this residue as a rigid body. >> To use real parameters, add the residue type to >> ${LIB}/restyp.lib, >> its topology to ${LIB}/top_*.lib, and suitable forcefield >> parameters to ${LIB}/par.lib. > > Indeed. > >> And nothing about CA (may be the program takes CA as Calpha?). > > No, of course not - Calpha is an atom type, not a residue. Modeller > already knows what the "CA" residue type is - it's defined in restyp.lib. > >> 2. Why modeller outputs model with no ligands if I use default >> automodel with no restraints (env.io.hetatm =True)?. > > Turning on env.io.hetatm instructs Modeller to read HETATM residues > from your template PDBs. It does not force those HETATMs to appear in > your model - the alignment controls that. > >> P.S. I am using windows compilation. May it be some platform specific >> modeller bug? > > No. Ligand modeling works fine in Windows. > > Ben Webb, Modeller Caretaker

1 0

Modeling multiple chains with two ligands
by Dimitry.A.Suplatov 08 Apr '07

08 Apr '07

Hello, I am having a great problem with modeller 9v1. My aim is to model 2 chain protein from a 2 chain template with a ligands. I want two ligands: Ca metal ion and SOX (Penicillin G sulphoxide). My template pdb file briefly looks like this: ---------------------------------------------------------------------------------------------------- ATOM 1 N SER A 3 27.496 31.222 28.262 1.00 48.33 N ATOM 2 CA SER A 3 27.785 31.042 26.803 1.00 43.97 C ... etc to the end of chain a TER 1679 ALA A 209 ATOM 1684 N SER B 1 14.845 1.596 -1.736 1.00 6.93 N ATOM 1685 CA SER B 1 15.548 2.917 -1.659 1.00 6.75 C ATOM 1686 C SER B 1 16.489 3.059 -2.844 1.00 8.04 C ..... ATOM 6113 NE ARG B 557 26.460 16.023 30.916 1.00 23.74 N ATOM 6114 CZ ARG B 557 27.175 15.276 30.094 1.00 19.20 C ATOM 6115 NH1 ARG B 557 28.016 15.921 29.310 1.00 21.83 N ATOM 6116 NH2 ARG B 557 27.069 13.952 30.055 1.00 20.49 N ATOM 6117 OXT ARG B 557 23.973 18.664 34.656 1.00 29.98 O TER 6118 ARG B 557 .... Cutting useless HETATM HETATM 6159 CA CA B1568 23.187 -16.230 6.242 1.00 10.86 CA << Ca ion HETATM 6160 O8 SOX B1569 13.279 0.047 0.037 1.00 37.00 O << SOX ... HETATM 6161 C7 SOX B1569 13.688 -1.062 0.060 1.00 38.52 C .. HETATM 6166 O12 SOX B1569 13.790 -4.072 -2.049 1.00 54.27 O ...etc to the end of SOX (I guess resid for SOX = 569, chain B1, ?) ----------------------------------------------------------------------------------------------------- I have made alignment in PIR using chain breaks "/" and block residues "." for Ca and SOX. My alignment looks like this: ----------------------------------------------------------------------------------------------------- >P1;1gm9 structureX:1gm9.pdb:3:A:569:B1:::: #Starting from A resid =3(because first two are missing) and finishing with SOX --SSSEIKIVRDEYG-PHIYANDTWHLFYGYGYVVAQDRLFQMEMARRSTQGTVAEVLGK DFVKFDKDIRRNYWPDAIRAQIAALSPEDMSILQGYADGMNAWIDKVNTNPETLLPKQFN TFGFTPKRWEPFDVAMIFVGTMANRFSDSTSEIDNLALLTALKDKYGVSQGMAVFNQLKW LVNPSAPTTIAVQESNYPLKFNQQNSQTA/ #Chain break = ending chain A SNMWVIGKSKAQDAKAIMVNGPQFGWYAPAY TYGIGLHGAGYDVTGNTPFAYPGLVFGHNGVISWGSTAGFGDDVDIFAERLSAEKPGYYL HNGKWVKMLSREETITVKNGQAETFTVWRTVHGNILQTDQTTQTAYAKSRAWDGKEVASL LAWTHQMKAKNWQEWTQQAAKQALTINWYYADVNGNIGYVHTGAYPDRQSGHDPRLPVPG TGKWDWKGLLPFEMNPKVYNPQSGYIANWNNSPQKDYPASDLFAFLWGGADRVTEIDRLL EQKPRLTADQAWDVIRQTSRQDLNLRLFLPTLQAATSGLTQSDPRRQLVETLTRWDGINL LNDDGKTWQQPGSAILNVWLTSMLKRTVVAAVPMPFDKWYSASGYETTQDGPTGSLNISV GAKILYEAVQGDKSPIPQAVDLFAGKPQQEVVLAALEDTWETLSKRYGNNVSNWKTPAMA LTFRANNFFGVPQAAAEETRHQAEYQNRGTENDMIVFSPTTSDRPVLAWDVVAPGQSGFI APDGTVDKHYEDQLKMYENFGRKSLWLTKQDVEAHKESQEVLHVQR/..* #Chain break = ending chain B and ".." for two HETATM >P1;1klc sequence:1klc: : : : ::: 0.00: 0.00 ASPPTEVKIVRDEYGMPHIYADDTYRLFYGYGYVVAQDRLFQMEMARRSTQGTVSEVLGK AFVSFDKDIRQNYWPDSIRAQIASLSAEDKSILQGYADGMNAWIDKVNASPDKLLPQQFS TFGFKPKHWEPFDVAMIFVGTMANRFSDSTSEIDNLALLTAVKDKYGNDEGMAVFNQLKW LVNPSAPTTIAARESSYPLKFDLQNTQTA/ SNMWVIGKNKAQDAKAIMVNGPQFGWYAPAY TYGIGLHGAGYDVTGNTPFAYPGLVFGHNGTISWGSTAGFGDDVDIFAEKLSAEKPGYYQ HNGEWVKMLSRKETIAVKDGQPETFTVWRTLDGNVIKTDTRTQTAYAKARAWAGKEVASL LAWTHQMKAKNWPEWTQQAAKQALTINWYYADVNGNIGYVHTGAYPDRQPGHDPRLPVP- DGKWDWKGLLSFDLNPKVYNPQSGYIANWNNSPQKDYPASDLFAFLWGGADRVTEIDTIL DKQPRFTADQAWDVIRQTSLRDL-LRLFLPALKDATANLAENDPRRQLVDKLASWDGENL VNDDGKTYQQPGSAILNAWLTSMLKRTVVAAVPAPFGKWYSASGYETTQDGPTGSLNISV GAKILYEALQGDKSPIPQAVDLFGGKPEQEVILAALDDAWQTLSKRYGNDVTGWKTPAMA LTFRANNFFGVPQAAAKEARHQAEYQNRGTENDMIVFSPTSGNRPVLAWDVVAPGQSGFI APDGKADKHYDDQLKMYESFGRKSLWLTPQDVDEHKESQEVLQVQR/--* --------------------------------------------------------------------------------------------------------- Then I used advanced example as a template to write my input script: --------------------------------------------------------------------------------------------------------- from modeller import * from modeller.automodel import * class mymodel(automodel): def special_restraints(self, aln): rsr = self.restraints for ids in (('NH2:471:B', 'O12:766:C'), # That is for SOX, no restraints for Ca ('ND2:449:B', 'O16:766:C'), ('CE2:280:B', 'C5:766:C')): atoms = [self.atoms[i] for i in ids] rsr.add(forms.upper_bound(group=physical.upper_distance, feature=features.distance(*atoms), mean=3.04, stdev=0.1)) env = environ() env.io.hetatm = True a = mymodel(env, alnfile='1klc_1gm9.ali', knowns='1gm9m, 1klc_model', sequence='1klc') a.starting_model = 1 a.ending_model = 1 a.make() ------------------------------------------------------------------------------------------------------ Modeller starts with this error: "import site' failed; use -v for traceback", (I guess it is not a big problem because in other cases it does not cause any trouble) , then program starts calculating, and then I always get : ----------------------------------------------------------------------------------------------------- Traceback (most recent call last): File "model-multiple-hetero.py", line 47, in ? a.make() File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", li ne 108, in make self.homcsr(exit_stage) File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", li ne 427, in homcsr self.mkhomcsr(selection(self), aln) File "C:\Program Files\Modeller9v1\modlib\modeller\automodel\automodel.py", li ne 537, in mkhomcsr self.special_restraints(aln) File "model-multiple-hetero.py", line 10, in special_restraints atoms = [self.atoms[i] for i in ids] File "C:\Program Files\Modeller9v1\modlib\modeller\coordinates.py", line 127, in __getitem__ (self.offset, self.length, self.suffix)) File "C:\Program Files\Modeller9v1\modlib\modeller\util\modutil.py", line 76, in handle_seq_indx int_indx = lookup_func(*args) File "C:\Program Files\Modeller9v1\modlib\modeller\coordinates.py", line 42, i n _indxatm raise KeyError, ("No such atom: %s" % indx) KeyError: 'No such atom: O12:766:C' ---------------------------------------------------------------------------------------------------------- That means, that it can not see atom O12:766:C. I am sure, that my seq is 764 residues long (I mean residues in seq, not position in alignment). So Ca must be 765 and SOX - 766. I have tried different counts (766,765,767...) and different chains (B1, C) but it did not help. I have tried to model only chain B with SOX, but it did not help. If I remove user restraints and just use automodel, it output good model, but without ligands at all! And the latter is what I absolutely do no understand. My log has this note about SOX: ----------------------------------------------------------------------------------------------------------- read_pd_459W> Residue type SOX not recognized. 'automodel' model building will treat this residue as a rigid body. To use real parameters, add the residue type to ${LIB}/restyp.lib, its topology to ${LIB}/top_*.lib, and suitable forcefield parameters to ${LIB}/par.lib. ----------------------------------------------------------------------------------------------------------- And nothing about CA (may be the program takes CA as Calpha?). So my questions are: 1. What am I doing wrong? 2. Why modeller outputs model with no ligands if I use default automodel with no restraints (env.io.hetatm =True)?. What do you think? Thank you for your suggestions. P.S. I am using windows compilation. May it be some platform specific modeller bug?

2 1

model ligand
by Bo Yang 31 Mar '07

31 Mar '07

Hello, Modeller: I try to model the ligand into my model by following the example of "Tutorial-2: Modeling ligands in the binding site'. First, I use a template and one of my model to build a alignment of the two. Then manually change the alignment to add "/.." to the end of the structures and sequence in the alignment. And change the number of residues of the structure file in the alignment. I then do the modeling using the modified alignment. But I keep getting the error message: modeller. error: check_a_337E> structure not read in I have checked that the structure files are all in the right path. I don't understand that why Modeller can't read the structure. I notice that the program generated two structure files ( all with xxx_fit) after the alignment. But these "xxx_fit" structures do not include the ligand. If I use these "xxx_fit" structures, there is no error message saying that "structure not read in", instead, it complain that "One or more atoms absent from MODEL". Since there is no ligand residue in such "xxx_fit" files. And if I manually add the ligand residue into the "xxx_fit", again, the modeller can't read the structure anymore. I have included the files used for modeling as attachments. I use mod 8v1. Thank you for help! Bo --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. _aln.pos 10 20 30 40 50 60 1PQ2-2C8Ahem KLPPGPTPLPIIGNMLQIDVKDICKSFTNFSKVYGPVFTVYFGMNPIVVFHGYEAVKEALIDNG 2c17mul1 ---------------------HMHNNFFKLQKKYGPIYSVRMGTKTTVIVGHHQLAKEVLI-KK 2c17 ---------------------HMHNNFFKLQKKYGPIYSVRMGTKTTVIVGHHQLAKEVLI-KK _consrvd * * *** * * * ** ** _aln.pos 70 80 90 100 110 120 1PQ2-2C8Ahem EEFSGRGN--SPISQRITKGLGIISSNG-KRWKEIRRFSL-TTLRNFGMGKRSIEDRVQEEAHC 2c17mul1 GKDFSGRPQMATLDIASNNRKGIAFADSGAHWQLHRRLAMATFALFKDGDQKLEKIICQEISTL 2c17 GKDFSGRPQMATLDIASNNRKGIAFADSGAHWQLHRRLAMATFALFKDGDQKLEKIICQEISTL _consrvd ** * ** * ** _aln.pos 130 140 150 160 170 180 190 1PQ2-2C8Ahem LVEELRKTKASPCDPTFILGCAPCNVICSVVFQKRFDYKDQNFLTLMKRFNENFRILNSPWIQV 2c17mul1 CDMLATHN-GQSIDISFPVFVAVTNVISLICFNTSYKN----GDPELNVIQNYNEGIID--NLS 2c17 CDMLATHN-GQSIDISFPVFVAVTNVISLICFNTSYKN----GDPELNVIQNYNEGIID--NLS _consrvd * * * *** * _aln.pos 200 210 220 230 240 250 1PQ2-2C8Ahem CNN------FPLLIDCFPGTHNKVLKNVALTRSYIREKVKEHQASLDVNNPRDFIDCFLIKMEQ 2c17mul1 KDSLVDLVPWLKIFP--NKTLEKLKSHVKIRNDLLNKILENYKEKFRS-DSITNMLDTLMQAKM 2c17 KDSLVDLVPWLKIFP--NKTLEKLKSHVKIRNDLLNKILENYKEKFRS-DSITNMLDTLMQAKM _consrvd * * * * _aln.pos 260 270 280 290 300 310 320 1PQ2-2C8Ahem EKDNQKSEF-------NIENLVGTVADLFVAGTETTSTTLRYGLLLLLKHPEVTAKVQEEIDHV 2c17mul1 NSDNGNAGPDQDSELLSDNHILTTIGDIFGAGVETTTSVVKWTLAFLLHNPQVKKKLYEEIDQN 2c17 NSDNGNAGPDQDSELLSDNHILTTIGDIFGAGVETTTSVVKWTLAFLLHNPQVKKKLYEEIDQN _consrvd ** * * * ** *** * ** * * * **** _aln.pos 330 340 350 360 370 380 1PQ2-2C8Ahem IGRHRSPCMQDRSH-MPYTDAVVHEIQRYSDLVPTGVPHAVTTDTKFRNYLIPKGTTIMALLTS 2c17mul1 VGFS-RTPTISDRNRLLLLEATIREVLRLRPVAPMLIPHKANVDSSIGEFAVDKGTEVIINLWA 2c17 VGFS-RTPTISDRNRLLLLEATIREVLRLRPVAPMLIPHKANVDSSIGEFAVDKGTEVIINLWA _consrvd * * * * * ** * *** * _aln.pos 390 400 410 420 430 440 1PQ2-2C8Ahem VLHDDKEFPNPNIFDPGHFLDKNGNFKKSD----YFMPFSAGKRICAGEGLARMELFLFLTTIL 2c17mul1 LHHNEKEWHQPDQFMPERFLN--PAGTQLISPSVSYLPFGAGPRSCIGEILARQELFLIMAWLL 2c17 LHHNEKEWHQPDQFMPERFLN--PAGTQLISPSVSYLPFGAGPRSCIGEILARQELFLIMAWLL _consrvd * ** * * * ** ** ** * * ** *** **** * _aln.pos 450 460 470 480 490 1PQ2-2C8Ahem QNFNLKSVDDLKNLNTTAVTKGIVSLPPSYQICFIPV-----/.. 2c17mul1 QRFDLEVPDDGQLPSLEGIP-KVVFLIDSFKVKIKVRQAWRE/-- 2c17 QRFDLEVPDDGQLPSLEGIP-KVVFLIDSFKVKIKVRQAWRE/.. _consrvd * * * ** * * *

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

modeller_usage April 2007