<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Apr 9, 2012, at 4:41 PM, Brad Ridder wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">Hi Scott and Eric,<br></span></span></blockquote><div><br></div><div><br></div>Hi Brad,</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">Okay, so I suppose the problem was not using the latest version of Chimera when running dockprep.py. I now correctly get "dp.mol2" written to the working directory.<br>Now, I am just confused to where this puts me in the 4-step process. In the tutorial, this .mol2 file should correspond to everything up to and including step 1g in the tutorial.<br></span></span></blockquote><div><br></div>I think that's correct.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">dp.mol2 has hydrogens in it, which need to be stripped away.<br><br>I have a some new questions then:<br><br>1. I need to take dp.mol2, and make rec_noH.pdb from it. Is there a quick, easy way to do this with Chimera? e.g. open dp.mol2, strip the hydrogens, and save the results as a .pdb file? I see this commented-out code from ligprep.py could be useful:<br><br>#runCommand('select H')<br>#runCommand('delete sel')<br><br>And also this "write" command:<br><br><a href="http://www.cgl.ucsf.edu/chimera/current/docs/UsersGuide/midas/write.html#options">http://www.cgl.ucsf.edu/chimera/current/docs/UsersGuide/midas/write.html#options</a><br><br>But how do I get python to use that "write" command? I don't understand why there is a "write" command here, but there is a totally separate python module "WriteMol2" just for writing .mol2 files. There is no "WritePDB."<br></span></span></blockquote><div><br></div>You could just add some lines to dockprep.py script to also write out the PDB file, keeping in mind that the runCommand function can be used to run any Chimera command. So you would probably add lines like these:</div><div><br></div><div>from chimera import runCommand</div><div>runCommand('select H')</div><div>runCommand('delete sel')</div><div>runCommand('write 0 rec_noH.pdb')</div><div><br></div><div>Alternatively you could write it as a separate script that opened the dp.mol2 file from the previous script if that was better for your workflow.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">2. I looked at the ligprep.py script, but I don't understand how to run it yet. First, where do you specify the input file? And what format does it have to be in? Also, there is some commented out code up top:<br><br># $HOME/chimera/1.2470/bin/chimera --nogui ligprep.py<br><br>Is that just the command for running it from the terminal? It has no inputs specified, so the input file appears to be "start.sdf". Am I understanding this correctly? I am just confused because in the original message, the person wanted to loop over many files, but as this ligprep.py script is written, I don't see how any looping could be done since the input file is hard-coded to be "start.sdf".<br></span></span></blockquote><div><br></div>If you are going to use Scott's ligprep.py script, it looks like you would need to use it in a shell script that copies the input to start.sdf and then copies the output from start.mol2. In csh syntax, something like this:</div><div><br></div><div>foreach sdf in (*.sdf)</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cp $sdf start.sdf</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>chimera --nogui ligprep.py</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cp start.mol $sdf:r.mol2</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">3. In the case of 2H4F, I have more than one ligand. I want to keep the large peptide fixed (it has a long lysine pointing into the center of the enzyme), but NAD is what I want to dock. How would I tell Chimera/Python to choose NAD for ligand preparation?<br></span></span></blockquote><div><br></div>Strip everything but NAD from the system to prep it as a ligand. Treat the peptide as part of the receptor, not as a ligand.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">4. The module "chimera" needs to be imported. However, I have three versions of Chimera on my computer: 1.5.3, 1.6, and 1.6.1. How will the Python import command know to go into the 1.6.1 directory to find the correct, up-to-date module files? Just adding the /chimera/share folder to the python path should work, right?<br></span></span></blockquote><div><br></div>You run a Chimera Python script with "chimera --nogui" not with the system Python. "chimera --nogui" will have the correct module paths.</div><div><br><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: verdana, sans-serif; font-size: large; ">5. Is there a special procedure for deleting the other Chimera versions, or just trash them?<br></span></span></blockquote><br></div><div>On Windows there is a de-installer. On the Mac, just drag them to the Trash.</div><div><br></div><div>--Eric</div><div><br></div><br></body></html>