modeller_usage October 2008

modeller_usage@salilab.org

12 participants
16 discussions

Modelling an oligomer
by Lucas Bleicher 17 Oct '08

17 Oct '08

I want to model a heterotrimer consisting of proteins A, B and C, where the structure of the A:B complex is already known, and C should be modelled. There is a known structure of another structure made of proteins D, E and F, where D and E are homologous to A:B (and can be easily spatially superposed) and F is homologous to C. Do I have to work with restraints or is there a way to set a PIR file using the A:B and D:E:F complexes as "knowns" so that Modeller can assume that it must build an A:B:C complex so that A:B would be in the equivalent positions to D:E (but should of course be nearly identical to the A:B x-ray structure more than the D:E structure, since A:B is the real thing) and C must be modelled using F as template and be in the position it would occupy in the D:E:F structure? To add insult to injury, although C and F are homologous, there is a better template, G, for it in terms of identity and alignment size. So the ideal solution to the problem would be: A trimer consisting of A:B:C where A and B are knowns, C is modelled against G, and the A:B is positioned against D:E and the C model against G is positioned against F in the known D:E:F structure. I hope my message is not too confusing... Lucas P.S.: I already tried to separately model only the protein C against G and then using SSM to superpose the C model against F and the A:B complex against D:E, but that would produce some serious clashes, so I really need to build the whole thing on modeller. Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua cara @ymail.com ou @rocketmail.com. http://br.new.mail.yahoo.com/addresses

2 1

Modeller 9v5 release
by Modeller Caretaker 16 Oct '08

16 Oct '08

The new version of Modeller, 9v5, is now available for download! Please see the download page at http://salilab.org/modeller/ for more information. If you have a license key for Modeller 8 or 9, there is no need to reregister for Modeller 9v5 - the same license key will work. (It won't do any harm to reregister if you want to, though!) 9v5 is primarily a bugfix release relative to the last public release (9v4). Major user-visible changes include: # New normalized DOPE assessment method, which returns a Z-score, and is thus comparable between different proteins. # PDB atom files are now also looked for in PDB-style subdirectories (the first two characters after the digit); e.g. 1abc is searched for in the 'ab' subdirectory, pdb4xyz.ent in the 'xy' subdirectory. # Libraries updated to correctly read and write remediated RNA and DNA, some other HETATMs (e.g. ions) and to use the new hydrogen names, in PDB v3. # Modeller now outputs new-style PDBs, with the element in columns 77 and 78, rather than older-style PDB which has a sequence number in this position. See the Modeller manual for a full change log: http://salilab.org/modeller/9v5/manual/node38.html If you encounter bugs in Modeller 9v5, please see http://salilab.org/modeller/9v5/manual/node10.html for information on how to report them. Note: you are receiving this email either because you subscribed to the modeller_usage mailing list, or you provided this address when you requested a Modeller license. In the latter case, if you no longer wish to receive announcements of new Modeller releases, simply reply to this email and let us know. Ben Webb, Modeller Caretaker -- modeller-care(a)salilab.org http://www.salilab.org/modeller/ Modeller mail list: http://salilab.org/mailman/listinfo/modeller_usage

1 0

Using of a template with the coordinates of the Calpha atoms only.
by Jean-Paul Becker 16 Oct '08

16 Oct '08

Dear Modeller users, I constructed a model of a protein using a template which contains only the Calpha trace. Due to a question of a reviewer of the article i submitted for publication, i am seeking for precisions on how the Calpha trace is rebuilt to atomic resolution and then made into the model. I guess these steps are performed by the functions: model.generate_topology() and/or Restraints.make(), but i do not understand how modeller generates all the essential restraints to build the model when almost all the atoms of the template are missing except the Calpha. Does these restraints come from a library ? In this case, how is this library built ? I did not mange to find many details concerning this point in the manual, so i would really appreciate if anyone could give me some explanations. Many thanks in advance for your time and knowledge. JPB -- Jean-Paul BECKER Structure et Fonction des Membranes Biologiques (SFMB) Centre de Biologie Structurale et de Bioinformatique (CBSB) Faculté des Sciences Université Libre de Bruxelles Campus de la Plaine CP 206/2 Boulevard du Triomphe 1050 BRUXELLES BELGIQUE

2 1

Is there anything wrong with my configuration file?My models look so strange
by wayj86 wayj86 09 Oct '08

09 Oct '08

Hi all, Two days ago I wanted to model an antibody with specifying the CDR regions.Here is my configuation file: # Homology modeling by the automodel class from modeller import * # Load standard Modeller classes from modeller.automodel import * # Load the automodel class # Redefine the special_patches routine to include the additional disulfides # (this routine is empty by default): class mymodel(loopmodel): def special_patches(self, aln): # A disulfide between residues 22 and 96: self.patch(residue_type='DISU', residues=(self.residues['22'], self.residues['95'])) self.patch(residue_type='DISU', residues=(self.residues['158'], self.residues['228'])) def select_loop_atoms(self): return selection(self.residue_range('26','33'),self.residue_range('51','57'),self.residue_range('96','110'),self.residue_range('162','172'),self.residue_range('190','192'),self.residue_range('229','237')) log.verbose() # request verbose output env = environ() # create a new MODELLER environment to build this model in # directories for input atom files env.io.atom_files_directory = './:../atom_files' a = mymodel(env, alnfile = '3.ali', # alignment filename knowns = ('HL','y','121','113'), # codes of the templates sequence = '6b4', loop_assess_methods=assess.DOPE) # code of the target a.starting_model= 1 # index of the first model a.ending_model = 8 # index of the last model # (determines how many models to calculate) a.loop.starting_model=1 a.loop.ending_model=2 a.make() # do the actual homology modeling I don't know what is wrong with it but the models it built were so strange,I can see some breakpoints in the structures. However,if I delete the sentences for loops specifying,the breakpoints would disappear. # Homology modeling by the automodel class from modeller import * # Load standard Modeller classes from modeller.automodel import * # Load the automodel class # Redefine the special_patches routine to include the additional disulfides # (this routine is empty by default): class mymodel(loopmodel): def special_patches(self, aln): # A disulfide between residues 22 and 96: self.patch(residue_type='DISU', residues=(self.residues['22'], self.residues['95'])) self.patch(residue_type='DISU', residues=(self.residues['158'], self.residues['228'])) log.verbose() # request verbose output env = environ() # create a new MODELLER environment to build this model in # directories for input atom files env.io.atom_files_directory = './:../atom_files' a = mymodel(env, alnfile = '3.ali', # alignment filename knowns = ('HL','y','121','113'), # codes of the templates sequence = '6b4') a.starting_model= 1 # index of the first model a.ending_model = 8 # index of the last model # (determines how many models to calculate) a.make() # do the actual homology modeling So could you please tell me how can I specify the CDR loops correctly?Thank you very much for any help. Best wishes, Stanley -- The future is now!

2 1

radii.lib
by Joaquim Rui Rodrigues 09 Oct '08

09 Oct '08

Dear Modellers, I am trying to model a non-standard residue, with non-standard lib files, by following the examples in the wiki page "Using non-standard parameter files". This works fine for toplib and parlib. However, I also need to read my extended versions of radii.lib and radii14.lib. Here is the relevant part of my script: env = environ(restyp_lib_file='/Users/jrui/modeller/LIBS/restyp.lib') class MyModel(automodel): .............. a = MyModel(env, ....) a.toplib = '/Users/jrui/modeller/LIBS/top_heav.lib' a.parlib = '/Users/jrui/modeller/LIBS/par.lib' I tried the obvious a.radlib = '/Users/jrui/modeller/LIBS/radii.lib' but I get: runcmd_____W>: creation of new member 'radlib' in <Model containing 0 chains, 0 residues, and 0 atoms>: possible typo! I searched for toplib and parlib in the manual but could not anything about these keywords. How can I tell modeller to read my radii files? Many thanks, Rui Rodrigues -- Webmail ESTG de Leiria (http://webmail.estg.ipleiria.pt)

2 1

PCA problem
by Julien Pele 06 Oct '08

06 Oct '08

Dear all, My question deals with the command which performs Principal Component Analysis (PCA). I use an input matrix of pairwise distances calculated from percentage residue identity of a multiple protein sequence alignment. I executed the following script : ################# env = environ() aln = alignment(env, file='alignment.pir') aln.id_table(matrix_file='id.mat') env.principal_components(matrix_file='id.mat', file='alignment_mod.princ') ################# The file 'alignment_mod.princ' contains projected coordinates of the first two principal components. I compared these results with other programs which hold PCA and go by the same input matrix. For instance, ade4, a package of the R software. I executed the following commands under R : ################# require (ade4) x <- read.table("id.mat", sep="") y <- dudi.pca(x, scan = F, nf = 2) write.table(y$li, file = "alignment_ade4.princ") ################# The file 'alignment_ade4.princ' also contains projected coordinates of the first two principal components. However, the coordinates acquired with these two softwares are not the same. I would like to know if the PCA command of Modeller uses internal procedures which could explain this disagreement ? How does the treatment of input matrix work with Modeller ? Any help on this will be greatly appreciated. Best regards, Julien

1 0

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 October 2008