- modeller_usage - salilab.org

Opening files
by pbonar＠ualberta.ca 04 May '10

04 May '10

Hi, I am new to modeller, and very inexperienced in python. I am trying to complete the first tutorial and I keep getting this error: IOError: openf______E> Cannot open file pdb_95.pir: No such file or directory. I have downloaded and extracted the files needed for this tutorial, however from what I gather by this message, the program cannot find/or read these files. Is there somewhere special where I must save them, or some other name that I have to give them. Do I have to do something to the file in order for it to work. And if so what program do I download to read the file? Thank you for you help Pam

2 1

template quality selection criteria
by Thomas Evangelidis 28 Apr '10

28 Apr '10

Apart from sequence similarity to the target sequence and crystallographic resolution, someone told me I should also look to the electron density map info. Yet his english is not good and I haven't found yet the parameter he's referring to. Can anyone clarify what other parameters I should look to in order to select the best templates for modelling? thanks, Tom

3 2

Modeller 9v8 release
by Modeller Caretaker 27 Apr '10

27 Apr '10

The new version of Modeller, 9v8, 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 9v8 - the same license key will work. (It won't do any harm to reregister if you want to, though!) 9v8 is primarily a bugfix release relative to the last public release (9v7). Major user-visible changes include: # Silicon Graphics (IRIX) binaries are no longer provided. If you wish to use Modeller on an IRIX machine, please use the older 9v7 version. # Residues treated as BLK no longer have to be HETATM residues; they will be marked as ATOM if so defined in restyp.lib or in the template PDB (for example, DNA or RNA residues). automodel.nonstd_restraints() now builds restraints on both HETATM and BLK residues. # Bonds between BLK residues are now detected by a simple distance criterion and are restrained more strongly than other distances by automodel.nonstd_restraints(). # A new method Chain.join() allows chain breaks between chains to be removed. # Files compressed with 'xz' can now be read, provided that the 'xz' binary is available on your system. # The allow_alternates option to alignment.append() will now allow G in the alignment sequence to match any non-standard residue type in the PDB file which maps to G. This is useful if the alignment sequence is 'cleaned' as by sequence_db.read(). See the Modeller manual for a full change log: http://salilab.org/modeller/9v8/manual/node38.html If you encounter bugs in Modeller 9v8, please see http://salilab.org/modeller/9v8/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 and ticked the "notify me of new releases" box. 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

align3d.py
by saibal das 27 Apr '10

27 Apr '10

Dear modeller users, i have been trying to use the align3d.py script for modeller created homology model pdb files but is not working but is working for all pdb entries. is there any solution to this problem.

2 1

Re: [modeller_usage] Alignment errors model not running
by Daniel Fernandez 27 Apr '10

27 Apr '10

sorry i forgot to attach the target sequence... it's the fasta sequence of the 1ATG protein... On Mon, Apr 26, 2010 at 8:19 PM, Daniel Fernandez <dfernan(a)gmail.com> wrote: > Hi, > > Please help me with this error. I have been more than a week trying to > solve this issue and I still can't solve it. > > Let me explain my approach to use modeller. > > 1. First I search for templates against the pdb database > 2. I select as templates the one with low e-value and reasonable > similarity percentage > 3. I use clustalW (or TCoffee) to align the target and the selected > templates. > 4. I use modeller to model the target based on the TCoffee alignment > file and the PDB files. > > I do the whole pipeline but modeller works for some sequences but for most > of them it gives me the following error and at this point I am clueless on > how to solve it. Here I attach my input files to modeller in case someone > wants to take a look at them and help me solve this issue. > > INPUT: finalseq.pir (as in modeller format, i tried all different formats > here, I attach my last approach that was to only save PDB files with the > data from a specific chain...) > template PDB files (the PDB files with the actual chain) > target.fasta > > OUTPUT: error: > get_ran_648E> Alignment sequence not found in PDB file: 3 > 2H5Y_A.pdb > (You didn't specify the starting and ending residue numbers > and > chain IDs in the alignment, so Modeller tried to guess these > from > the PDB file.) > Suggestion: put in the residue numbers and chain IDs (see the > manual) and run again for more detailed diagnostics. > You could also try running with allow_alternates=True to > accept > alternate one-letter code matches (e.g. B to N, Z to Q). > Traceback (most recent call last): > File "testclean.py", line 18, in <module> > a.make() # do the homollogy modelling > File "/n/sw/modeller-9v7/modlib/modeller/automodel/automodel.py", line > 98, in make > self.homcsr(exit_stage) > File "/n/sw/modeller-9v7/modlib/modeller/automodel/automodel.py", line > 411, in homcsr > aln = self.read_alignment() > File "/n/sw/modeller-9v7/modlib/modeller/automodel/automodel.py", line > 401, in read_alignment > aln.append(file=self.alnfile, align_codes=self.knowns+[self.sequence]) > File "/n/sw/modeller-9v7/modlib/modeller/alignment.py", line 79, in > append > allow_alternates) > _modeller.SequenceMismatchError: get_ran_648E> Alignment sequence not found > in PDB file: 3 2H5Y_A.pdb (You didn't specify the starting and > ending residue numbers and chain IDs in the alignment, so Modeller tried to > guess these from the PDB file.) Suggestion: put in the residue numbers and > chain IDs (see the manual) and run again for more detailed diagnostics. You > could also try running with allow_alternates=True to accept alternate > one-letter code matches (e.g. B to N, Z to Q). > > I am completely clueless on where to look the starting and ending residue > numbers and chain IDs in the alignment, clustalW does not give me that > information at all so not sure where to look that info and if possible with > the approach I am using... > > Thanks, > > Daniel F. > -- Daniel F. Department of Statistics, Harvard University 1 Oxford Street, Cambridge, MA 02138

2 2

gaps in template alignment to query sequence in case of multidomain modelling
by saibal das 26 Apr '10

26 Apr '10

dear modeller users, i have created a multi domain model using modeller FAQ first method aligning each template to query sequence and arranging them in PIR format in multi alignment file. but template is not available for a large C terminal region of the model. Even template alignment to query has gap regions between each domains.The model is giving poor stereochemical properties. is there any solution to this problem. thanking you saibal das m.sc bioinformatics BIT mesra India.

2 1

update profile database for PDB
by Knut J Bjuland 24 Apr '10

24 Apr '10

How can I acces ans update the pdb seqeunce database or profile database to the current database in www.pdb.org Best regards Knut J

2 1

phi/psi angle restraint
by Armin Meier 23 Apr '10

23 Apr '10

Hi, I encountered a strange behavior, I dont understand yet. First, I replaced Modeller generated phi/psi dihedral constraints (group 25, physical.phi_psi_dihedral) in the rsr-file. In the corresponding cuser_form.c file, I get the phi and psi angle like this (in myform_eval): float phi = feat[0]; float psi = feat[1]; printf("phi=%f, psi=%f\n", phi, psi); Then Modeller is called. When comparing the printed phi/psi angles, I expected the very first ones (i.e. the first ones printed into the log-file, right at the start of optimization) to be the same as the phi/psi angles extracted from the *.ini file, because this is the starting point. But this isnt at all what I see. I hope, my description was clear enough Armin Meier

2 1

question about tutorial build_profile basic
by Knut J Bjuland 22 Apr '10

22 Apr '10

I have read through the basic tutorial and I have question about section 2 selecting template. Where I can I read what the other collums are used for and what kind of information do the provide. I is colloum 6 though 9 I am interest about. Best regards Knut J

2 1

(no subject)
by Davide Pirolli 22 Apr '10

22 Apr '10

Hello, <style type="text/css"> </style>I'm a PhD student and I'm using modeller version 9. I'd very glad if you could explain to me which is the solvation model used by modeller in the various steps (in particular in the simulated annealing refinement procedure, CG_minimization, MD etc.) and the temperatures at which SA is carried out in the high optimization level procedure. Many thanks in advance. Davide Pirolli Grazie a un gesto semplice puoi aiutare i malati del Policlinico "A. Gemelli", soprattutto nel campo delle cure palliative e della radioterapia oncologica e sintomatica, e puoi contribuire in prima persona alle iniziative promosse dal Centro di Ateneo per la solidarieta' internazionale e alla formazione di giovani meritevoli provenienti dai Paesi piÃ¹ bisognosi. Con questo messaggio istituzionale l'Ateneo dei cattolici italiani chiede un segno di amicizia e generosita', di cui molti Ti saranno riconoscenti. Dona il Tuo "5 x mille" all'Universita' Cattolica: codice fiscale 02133120150. Info: www.unicatt.it/5permille --- Le informazioni trasmesse sono destinate esclusivamente alla persona o alla societa' in indirizzo e sono da intendersi confidenziali e riservate. Ogni trasmissione, inoltro, diffusione o altro uso di queste informazioni a persone o societa' differenti dal destinatario e' proibita. Se ricevete questa comunicazione per errore, contattate il mittente e cancellate le informazioni da ogni computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use, of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you recived this in error please contact the sender and delete the material from any computer. ---

2 1