Zoey's way of retrodocking: Difference between revisions

From DISI
Jump to navigation Jump to search
(Created page.)
 
mNo edit summary
Line 17: Line 17:
'''Split your protein using ChimeraX.''' Separate out the xtal ligand from the rest of the structure. Save as `rec_maestro.pdb` and `xtal_maestro.pdb`. Upload these files to the previously created preparation directory on cluster2.
'''Split your protein using ChimeraX.''' Separate out the xtal ligand from the rest of the structure. Save as `rec_maestro.pdb` and `xtal_maestro.pdb`. Upload these files to the previously created preparation directory on cluster2.


'''Prepare your protein using prepare_protein.py.''' See the documentation [[Protein Target Preparation (before Blastermaster)|here]]. My own fork is currently identical to Andrii's script, but I intend to clean up some of the pathways eventually. Run:
'''Prepare your protein using prepare_protein.py.''' See the documentation [[Protein Target Preparation (before Blastermaster)|here]]. My own fork is currently identical to Andrii's script, but I intend to clean up some of the pathways eventually. Run the following:


   python /nfs/home/zdingman/scripts/dockopt/prepare_protein.py --rec rec_maestro.pdb --xtal xtal_maestro.pdb
   python /nfs/home/zdingman/scripts/dockopt/prepare_protein.py --rec rec_maestro.pdb --xtal xtal_maestro.pdb
Line 23: Line 23:
== Blastermaster ==
== Blastermaster ==


Assuming you're still in your preparation folder:
'''Change your directory.''' Assuming you're still in your preparation folder:


   cp rec.pdb ../blaster ; cp working/rec.crg.pdb ../blaster ; cp xtal-lig.pdb ../blaster
   cp rec.pdb ../blaster ; cp working/rec.crg.pdb ../blaster ; cp xtal-lig.pdb ../blaster
   cd blaster
   cd blaster


This is verbatim from Read-The-Dock-Docs:
'''Source the environment and initialize the job.''' This is verbatim from Read-The-Dock-Docs:


   source /mnt/nfs/soft/dock/versions/dock385/env.sh
   source /mnt/nfs/soft/dock/versions/dock385/env.sh
Line 34: Line 34:
   cd blastermaster_job
   cd blastermaster_job


Make any edits necessary to your blastermaster_config.yaml file now. Typically we adjust the bump_max from 10.0 to 100.0.
'''Modify blastermaster_config.yaml.''' Make any edits necessary to your blastermaster_config.yaml file now. Typically we adjust the bump_max from 10.0 to 100.0.
 
'''Run the job.''' Run the following:


   pydock3 blastermaster - run
   pydock3 blastermaster - run

Revision as of 21:04, 15 October 2026

The instructions detailed here are my adaptation of the Read-The-Dock-Docs standard procedures, which can be found here. The Docs don't fully cover preparation on cluster2 (i.e., gimel), and this wiki page serves to keep track of my own scripts and post-processing files.

Directory preparation

We'll make a directory for your protein structure, with subdirectories for each individual step.

 mkdir [protein_name]
 cd [protein_name]
 mkdir preparation
 mkdir blaster
 mkdir retrodocking

Initial protein preparation

Use Maestro to prepare the protein. Cap termini, protonate, minimize hydrogens (but not heavy atoms!), etc. Save as a pdb file: `rec_and_xtal_maestro.pdb1

Split your protein using ChimeraX. Separate out the xtal ligand from the rest of the structure. Save as `rec_maestro.pdb` and `xtal_maestro.pdb`. Upload these files to the previously created preparation directory on cluster2.

Prepare your protein using prepare_protein.py. See the documentation here. My own fork is currently identical to Andrii's script, but I intend to clean up some of the pathways eventually. Run the following:

 python /nfs/home/zdingman/scripts/dockopt/prepare_protein.py --rec rec_maestro.pdb --xtal xtal_maestro.pdb

Blastermaster

Change your directory. Assuming you're still in your preparation folder:

 cp rec.pdb ../blaster ; cp working/rec.crg.pdb ../blaster ; cp xtal-lig.pdb ../blaster
 cd blaster

Source the environment and initialize the job. This is verbatim from Read-The-Dock-Docs:

 source /mnt/nfs/soft/dock/versions/dock385/env.sh
 pydock3 blastermaster - new
 cd blastermaster_job

Modify blastermaster_config.yaml. Make any edits necessary to your blastermaster_config.yaml file now. Typically we adjust the bump_max from 10.0 to 100.0.

Run the job. Run the following:

 pydock3 blastermaster - run

Retrodocking - job launching

Below are the steps for running any sort of dock job on cluster2 -- in this case, a retrodocking job. However, the procedure is identical for any larger job you may wish to submit.

(placeholder)

Retrodocking - analysis

(placeholder)