<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Stefan</id>
	<title>DISI - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.docking.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Stefan"/>
	<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Special:Contributions/Stefan"/>
	<updated>2026-05-25T02:51:01Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.1</generator>
	<entry>
		<id>http://wiki.docking.org/index.php?title=How_to_dock_in_DOCK3.8&amp;diff=13241</id>
		<title>How to dock in DOCK3.8</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=How_to_dock_in_DOCK3.8&amp;diff=13241"/>
		<updated>2021-02-03T00:46:15Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;How to dock in DOCK 3.8.0&lt;br /&gt;
&lt;br /&gt;
== Differences from DOCK.3.7 ==&lt;br /&gt;
&lt;br /&gt;
DOCK 3.8.0 can be interrupted safely and restarted, which allows more flexibility when submitting docking jobs.&lt;br /&gt;
&lt;br /&gt;
For example, you could set QSUB_ARGS=&amp;quot;-l s_rt=00:05:00 -l h_rt=00:07:00&amp;quot; (or SBATCH_ARGS=&amp;quot;--time=00:07:00&amp;quot;)&lt;br /&gt;
so that each docking job will only run for 5 minutes before being interrupted. The new subdock.bash script allows submitting the same set of jobs multiple times, until they are all complete.&lt;br /&gt;
&lt;br /&gt;
== Running the Script ==&lt;br /&gt;
&lt;br /&gt;
New subdock scripts are here:&lt;br /&gt;
&lt;br /&gt;
$DOCKBASE/docking/submit/sge/subdock.bash&lt;br /&gt;
$DOCKBASE/docking/submit/slurm/subdock.bash&lt;br /&gt;
&lt;br /&gt;
subdock.bash requires a number of environmental variables to be passed as arguments.&lt;br /&gt;
&lt;br /&gt;
=== Required Arguments ===&lt;br /&gt;
&lt;br /&gt;
==== INPUT_SOURCE ====&lt;br /&gt;
&lt;br /&gt;
INPUT_SOURCE should be either:&lt;br /&gt;
&lt;br /&gt;
a) A directory containing one or more db2.tgz files OR&lt;br /&gt;
&lt;br /&gt;
b) A text file containing a list of paths to db2.tgz files&lt;br /&gt;
&lt;br /&gt;
==== EXPORT_DEST ====&lt;br /&gt;
&lt;br /&gt;
A directory on the NFS where you would like your docking output to end up. If the directory does not exist, the script will try to create it.&lt;br /&gt;
&lt;br /&gt;
==== DOCKEXEC ====&lt;br /&gt;
&lt;br /&gt;
An NFS path to a DOCK binary executable (NOT a wrapper script).&lt;br /&gt;
&lt;br /&gt;
==== DOCKFILES ====&lt;br /&gt;
&lt;br /&gt;
An NFS path to the dockfiles (INDOCK, spheres, receptor files, grids, etc.) being used for this docking run. The dockfiles directory should be named uniquely, to avoid confusion with other dockfiles other users may be running.&lt;br /&gt;
&lt;br /&gt;
=== Optional Arguments ===&lt;br /&gt;
&lt;br /&gt;
==== SHRTCACHE ====&lt;br /&gt;
&lt;br /&gt;
The directory DOCK will perform it&#039;s work in. Files saved to this directory will be deleted once the docking job has concluded. By default this is /dev/shm.&lt;br /&gt;
&lt;br /&gt;
==== LONGCACHE ====&lt;br /&gt;
&lt;br /&gt;
The directory DOCK will store files that are shared between multiple docking jobs. Files saved to this directory (dockexec and dockfiles) will persist until they are deleted. By default this directory is /tmp. &lt;br /&gt;
&lt;br /&gt;
Beware of using the default SHRTCACHE or LONGCACHE settings on large clusters.&lt;br /&gt;
&lt;br /&gt;
==== SBATCH_ARGS ====&lt;br /&gt;
&lt;br /&gt;
Additional arguments to provide to slurm&#039;s sbatch, if using the slurm version of subdock.bash.&lt;br /&gt;
&lt;br /&gt;
==== QSUB_ARGS ====&lt;br /&gt;
&lt;br /&gt;
Additional arguments to provide to sge&#039;s qsub, if using the sge version of subdock.bash&lt;br /&gt;
&lt;br /&gt;
=== Example: Running a lot of docking jobs ===&lt;br /&gt;
&lt;br /&gt;
* 1. set up sdi files&lt;br /&gt;
 mkdir sdi&lt;br /&gt;
 export sdi=sdi&lt;br /&gt;
 ls /wynton/group/bks/zinc-22/H19/H19P0??/*.db2.tgz &amp;gt; $sdi/h19p0.in&lt;br /&gt;
 ls /wynton/group/bks/zinc-22/H19/H19P1??/*.db2.tgz &amp;gt; $sdi/h19p1.in&lt;br /&gt;
 ls /wynton/group/bks/zinc-22/H19/H19P2??/*.db2.tgz &amp;gt; $sdi/h19p2.in&lt;br /&gt;
 ls /wynton/group/bks/zinc-22/H19/H19P3??/*.db2.tgz &amp;gt; $sdi/h19p3.in&lt;br /&gt;
 and so on&lt;br /&gt;
&lt;br /&gt;
* 2. set up INDOCK and dockfiles. rename dockfiles to dockfiles.$indockhash. On some nodes, the shasum command is called by sha1sum. Ultimately, renaming the dockfiles to a unique dockfiles is key. &lt;br /&gt;
 bash&lt;br /&gt;
 indockhash=$(cat INDOCK | shasum | awk &#039;{print substr($1, 1, 12)}&#039;)&lt;br /&gt;
&lt;br /&gt;
* 3. super script:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;&lt;br /&gt;
export DOCKBASE=/wynton/group/bks/work/jji/DOCK&lt;br /&gt;
export DOCKFILES=$WORKDIR/dockfiles.21751f1bb16b&lt;br /&gt;
export DOCKEXEC=$DOCKBASE/docking/DOCK/bin/dock64&lt;br /&gt;
#export SHRTCACHE=/dev/shm # default&lt;br /&gt;
export SHRTCACHE=/scratch&lt;br /&gt;
#export LONGCACHE=/scratch # default&lt;br /&gt;
export QSUB_ARGS=&amp;quot;-l s_rt=00:28:00 -l h_rt=00:30:00 -l mem_free=2G&amp;quot;&lt;br /&gt;
&lt;br /&gt;
for i in  sdi/*.in  ; do&lt;br /&gt;
        export k=$(basename $i .in)&lt;br /&gt;
	echo k $k&lt;br /&gt;
	export INPUT_SOURCE=$PWD/$i&lt;br /&gt;
	export EXPORT_DEST=$PWD/output/$k&lt;br /&gt;
	$DOCKBASE/docking/submit/sge/subdock.bash&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
# 3a. to run for first time&lt;br /&gt;
 sh super&lt;br /&gt;
&lt;br /&gt;
# 4. how to restart (to make sure complete, iterate until complete)&lt;br /&gt;
&lt;br /&gt;
 sh super&lt;br /&gt;
&lt;br /&gt;
# 5. check which output is valid (and broken or incomplete output)&lt;br /&gt;
&lt;br /&gt;
# 6. extract all blazing fast&lt;br /&gt;
&lt;br /&gt;
# 7. extract mol2&lt;br /&gt;
&lt;br /&gt;
more soon, under active development, Jan 28.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Flexible_Docking:_tarting_and_thin_spheres&amp;diff=13162</id>
		<title>Flexible Docking: tarting and thin spheres</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Flexible_Docking:_tarting_and_thin_spheres&amp;diff=13162"/>
		<updated>2020-12-31T02:14:14Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;written by Stefan Gahbauer 12/30/2020&lt;br /&gt;
&lt;br /&gt;
Weighted flexible docking as described in Fischer &#039;&#039;et al.&#039;&#039;, Nat. Chem., 2014 [https://www.nature.com/articles/nchem.1954], is implemented in DOCK3.7, however, fine-tuning docking grids using tarting or thin spheres was not possible with the common scripts used for rigid docking.&lt;br /&gt;
&lt;br /&gt;
== Run flexible blastermaster on protonated rec.crg.pdb including tarted residues ==&lt;br /&gt;
&lt;br /&gt;
DOCKBASE with adapted blastermaster_flex function:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/DOCK-3.7.4-1228&lt;br /&gt;
&lt;br /&gt;
This version cannot be used to protonate rec.pdb, rec.crg.pdb containing protonated flexible states must be prepared before.&lt;br /&gt;
&lt;br /&gt;
You can find an example for AmpC with tarted, flexible GLN120 here:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC&lt;br /&gt;
&lt;br /&gt;
Run blastermaster for flexible grid generation:&lt;br /&gt;
&lt;br /&gt;
     python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/DOCK-3.7.4-1228/proteins/blastermaster/blastermaster.py &lt;br /&gt;
            --addNOhydrogensflag -v -f --flexiblePenaltyM=2.0 --flexibleResidues=120 &lt;br /&gt;
            --chargeFile=&amp;quot;/nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC/amb.crg.oxt&amp;quot; &lt;br /&gt;
            --vdwprottable=&amp;quot;/nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC/prot.table.ambcrg.ambH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will generate INDOCK, dockfiles for flexible docking, flexible.explanation.txt and part.explanation.txt.&lt;br /&gt;
&lt;br /&gt;
== Thin sphere scan ==&lt;br /&gt;
&lt;br /&gt;
After the initial grids are computed with blastermaster, thin spheres can be introduced by using the following script:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0001_generate_ES_LD_generation_flexible.py&lt;br /&gt;
&lt;br /&gt;
This script is based on the rigid-docking thin sphere scan by Reed: [http://wiki.docking.org/index.php/How_to_do_parameter_scanning]&lt;br /&gt;
A few new options were added for flexible thin sphere scans:&lt;br /&gt;
&lt;br /&gt;
     usage: new_0001_generate_ES_LD_generation_flexible.py [-h]&lt;br /&gt;
     &lt;br /&gt;
     This is a sphere scan directory generator script. This script requires that&lt;br /&gt;
     you provide the full path to your original blastermaster directory that you&lt;br /&gt;
     want to run a sphere scan on. This looks like: python&lt;br /&gt;
     new_0001_generate_ES_LD_combine.py --path&lt;br /&gt;
     /mnt/nfs/blah/work/yourName/blah/DOCKprep/ Other options include specifying&lt;br /&gt;
     the: 1) DMS density (--dms) 2) electrostatic thin sphere radii (--es_rad) 3)&lt;br /&gt;
     ligand desolvation sphere radii (--ld_rad) 4) distance of spheres to your&lt;br /&gt;
     xtal-lig.pdb (--xdist) 5) Grid IDs (--flexgrids) 6) Ground state grid&lt;br /&gt;
     (--ground_state)&lt;br /&gt;
     &lt;br /&gt;
     optional arguments:&lt;br /&gt;
       -h, --help            show this help message and exit&lt;br /&gt;
       -p ORI_PATH, --path ORI_PATH&lt;br /&gt;
                             Full path of the original blastermaster directory,&lt;br /&gt;
                             e.g. /mnt/nfs/work/asdf/asdf/asdf/&lt;br /&gt;
       -d DMS, --dms DMS     DMS Density. The higher the number, the more dense the&lt;br /&gt;
                             molecular surface is. 10.0 is default to ensure that&lt;br /&gt;
                             the smaller radii spheres sufficiently cover the&lt;br /&gt;
                             protein surface. If your spheres have larger radii or&lt;br /&gt;
                             if you are using small radii for ES spheres and QNIFFT&lt;br /&gt;
                             fails, this value can be decreased to 1.0.&lt;br /&gt;
       -es ES_RAD [ES_RAD ...], --es_rad ES_RAD [ES_RAD ...]&lt;br /&gt;
                             Radius of Electrostatic spheres. &lt;br /&gt;
                             Default is 1.0, 1.3, 1.5, 1.7, 1.9&lt;br /&gt;
       -ld LD_RAD [LD_RAD ...], --ld_rad LD_RAD [LD_RAD ...]&lt;br /&gt;
                             Radius of ligand desolvation spheres. &lt;br /&gt;
                             Default is 0.1, 0.2, 0.3, 0.4, 0.5&lt;br /&gt;
       -xd XDIST, --xdist XDIST&lt;br /&gt;
                             Distance thin spheres can be from xtal-lig.pdb.&lt;br /&gt;
                             Default is 2 Angstroms&lt;br /&gt;
       &#039;&#039;&#039;-fg GNUM [GNUM ...], --flexgrids GNUM [GNUM ...]&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Alternative conformation names. E.g. A,B,C&#039;&#039;&#039;&lt;br /&gt;
       &#039;&#039;&#039;-gs GROUND_STATE, --ground_state GROUND_STATE&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Ground state conformation name. E.g. A&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
      python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0001_generate_ES_LD_generation_flexible.py &lt;br /&gt;
             -p /nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC &lt;br /&gt;
             -d 5 -es 1.0 1.5 1.9 -ld 0.4 0.6 0.8 -xd 4 &lt;br /&gt;
             -fg A B C -gs A&lt;br /&gt;
&lt;br /&gt;
This will take a few minutes (code is still being optimized).&lt;br /&gt;
&lt;br /&gt;
Once the girds are calculated, dockfiles for different thin sphere combination need to be generated using the following script:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0002_combine_es_ld_grids_into_combos_flexible.py&lt;br /&gt;
&lt;br /&gt;
     usage: new_0002_combine_es_ld_grids_into_combos_flexible.py&lt;br /&gt;
       [-h] -p ORI_PATH -fg GNUM [GNUM ...] -gs GROUND_STATE&lt;br /&gt;
     &lt;br /&gt;
     This is a sphere scan directory generator script. This script requires that&lt;br /&gt;
     you provide the full path to your original blastermaster directory that you&lt;br /&gt;
     want to run a sphere scan on. This looks like: python&lt;br /&gt;
     new_0002_combine_ES_LD.py --path /mnt/nfs/blah/work/yourName/blah/DOCKprep/&lt;br /&gt;
     --flexgrids A B C --ground_state A&lt;br /&gt;
     &lt;br /&gt;
     optional arguments:&lt;br /&gt;
       -h, --help            show this help message and exit&lt;br /&gt;
       -p ORI_PATH, --path ORI_PATH&lt;br /&gt;
                             Full path of the original blastermaster directory,&lt;br /&gt;
                             e.g. /mnt/nfs/work/asdf/asdf/asdf/&lt;br /&gt;
       &#039;&#039;&#039;-fg GNUM [GNUM ...], --flexgrids GNUM [GNUM ...]&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Alternative conformation names. E.g. A,B,C&#039;&#039;&#039;&lt;br /&gt;
       &#039;&#039;&#039;-gs GROUND_STATE, --ground_state GROUND_STATE&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Ground state conformation name. E.g. A&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
     python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0002_combine_es_ld_grids_into_combos_flexible.py &lt;br /&gt;
            -p /nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC &lt;br /&gt;
            -fg A B C -gs A&lt;br /&gt;
&lt;br /&gt;
This will generate combo_directories containing flexible docking grids.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Flexible_Docking:_tarting_and_thin_spheres&amp;diff=13161</id>
		<title>Flexible Docking: tarting and thin spheres</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Flexible_Docking:_tarting_and_thin_spheres&amp;diff=13161"/>
		<updated>2020-12-31T02:00:32Z</updated>

		<summary type="html">&lt;p&gt;Stefan: Created page with &amp;quot;written by Stefan Gahbauer 12/30/2020  Weighted flexible docking as described in Fischer &amp;#039;&amp;#039;et al.&amp;#039;&amp;#039;, Nat. Chem., 2014 [https://www.nature.com/articles/nchem.1954], is implemen...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;written by Stefan Gahbauer 12/30/2020&lt;br /&gt;
&lt;br /&gt;
Weighted flexible docking as described in Fischer &#039;&#039;et al.&#039;&#039;, Nat. Chem., 2014 [https://www.nature.com/articles/nchem.1954], is implemented in DOCK3.7, however, fine-tuning docking grids using tarting or thin spheres was not possible with the common scripts used for rigid docking.&lt;br /&gt;
&lt;br /&gt;
== Run flexible blastermaster on protonated rec.crg.pdb including tarted residues ==&lt;br /&gt;
&lt;br /&gt;
DOCKBASE with adapted blastermaster_flex function:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/DOCK-3.7.4-1228&lt;br /&gt;
&lt;br /&gt;
This version cannot be used to protonate rec.pdb, rec.crg.pdb containing protonated flexible states must be prepared before.&lt;br /&gt;
&lt;br /&gt;
You can find an example for AmpC with tarted, flexible GLN120 here:&lt;br /&gt;
&lt;br /&gt;
     /nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC&lt;br /&gt;
&lt;br /&gt;
Run blastermaster for flexible grid generation:&lt;br /&gt;
&lt;br /&gt;
     python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/DOCK-3.7.4-1228/proteins/blastermaster/blastermaster.py &lt;br /&gt;
            --addNOhydrogensflag -v -f --flexiblePenaltyM=2.0 --flexibleResidues=120 &lt;br /&gt;
            --chargeFile=&amp;quot;/nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC/amb.crg.oxt&amp;quot; &lt;br /&gt;
            --vdwprottable=&amp;quot;/nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC/prot.table.ambcrg.ambH&amp;quot;&lt;br /&gt;
&lt;br /&gt;
This will generate INDOCK, dockfiles for flexible docking, flexible.explanation.txt and part.explanation.txt.&lt;br /&gt;
&lt;br /&gt;
== Thin sphere scan ==&lt;br /&gt;
&lt;br /&gt;
After the initial grids are computed with blastermaster, thin spheres can be introduced by using the following script:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0001_generate_ES_LD_generation_flexible.py&lt;br /&gt;
&lt;br /&gt;
This script is based on the rigid-docking thin sphere scan by Reed: [http://wiki.docking.org/index.php/How_to_do_parameter_scanning]&lt;br /&gt;
A few new options were added for flexible thin sphere scans:&lt;br /&gt;
&lt;br /&gt;
     usage: new_0001_generate_ES_LD_generation_flexible.py [-h]&lt;br /&gt;
     &lt;br /&gt;
     This is a sphere scan directory generator script. This script requires that&lt;br /&gt;
     you provide the full path to your original blastermaster directory that you&lt;br /&gt;
     want to run a sphere scan on. This looks like: python&lt;br /&gt;
     new_0001_generate_ES_LD_combine.py --path&lt;br /&gt;
     /mnt/nfs/blah/work/yourName/blah/DOCKprep/ Other options include specifying&lt;br /&gt;
     the: 1) DMS density (--dms) 2) electrostatic thin sphere radii (--es_rad) 3)&lt;br /&gt;
     ligand desolvation sphere radii (--ld_rad) 4) distance of spheres to your&lt;br /&gt;
     xtal-lig.pdb (--xdist) 5) Grid IDs (--flexgrids) 6) Ground state grid&lt;br /&gt;
     (--ground_state)&lt;br /&gt;
     &lt;br /&gt;
     optional arguments:&lt;br /&gt;
       -h, --help            show this help message and exit&lt;br /&gt;
       -p ORI_PATH, --path ORI_PATH&lt;br /&gt;
                             Full path of the original blastermaster directory,&lt;br /&gt;
                             e.g. /mnt/nfs/work/asdf/asdf/asdf/&lt;br /&gt;
       -d DMS, --dms DMS     DMS Density. The higher the number, the more dense the&lt;br /&gt;
                             molecular surface is. 10.0 is default to ensure that&lt;br /&gt;
                             the smaller radii spheres sufficiently cover the&lt;br /&gt;
                             protein surface. If your spheres have larger radii or&lt;br /&gt;
                             if you are using small radii for ES spheres and QNIFFT&lt;br /&gt;
                             fails, this value can be decreased to 1.0.&lt;br /&gt;
       -es ES_RAD [ES_RAD ...], --es_rad ES_RAD [ES_RAD ...]&lt;br /&gt;
                             Radius of Electrostatic spheres. &lt;br /&gt;
                             Default is 1.0, 1.3, 1.5, 1.7, 1.9&lt;br /&gt;
       -ld LD_RAD [LD_RAD ...], --ld_rad LD_RAD [LD_RAD ...]&lt;br /&gt;
                             Radius of ligand desolvation spheres. &lt;br /&gt;
                             Default is 0.1, 0.2, 0.3, 0.4, 0.5&lt;br /&gt;
       -xd XDIST, --xdist XDIST&lt;br /&gt;
                             Distance thin spheres can be from xtal-lig.pdb.&lt;br /&gt;
                             Default is 2 Angstroms&lt;br /&gt;
       &#039;&#039;&#039;-fg GNUM [GNUM ...], --flexgrids GNUM [GNUM ...]&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Alternative conformation names. E.g. A,B,C&#039;&#039;&#039;&lt;br /&gt;
       &#039;&#039;&#039;-gs GROUND_STATE, --ground_state GROUND_STATE&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Ground state conformation name. E.g. A&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
      python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0001_generate_ES_LD_generation_flexible.py &lt;br /&gt;
             -p /nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC &lt;br /&gt;
             -d 5 -es 1.0 1.5 1.9 -ld 0.4 0.6 0.8 -xd 4 &lt;br /&gt;
             -fg A B C -gs A&lt;br /&gt;
&lt;br /&gt;
This will take a few minutes (code is still being optimized).&lt;br /&gt;
&lt;br /&gt;
Once the girds are calculated, dockfiles for different thin sphere combination need to be generated using the following script:&lt;br /&gt;
&lt;br /&gt;
     /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0002_combine_es_ld_grids_into_combos_flexible.py&lt;br /&gt;
&lt;br /&gt;
     usage: new_0002_combine_es_ld_grids_into_combos_flexible.py&lt;br /&gt;
       [-h] -p ORI_PATH -fg GNUM [GNUM ...] -gs GROUND_STATE&lt;br /&gt;
     &lt;br /&gt;
     This is a sphere scan directory generator script. This script requires that&lt;br /&gt;
     you provide the full path to your original blastermaster directory that you&lt;br /&gt;
     want to run a sphere scan on. This looks like: python&lt;br /&gt;
     new_0002_combine_ES_LD.py --path /mnt/nfs/blah/work/yourName/blah/DOCKprep/&lt;br /&gt;
     --flexgrids A B C --ground_state A&lt;br /&gt;
     &lt;br /&gt;
     optional arguments:&lt;br /&gt;
       -h, --help            show this help message and exit&lt;br /&gt;
       -p ORI_PATH, --path ORI_PATH&lt;br /&gt;
                             Full path of the original blastermaster directory,&lt;br /&gt;
                             e.g. /mnt/nfs/work/asdf/asdf/asdf/&lt;br /&gt;
       &#039;&#039;&#039;-fg GNUM [GNUM ...], --flexgrids GNUM [GNUM ...]&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Alternative conformation names. E.g. A,B,C&#039;&#039;&#039;&lt;br /&gt;
       &#039;&#039;&#039;-gs GROUND_STATE, --ground_state GROUND_STATE&#039;&#039;&#039;&lt;br /&gt;
                             &#039;&#039;&#039;Ground state conformation name. E.g. A&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
     python /mnt/nfs/exc/work/stefan/Flexible_docking_Tarting_Thin_Spheres/thin_sphere_scan/new_0002_combine_es_ld_grids_into_combos_flexible.py &lt;br /&gt;
            -p /nfs/home/stefan/exc/Flexible_docking_Tarting_Thin_Spheres/example_AmpC &lt;br /&gt;
            -fg A B C -gs A&lt;br /&gt;
&lt;br /&gt;
This will generate combo_directories containing flexible docking grids.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12817</id>
		<title>Quartzy and BearBuy</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12817"/>
		<updated>2020-08-04T21:51:25Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Compounds are typically ordered by adding requests on quartzy.com. Once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to keep in mind.&lt;br /&gt;
&lt;br /&gt;
= Placing requests and adding new vendors to BearBuy =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1)&#039;&#039;&#039; Whenever possible, if the lab still uses Quartzy, please enter (not place orders via Quartzy) your orders in Quartzy vs sending them directly to the lab manager (Henry).  Entering it in Quartzy will help keep track of the whereabouts of the compounds you are ordering (qty, location, etc).&lt;br /&gt;
Henry will check Quartzy &amp;amp; place your orders.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2)&#039;&#039;&#039; If a vendor is not set up in BearBuy, have the vendor complete the &#039;&#039;&#039;W-8BEN-E&#039;&#039;&#039; form (for international vendors), or, the &#039;&#039;&#039;W-8BEN&#039;&#039;&#039; form (for domestic vendors). To check whether a vendor is setup in BearBuy, login via MyAccess and search through the suppliers. &lt;br /&gt;
The W8 forms are available from the purchasing manager Matthew Denny (matt.denny@ucsf.edu). Forward the completed form to Yvonne or Matt Denny so the vendor can be set up in BearBuy. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;3)&#039;&#039;&#039; Please DO NOT place orders w/o PO #s, or, have vendors invoice UCSF w/o a PO #.  An order, or, invoice w/o a PO # causes problems w/ purchasing &amp;amp; accounting.  Don&#039;t place orders w/o PO #s.  If you have an urgent order, you will still need a PO to place it.  If necessary, consult Matt Denny (matt.denny@ucsf.edu) on how to best place/expedite urgent orders, or, if you have any questions about purchasing.&lt;br /&gt;
&lt;br /&gt;
= Placing orders in BearBuy from Quartzy requests =&lt;br /&gt;
&lt;br /&gt;
Written by Henry O&#039;Donnell&lt;br /&gt;
&lt;br /&gt;
=== How to place orders for the lab ===&lt;br /&gt;
&lt;br /&gt;
- Log in to Quartzy and check for new order requests, take note of the total price, the supplier, name of the person who placed the order, and the grant ID&lt;br /&gt;
&lt;br /&gt;
If there is a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-Click on the order request and download the PDF, but rename the file by adding the requester’s name and the date. For Example, change “Q125768.pdf” to “John Smith March 2 Q125768.pdf”&lt;br /&gt;
&lt;br /&gt;
-Copy the new file name (exclude .pdf), in this example you would copy “John Smith March 2 Q125768”&lt;br /&gt;
&lt;br /&gt;
-Log in to MyAccess and open “BearBuy”, scroll down and select “Amount based PO”&lt;br /&gt;
&lt;br /&gt;
-Input the name of the supplier (if the supplier is Tocris, input R&amp;amp;D)&lt;br /&gt;
&lt;br /&gt;
-Under Product description write “Chemicals per attached quote John Smith March 2 Q125768”. Paste the name of the file to save time and avoid mistakes.&lt;br /&gt;
&lt;br /&gt;
-Input the total price, select commodity code 00025 Chemicals, select “No” for the Protected health drop down, “No” for the services requested drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll to the bottom of the form and attach the pdf file under “external files”&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
If there is NOT a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-On the Bearbuy homepage search for the item, make sure it matches the request exactly, and add to cart.&lt;br /&gt;
&lt;br /&gt;
-If you can’t find the exact item, use the “non-catalog” form under the frequently used forms section.&lt;br /&gt;
&lt;br /&gt;
-Enter in the supplier, product description, catalogue number and price. Try to be specific in the product description. &lt;br /&gt;
&lt;br /&gt;
-Select commodity code 00025 Chemicals, and enter the relevant information for quantity. Select “No” for the Protected health drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Check out: ===&lt;br /&gt;
&lt;br /&gt;
-Edit the procurement department and enter “333019”&lt;br /&gt;
&lt;br /&gt;
-Edit the Accounting code and enter the corresponding Grant ID which should begin with PPSHOF&lt;br /&gt;
&lt;br /&gt;
-Edit the Shipping address, select the appropriate address and name. You may have to look up the address by typing in “BH509” or “BH501”&lt;br /&gt;
&lt;br /&gt;
-Finally, click “assign cart”, enter “Matthew Denny” and under notes write “Chemicals per attached quote John Smith March 2 Q125768” or leave blank for single items.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12816</id>
		<title>Quartzy and BearBuy</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12816"/>
		<updated>2020-08-04T21:50:41Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Compounds are typically ordered by adding requests on quartzy.com. Once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to keep in mind.&lt;br /&gt;
&lt;br /&gt;
= Placing requests and adding new vendors to BearBuy =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1)&#039;&#039;&#039; Whenever possible, if the lab still uses Quartzy, please enter (not place orders via Quartzy) your orders in Quartzy vs sending them directly to the lab manager (Henry).  Entering it in Quartzy will help keep track of the whereabouts of the compounds you are ordering (qty, location, etc).&lt;br /&gt;
Henry will check Quartzy &amp;amp; place your orders.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2)&#039;&#039;&#039; If a vendor is not set up in BearBuy, have the vendor complete the *W-8BEN-E* form (for international vendors), or, the *W-8BEN* form (for domestic vendors). To check whether a vendor is setup in BearBuy, login via MyAccess and search through the suppliers. &lt;br /&gt;
The W8 forms are available from the purchasing manager Matthew Denny (matt.denny@ucsf.edu). Forward the completed form to Yvonne or Matt Denny so the vendor can be set up in BearBuy. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;3)&#039;&#039;&#039; Please DO NOT place orders w/o PO #s, or, have vendors invoice UCSF w/o a PO #.  An order, or, invoice w/o a PO # causes problems w/ purchasing &amp;amp; accounting.  Don&#039;t place orders w/o PO #s.  If you have an urgent order, you will still need a PO to place it.  If necessary, consult Matt Denny (matt.denny@ucsf.edu) on how to best place/expedite urgent orders, or, if you have any questions about purchasing.&lt;br /&gt;
&lt;br /&gt;
= Placing orders in BearBuy from Quartzy requests =&lt;br /&gt;
&lt;br /&gt;
Written by Henry O&#039;Donnell&lt;br /&gt;
&lt;br /&gt;
=== How to place orders for the lab ===&lt;br /&gt;
&lt;br /&gt;
- Log in to Quartzy and check for new order requests, take note of the total price, the supplier, name of the person who placed the order, and the grant ID&lt;br /&gt;
&lt;br /&gt;
If there is a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-Click on the order request and download the PDF, but rename the file by adding the requester’s name and the date. For Example, change “Q125768.pdf” to “John Smith March 2 Q125768.pdf”&lt;br /&gt;
&lt;br /&gt;
-Copy the new file name (exclude .pdf), in this example you would copy “John Smith March 2 Q125768”&lt;br /&gt;
&lt;br /&gt;
-Log in to MyAccess and open “BearBuy”, scroll down and select “Amount based PO”&lt;br /&gt;
&lt;br /&gt;
-Input the name of the supplier (if the supplier is Tocris, input R&amp;amp;D)&lt;br /&gt;
&lt;br /&gt;
-Under Product description write “Chemicals per attached quote John Smith March 2 Q125768”. Paste the name of the file to save time and avoid mistakes.&lt;br /&gt;
&lt;br /&gt;
-Input the total price, select commodity code 00025 Chemicals, select “No” for the Protected health drop down, “No” for the services requested drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll to the bottom of the form and attach the pdf file under “external files”&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
If there is NOT a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-On the Bearbuy homepage search for the item, make sure it matches the request exactly, and add to cart.&lt;br /&gt;
&lt;br /&gt;
-If you can’t find the exact item, use the “non-catalog” form under the frequently used forms section.&lt;br /&gt;
&lt;br /&gt;
-Enter in the supplier, product description, catalogue number and price. Try to be specific in the product description. &lt;br /&gt;
&lt;br /&gt;
-Select commodity code 00025 Chemicals, and enter the relevant information for quantity. Select “No” for the Protected health drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Check out: ===&lt;br /&gt;
&lt;br /&gt;
-Edit the procurement department and enter “333019”&lt;br /&gt;
&lt;br /&gt;
-Edit the Accounting code and enter the corresponding Grant ID which should begin with PPSHOF&lt;br /&gt;
&lt;br /&gt;
-Edit the Shipping address, select the appropriate address and name. You may have to look up the address by typing in “BH509” or “BH501”&lt;br /&gt;
&lt;br /&gt;
-Finally, click “assign cart”, enter “Matthew Denny” and under notes write “Chemicals per attached quote John Smith March 2 Q125768” or leave blank for single items.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12815</id>
		<title>Quartzy and BearBuy</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12815"/>
		<updated>2020-08-04T21:29:19Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Compounds are typically ordered by adding requests on quartzy.com. Once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to keep in mind.&lt;br /&gt;
&lt;br /&gt;
= Placing requests and adding new vendors to BearBuy =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1)&#039;&#039;&#039; Whenever possible, if the lab still uses Quartzy, please enter (not place orders via Quartzy) your orders in Quartzy vs sending them directly to the lab manager (Henry).  Entering it in Quartzy will help keep track of the whereabouts of the compounds you are ordering (qty, location, etc).&lt;br /&gt;
Henry will check Quartzy &amp;amp; place your orders.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2)&#039;&#039;&#039; If a vendor is not set up in BearBuy, have the vendor complete the W-8BEN-E form (for international vendors), or, the W-8BEN form (for domestic vendors). To check whether a vendor is setup in BearBuy, login via MyAccess and search through the suppliers. &lt;br /&gt;
The W8 forms are available from the purchasing manager Matthew Denny (matt.denny@ucsf.edu). Forward the completed form to Yvonne or Matt Denny so the vendor can be set up in BearBuy. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;3)&#039;&#039;&#039; Please DO NOT place orders w/o PO #s, or, have vendors invoice UCSF w/o a PO #.  An order, or, invoice w/o a PO # causes problems w/ purchasing &amp;amp; accounting.  Don&#039;t place orders w/o PO #s.  If you have an urgent order, you will still need a PO to place it.  If necessary, consult Matt Denny (matt.denny@ucsf.edu) on how to best place/expedite urgent orders, or, if you have any questions about purchasing.&lt;br /&gt;
&lt;br /&gt;
= Placing orders in BearBuy from Quartzy requests =&lt;br /&gt;
&lt;br /&gt;
Written by Henry O&#039;Donnell&lt;br /&gt;
&lt;br /&gt;
=== How to place orders for the lab ===&lt;br /&gt;
&lt;br /&gt;
- Log in to Quartzy and check for new order requests, take note of the total price, the supplier, name of the person who placed the order, and the grant ID&lt;br /&gt;
&lt;br /&gt;
If there is a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-Click on the order request and download the PDF, but rename the file by adding the requester’s name and the date. For Example, change “Q125768.pdf” to “John Smith March 2 Q125768.pdf”&lt;br /&gt;
&lt;br /&gt;
-Copy the new file name (exclude .pdf), in this example you would copy “John Smith March 2 Q125768”&lt;br /&gt;
&lt;br /&gt;
-Log in to MyAccess and open “BearBuy”, scroll down and select “Amount based PO”&lt;br /&gt;
&lt;br /&gt;
-Input the name of the supplier (if the supplier is Tocris, input R&amp;amp;D)&lt;br /&gt;
&lt;br /&gt;
-Under Product description write “Chemicals per attached quote John Smith March 2 Q125768”. Paste the name of the file to save time and avoid mistakes.&lt;br /&gt;
&lt;br /&gt;
-Input the total price, select commodity code 00025 Chemicals, select “No” for the Protected health drop down, “No” for the services requested drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll to the bottom of the form and attach the pdf file under “external files”&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
If there is NOT a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-On the Bearbuy homepage search for the item, make sure it matches the request exactly, and add to cart.&lt;br /&gt;
&lt;br /&gt;
-If you can’t find the exact item, use the “non-catalog” form under the frequently used forms section.&lt;br /&gt;
&lt;br /&gt;
-Enter in the supplier, product description, catalogue number and price. Try to be specific in the product description. &lt;br /&gt;
&lt;br /&gt;
-Select commodity code 00025 Chemicals, and enter the relevant information for quantity. Select “No” for the Protected health drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Check out: ===&lt;br /&gt;
&lt;br /&gt;
-Edit the procurement department and enter “333019”&lt;br /&gt;
&lt;br /&gt;
-Edit the Accounting code and enter the corresponding Grant ID which should begin with PPSHOF&lt;br /&gt;
&lt;br /&gt;
-Edit the Shipping address, select the appropriate address and name. You may have to look up the address by typing in “BH509” or “BH501”&lt;br /&gt;
&lt;br /&gt;
-Finally, click “assign cart”, enter “Matthew Denny” and under notes write “Chemicals per attached quote John Smith March 2 Q125768” or leave blank for single items.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12814</id>
		<title>Quartzy and BearBuy</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12814"/>
		<updated>2020-08-04T21:19:07Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Compounds are typically ordered by adding requests on quartzy.com. Once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to keep in mind.&lt;br /&gt;
&lt;br /&gt;
= Adding new vendors to BearBuy =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1)&#039;&#039;&#039; Whenever possible, if the lab still uses Quartzy, please enter (not place orders via Quartzy) your orders in Quartzy vs sending them directly to the lab manager (Henry).  Entering it in Quartzy will help keep track of the whereabouts of the compounds you are ordering (qty, location, etc).&lt;br /&gt;
Henry will check Quartzy &amp;amp; place your orders.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2)&#039;&#039;&#039; If a vendor is not set up in BearBuy, have the vendor complete the W-8BEN-E form (for international vendors), or, the W-8BEN form (for domestic vendors). To check whether a vendor is setup in BearBuy, login via MyAccess and search through the suppliers. &lt;br /&gt;
The W8 forms are available from the purchasing manager Matthew Denny (matt.denny@ucsf.edu). Forward the completed form to Yvonne or Matt Denny so the vendor can be set up in BearBuy. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;3)&#039;&#039;&#039; Please DO NOT place orders w/o PO #s, or, have vendors invoice UCSF w/o a PO #.  An order, or, invoice w/o a PO # causes problems w/ purchasing &amp;amp; accounting.  Don&#039;t place orders w/o PO #s.  If you have an urgent order, you will still need a PO to place it.  If necessary, consult Matt Denny (matt.denny@ucsf.edu) on how to best place/expedite urgent orders, or, if you have any questions about purchasing.&lt;br /&gt;
&lt;br /&gt;
= Placing orders in BearBuy from Quartzy requests =&lt;br /&gt;
&lt;br /&gt;
Written by Henry O&#039;Donnell&lt;br /&gt;
&lt;br /&gt;
=== How to place orders for the lab ===&lt;br /&gt;
&lt;br /&gt;
- Log in to Quartzy and check for new order requests, take note of the total price, the supplier, name of the person who placed the order, and the grant ID&lt;br /&gt;
&lt;br /&gt;
If there is a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-Click on the order request and download the PDF, but rename the file by adding the requester’s name and the date. For Example, change “Q125768.pdf” to “John Smith March 2 Q125768.pdf”&lt;br /&gt;
&lt;br /&gt;
-Copy the new file name (exclude .pdf), in this example you would copy “John Smith March 2 Q125768”&lt;br /&gt;
&lt;br /&gt;
-Log in to MyAccess and open “BearBuy”, scroll down and select “Amount based PO”&lt;br /&gt;
&lt;br /&gt;
-Input the name of the supplier (if the supplier is Tocris, input R&amp;amp;D)&lt;br /&gt;
&lt;br /&gt;
-Under Product description write “Chemicals per attached quote John Smith March 2 Q125768”. Paste the name of the file to save time and avoid mistakes.&lt;br /&gt;
&lt;br /&gt;
-Input the total price, select commodity code 00025 Chemicals, select “No” for the Protected health drop down, “No” for the services requested drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll to the bottom of the form and attach the pdf file under “external files”&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
If there is NOT a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-On the Bearbuy homepage search for the item, make sure it matches the request exactly, and add to cart.&lt;br /&gt;
&lt;br /&gt;
-If you can’t find the exact item, use the “non-catalog” form under the frequently used forms section.&lt;br /&gt;
&lt;br /&gt;
-Enter in the supplier, product description, catalogue number and price. Try to be specific in the product description. &lt;br /&gt;
&lt;br /&gt;
-Select commodity code 00025 Chemicals, and enter the relevant information for quantity. Select “No” for the Protected health drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Check out: ===&lt;br /&gt;
&lt;br /&gt;
-Edit the procurement department and enter “333019”&lt;br /&gt;
&lt;br /&gt;
-Edit the Accounting code and enter the corresponding Grant ID which should begin with PPSHOF&lt;br /&gt;
&lt;br /&gt;
-Edit the Shipping address, select the appropriate address and name. You may have to look up the address by typing in “BH509” or “BH501”&lt;br /&gt;
&lt;br /&gt;
-Finally, click “assign cart”, enter “Matthew Denny” and under notes write “Chemicals per attached quote John Smith March 2 Q125768” or leave blank for single items.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12813</id>
		<title>Quartzy and BearBuy</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Quartzy_and_BearBuy&amp;diff=12813"/>
		<updated>2020-08-04T21:18:00Z</updated>

		<summary type="html">&lt;p&gt;Stefan: Created page with &amp;quot;Compounds are typically ordered by adding requests on quartzy.com, once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Compounds are typically ordered by adding requests on quartzy.com, once the request is approved, the order is placed on BearBuy (by the lab manager). Here are a few things to keep in mind.&lt;br /&gt;
&lt;br /&gt;
= Adding new vendors to BearBuy =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;1)&#039;&#039;&#039; Whenever possible, if the lab still uses Quartzy, please enter (not place orders via Quartzy) your orders in Quartzy vs sending them directly to the lab manager (Henry).  Entering it in Quartzy will help keep track of the whereabouts of the compounds you are ordering (qty, location, etc).&lt;br /&gt;
Henry will check Quartzy &amp;amp; place your orders.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2)&#039;&#039;&#039; If a vendor is not set up in BearBuy, have the vendor complete the W-8BEN-E form (for international vendors), or, the W-8BEN form (for domestic vendors). To check whether a vendor is setup in BearBuy, login via MyAccess and search through the suppliers. &lt;br /&gt;
The W8 forms are available from the purchasing manager Matthew Denny (matt.denny@ucsf.edu). Forward the completed form to Yvonne or Matt Denny so the vendor can be set up in BearBuy. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;3)&#039;&#039;&#039; Please DO NOT place orders w/o PO #s, or, have vendors invoice UCSF w/o a PO #.  An order, or, invoice w/o a PO # causes problems w/ purchasing &amp;amp; accounting.  Don&#039;t place orders w/o PO #s.  If you have an urgent order, you will still need a PO to place it.  If necessary, consult Matt Denny (matt.denny@ucsf.edu) on how to best place/expedite urgent orders, or, if you have any questions about purchasing.&lt;br /&gt;
&lt;br /&gt;
= Placing orders in BearBuy from Quartzy requests =&lt;br /&gt;
&lt;br /&gt;
Written by Henry O&#039;Donnell&lt;br /&gt;
&lt;br /&gt;
=== How to place orders for the lab ===&lt;br /&gt;
&lt;br /&gt;
- Log in to Quartzy and check for new order requests, take note of the total price, the supplier, name of the person who placed the order, and the grant ID&lt;br /&gt;
&lt;br /&gt;
If there is a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-Click on the order request and download the PDF, but rename the file by adding the requester’s name and the date. For Example, change “Q125768.pdf” to “John Smith March 2 Q125768.pdf”&lt;br /&gt;
&lt;br /&gt;
-Copy the new file name (exclude .pdf), in this example you would copy “John Smith March 2 Q125768”&lt;br /&gt;
&lt;br /&gt;
-Log in to MyAccess and open “BearBuy”, scroll down and select “Amount based PO”&lt;br /&gt;
&lt;br /&gt;
-Input the name of the supplier (if the supplier is Tocris, input R&amp;amp;D)&lt;br /&gt;
&lt;br /&gt;
-Under Product description write “Chemicals per attached quote John Smith March 2 Q125768”. Paste the name of the file to save time and avoid mistakes.&lt;br /&gt;
&lt;br /&gt;
-Input the total price, select commodity code 00025 Chemicals, select “No” for the Protected health drop down, “No” for the services requested drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll to the bottom of the form and attach the pdf file under “external files”&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
If there is NOT a PDF quote attached for multiple compounds:&lt;br /&gt;
&lt;br /&gt;
-On the Bearbuy homepage search for the item, make sure it matches the request exactly, and add to cart.&lt;br /&gt;
&lt;br /&gt;
-If you can’t find the exact item, use the “non-catalog” form under the frequently used forms section.&lt;br /&gt;
&lt;br /&gt;
-Enter in the supplier, product description, catalogue number and price. Try to be specific in the product description. &lt;br /&gt;
&lt;br /&gt;
-Select commodity code 00025 Chemicals, and enter the relevant information for quantity. Select “No” for the Protected health drop down, and “Agree” for the conflict of interest question&lt;br /&gt;
&lt;br /&gt;
-Scroll up and select “go”, then “proceed to check out”&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Check out: ===&lt;br /&gt;
&lt;br /&gt;
-Edit the procurement department and enter “333019”&lt;br /&gt;
&lt;br /&gt;
-Edit the Accounting code and enter the corresponding Grant ID which should begin with PPSHOF&lt;br /&gt;
&lt;br /&gt;
-Edit the Shipping address, select the appropriate address and name. You may have to look up the address by typing in “BH509” or “BH501”&lt;br /&gt;
&lt;br /&gt;
-Finally, click “assign cart”, enter “Matthew Denny” and under notes write “Chemicals per attached quote John Smith March 2 Q125768” or leave blank for single items.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Membrane_Modeling&amp;diff=12157</id>
		<title>Membrane Modeling</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Membrane_Modeling&amp;diff=12157"/>
		<updated>2019-11-18T21:18:45Z</updated>

		<summary type="html">&lt;p&gt;Stefan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Written by Stefan Gahbauer, 2019/11/03&lt;br /&gt;
&lt;br /&gt;
In order to account for ligand desolvation and electrostatic interactions in the low-dielectric environment of the hydrophobic membrane core, a lipid-bilayer is generated around the target receptor and included in the docking score grid generation.&lt;br /&gt;
Aiming at a fast, robust and computationally effective equilibration of the lipid bilayer around the embedded transmembrane receptor, coarse-grained (CG) molecular dynamics (MD) simulations and (if needed) subsequent atomistic simulations are employed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Required software and datasets =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Gromacs&#039;&#039;&#039; (v5 or newer) - Molecular Dynamics software package (http://manual.gromacs.org/)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CHARMM36m force field&#039;&#039;&#039; (http://mackerell.umaryland.edu/charmm_ff.shtml)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MARTINI&#039;&#039;&#039; Coarse-grained force field parameters(http://cgmartini.nl/)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;DSSP&#039;&#039;&#039; - Secondary Structure assignment (https://swift.cmbi.umcn.nl/gv/dssp/ , https://anaconda.org/salilab/dssp)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;martinize.py&#039;&#039;&#039; - Coarse-graining atomistic protein structures (http://cgmartini.nl/index.php/tools2/proteins-and-bilayers)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;insane.py&#039;&#039;&#039; - INSerting proteins in coarse-grained MembrANE (http://cgmartini.nl/index.php/tools2/proteins-and-bilayers)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;initram.sh&#039;&#039;&#039; and &#039;&#039;&#039;backward.py&#039;&#039;&#039; - Conversion of coarse-grained system to atomistic resolution (http://cgmartini.nl/index.php/tools2/resolution-transformation)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 1) Setting up the coarse-grained system =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0001-prepare-protein-CG-membrane.sh&lt;br /&gt;
&lt;br /&gt;
== 1.1) Prepare your files ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
Copy your rec.pdb to your working directory.&lt;br /&gt;
&lt;br /&gt;
If your rec.pdb has gaps, e.g. unresolved loops between transmembrane helices in case of GPCRs, try to model missing residues.&lt;br /&gt;
&lt;br /&gt;
One way is to use MODELLER following https://salilab.org/modeller/wiki/Missing%20residues.&lt;br /&gt;
&lt;br /&gt;
Corresponding input scripts for modeller can be found in:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/modeller&lt;br /&gt;
&lt;br /&gt;
== 1.2) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Login to gimel2.&lt;br /&gt;
&lt;br /&gt;
./0001-prepare-protein-CG-membrane.sh&lt;br /&gt;
&lt;br /&gt;
The script reads rec.pdb and copies all other required files from &lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/gromacs&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Generate CHARMM36m force field parameters of your protein in a Gromacs-readable format. &lt;br /&gt;
&lt;br /&gt;
Used tool: gmx pdb2gmx &lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;pdb2gmx&#039;&#039; directory&lt;br /&gt;
&lt;br /&gt;
-conf.gro / conf.pdb - Gromacs coordinate file&lt;br /&gt;
&lt;br /&gt;
-topol.top / Protein-atomistic.itp - Gromacs topology file, i.e. force field description of your input structure&lt;br /&gt;
&lt;br /&gt;
-posre.itp - Position restraints for heavy atoms of atomistic protein strucutre.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Build coarse-grained structure&lt;br /&gt;
&lt;br /&gt;
Used tool: martinize.py&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-chain_.ssd - Output from the DSSP program that is called by martinize.py&lt;br /&gt;
&lt;br /&gt;
-prot-cg.pdb - Coarse-grained protein structure&lt;br /&gt;
&lt;br /&gt;
-prot-cg.top - Coarse-grained Martini topology of system&lt;br /&gt;
&lt;br /&gt;
-Protein.itp - Coarse-grained Martini description of Protein structure&lt;br /&gt;
&lt;br /&gt;
-prot-rot.pdb - Coarse-grained protein structure aligned along z-axis of the simulation box according to the proteins first principal component axis. This ensures the correct placement of the protein during membrane preparation. &#039;&#039;&#039;You may have to adjust the orientation of your input structure prior to membrane modeling.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;c.&#039;&#039;&#039; Build coarse-grained membrane&lt;br /&gt;
&lt;br /&gt;
Used tool: insane.py&lt;br /&gt;
&lt;br /&gt;
Here, a lipid bilayer will be created around the protein structure (in the x/y-plane) and water will be added to the system. The default box shape is rectangular and the size is set to x,y=10nm, z=11nm. This can be changed in the ./insane.py command line. The default lipid type is POPC, you can change that to arbitrary lipid compositions using the -l and -u options of of insane.py.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-out.top / topol-cg.top - Topology of coarse-grained system&lt;br /&gt;
&lt;br /&gt;
-cg-membrane.gro/.pdb - Coarse-grained system coordinates. &#039;&#039;&#039;Carefully inspect and visualize the cg-membrane.pdb.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Use PyMOL to check if you&#039;re protein is embedded correctly in the lipid bilayer.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 2) Simulating the coarse-grained system =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0002-run-CG-Minimization-and-MD.sh&lt;br /&gt;
&lt;br /&gt;
== 2.1) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
./0002-run-CG-Minimization-and-MD.sh&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Minimize coarse-grained system&lt;br /&gt;
&lt;br /&gt;
Used tools: gmx grompp , gmx mdrun&lt;br /&gt;
&lt;br /&gt;
gmx grompp generates a single .tpr file that contains all information necessary for running a MD simulation or minimization using gmx mdrun.&lt;br /&gt;
&lt;br /&gt;
Minimization parameters are provided in martini_new-rf_min.mdp. The system will be minimized in 500 steps using steepest descent. The protein structure will be frozen during minimization.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-min.tpr - MD run input file&lt;br /&gt;
&lt;br /&gt;
-min.log - Output log file from minimization&lt;br /&gt;
&lt;br /&gt;
-min.trr - Minimization trajectory&lt;br /&gt;
&lt;br /&gt;
-min.gro - Minimized system coordinates&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Simulate coarse-grained system&lt;br /&gt;
&lt;br /&gt;
MD simulation parameters are provided in martini_v2.x_new-rf.mdp. Strong position restraints are applied on the protein structure during the simulation. The system will be simulated for 50ns.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-md.tpr - MD run input file&lt;br /&gt;
&lt;br /&gt;
-md.log - Output log file from simulation&lt;br /&gt;
&lt;br /&gt;
-md.trr - lossless trajectory of simulation&lt;br /&gt;
&lt;br /&gt;
-md.xtc - coordinates of simulation trajectory&lt;br /&gt;
&lt;br /&gt;
-md.gro - coordinates of final simulation snapshot&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The simulation will run for roughly 3 hours.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 3) Converting coarse-grained system to atomistic resolution and select lipid atoms for grid generation =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0003-backmap-and-lpd-selection.sh&lt;br /&gt;
&lt;br /&gt;
== 3.1) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
./0003-backmap-and-lpd-selection.sh&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Backmapping from coarse-grained to atomistic&lt;br /&gt;
&lt;br /&gt;
Used tool: gmx trjconv, initram.sh&lt;br /&gt;
&lt;br /&gt;
gmx trjconv can perform a variety of conversions of MD trajectory, e.g. making molecules broken over the periodic boundary conditions whole again. &lt;br /&gt;
&lt;br /&gt;
initram.sh calls the backward.py program which performs the backmapping of input coarse-grained to atomistic systems, and performs a small series of short minimizations and simulations to relax the backmapped system.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-0-backmapped.gro / projected.gro - initial backmapped coordinates&lt;br /&gt;
&lt;br /&gt;
-backmapped.top - Topology of atomistic system&lt;br /&gt;
&lt;br /&gt;
-1-EM*/2-EM* - Output from minimizations &lt;br /&gt;
&lt;br /&gt;
-3-mdpr*/4-mdpr*/5-mdpr*/6-mdpr* - Output from simulations&lt;br /&gt;
&lt;br /&gt;
-backmapped.gro - Coordinates of final backmapped and relaxed system&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This may need a few attempts to work all the way through. There is a while-loop that only stops until all relaxation steps have finished.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Replacing backmapped protein with initial atomistic protein structure&lt;br /&gt;
&lt;br /&gt;
Used tool: PyMOL script align.pml&lt;br /&gt;
&lt;br /&gt;
The pymol script will align the initial &amp;quot;Gromacs&amp;quot;-protein structure (conf.pdb) onto the backmapped structure and combine the fitted protein coordinates with the coordinates of the lipid and solvent environment.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap/prepare_AA_system&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-conf-fitted.pdb - Fitted initial protein structure&lt;br /&gt;
&lt;br /&gt;
-backmapped-environment.pdb - All membrane and water coordinates&lt;br /&gt;
&lt;br /&gt;
-fitted_system.pdb - Complete system containing fitted protein and environment coordinates&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Be sure that fitted_system.pdb has the same number of coordinates as backmapped-mol.pdb.&#039;&#039;&#039; If there is a discrepancy there might be an issue with the PyMOL version you&#039;re using to run align.pml. Using PyMOL v2 or newer seems to avoid any issues. You can also generate backmapped-environment.pdb manually by taking all POPC and Water cooridnates from backmapped-mol.pdb.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;c.&#039;&#039;&#039; Run minimizations of atomistic system&lt;br /&gt;
&lt;br /&gt;
Used tools: gmx grompp, gmx mdrun&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;backmap/prepare_AA_system&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
Tow minimizations will be calculated. &lt;br /&gt;
&lt;br /&gt;
1) Minimization with frozen protein coordinates: 1,500 steps steepest descent (min_freeze.mdp).&lt;br /&gt;
&lt;br /&gt;
-min_freeze* - Output files of first minimization&lt;br /&gt;
&lt;br /&gt;
2) Minimization of full system: 500 steps (min.mdp).&lt;br /&gt;
&lt;br /&gt;
-min* - Output files of second minimization&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;d.&#039;&#039;&#039; Select lipid atoms for DOCK grid generation&lt;br /&gt;
&lt;br /&gt;
Used tools: PyMOL script prepare.pml&lt;br /&gt;
&lt;br /&gt;
This will select carbon and hydrogen atoms of the hydrophobic lipid tail segments in a radius of 1.7 nm around the protein and assign them to the atom type &amp;quot;LPD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You need to provide the rec.pdb to want to use for docking (potentially with missing loops) at that step as xtal-prot.pdb&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap/prepare_AA_system/prepare_min&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-shell-LPD.pdb - all LPD atoms selected for grid generation&lt;br /&gt;
&lt;br /&gt;
Add these coordinates to your docking protein structure and provide a amb.crg.oxt file adding&lt;br /&gt;
&lt;br /&gt;
C     lpd        0.000     LIPID SPHERE&lt;br /&gt;
&lt;br /&gt;
Now you can run blastermaster.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
	<entry>
		<id>http://wiki.docking.org/index.php?title=Membrane_Modeling&amp;diff=12142</id>
		<title>Membrane Modeling</title>
		<link rel="alternate" type="text/html" href="http://wiki.docking.org/index.php?title=Membrane_Modeling&amp;diff=12142"/>
		<updated>2019-11-03T00:28:29Z</updated>

		<summary type="html">&lt;p&gt;Stefan: Created page with &amp;quot;Written by Stefan Gahbauer, 2019/11/03  In order to account for ligand desolvation and electrostatic interactions in the low-dielectric environment of the hydrophobic membrane...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Written by Stefan Gahbauer, 2019/11/03&lt;br /&gt;
&lt;br /&gt;
In order to account for ligand desolvation and electrostatic interactions in the low-dielectric environment of the hydrophobic membrane core, a lipid-bilayer is generated around the target receptor and included in the docking score grid generation.&lt;br /&gt;
Aiming at a fast, robust and computationally effective equilibration of the lipid bilayer around the embedded transmembrane receptor, coarse-grained (CG) molecular dynamics (MD) simulations and (if needed) subsequent atomistic simulations are employed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Required software and datasets =&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Gromacs&#039;&#039;&#039; (v5 or newer) - Molecular Dynamics software package (http://manual.gromacs.org/)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;CHARMM36m force field&#039;&#039;&#039; (http://mackerell.umaryland.edu/charmm_ff.shtml)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;MARTINI&#039;&#039;&#039; Coarse-grained force field parameters(http://cgmartini.nl/)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;DSSP&#039;&#039;&#039; - Secondary Structure assignment (https://swift.cmbi.umcn.nl/gv/dssp/ , https://anaconda.org/salilab/dssp)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;martinize.py&#039;&#039;&#039; - Coarse-graining atomistic protein structures (http://cgmartini.nl/index.php/tools2/proteins-and-bilayers)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;insane.py&#039;&#039;&#039; - INSerting proteins in coarse-grained MembrANE (http://cgmartini.nl/index.php/tools2/proteins-and-bilayers)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;initram.sh&#039;&#039;&#039; and &#039;&#039;&#039;backward.py&#039;&#039;&#039; - Conversion of coarse-grained system to atomistic resolution (http://cgmartini.nl/index.php/tools2/resolution-transformation)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 1) Setting up the coarse-grained system =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0001-prepare-protein-CG-membrane.sh&lt;br /&gt;
&lt;br /&gt;
== 1.1) Prepare your files ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
Copy your rec.pdb to your working directory.&lt;br /&gt;
&lt;br /&gt;
If your rec.pdb has gaps, e.g. unresolved loops between transmembrane helices in case of GPCRs, try to model missing residues.&lt;br /&gt;
&lt;br /&gt;
One way is to use MODELLER following https://salilab.org/modeller/wiki/Missing%20residues.&lt;br /&gt;
&lt;br /&gt;
Corresponding input scripts for modeller can be found in:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/modeller&lt;br /&gt;
&lt;br /&gt;
== 1.2) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Login to gimel2.&lt;br /&gt;
&lt;br /&gt;
./0001-prepare-protein-CG-membrane.sh&lt;br /&gt;
&lt;br /&gt;
The script reads rec.pdb and copies all other required files from &lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/gromacs&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Generate CHARMM36m force field parameters of your protein in a Gromacs-readable format. &lt;br /&gt;
&lt;br /&gt;
Used tool: gmx pdb2gmx &lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;pdb2gmx&#039;&#039; directory&lt;br /&gt;
&lt;br /&gt;
-conf.gro / conf.pdb - Gromacs coordinate file&lt;br /&gt;
&lt;br /&gt;
-topol.top / Protein-atomistic.itp - Gromacs topology file, i.e. force field description of your input structure&lt;br /&gt;
&lt;br /&gt;
-posre.itp - Position restraints for heavy atoms of atomistic protein strucutre.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Build coarse-grained structure&lt;br /&gt;
&lt;br /&gt;
Used tool: martinize.py&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-chain_.ssd - Output from the DSSP program that is called by martinize.py&lt;br /&gt;
&lt;br /&gt;
-prot-cg.pdb - Coarse-grained protein structure&lt;br /&gt;
&lt;br /&gt;
-prot-cg.top - Coarse-grained Martini topology of system&lt;br /&gt;
&lt;br /&gt;
-Protein.itp - Coarse-grained Martini description of Protein structure&lt;br /&gt;
&lt;br /&gt;
-prot-rot.pdb - Coarse-grained protein structure aligned along z-axis of the simulation box according to the proteins first principal component axis. This ensures the correct placement of the protein during membrane preparation. &#039;&#039;&#039;You may have to adjust the orientation of your input structure prior to membrane modeling.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;c.&#039;&#039;&#039; Build coarse-grained membrane&lt;br /&gt;
&lt;br /&gt;
Used tool: insane.py&lt;br /&gt;
&lt;br /&gt;
Here, a lipid bilayer will be created around the protein structure (in the x/y-plane) and water will be added to the system. The default box shape is rectangular and the size is set to x,y=10nm, z=11nm. This can be changed in the ./insane.py command line. The default lipid type is POPC, you can change that to arbitrary lipid compositions using the -l and -u options of of insane.py.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-out.top / topol-cg.top - Topology of coarse-grained system&lt;br /&gt;
&lt;br /&gt;
-cg-membrane.gro - Coarse-grained system coordinates. &#039;&#039;&#039;Carefully inspect and visualize the cg-membrane.gro.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Use PyMOL to check if you&#039;re protein is embedded correctly in the lipid bilayer.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 2) Simulating the coarse-grained system =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0002-run-CG-Minimization-and-MD.sh&lt;br /&gt;
&lt;br /&gt;
== 2.1) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
./0002-run-CG-Minimization-and-MD.sh&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Minimize coarse-grained system&lt;br /&gt;
&lt;br /&gt;
Used tools: gmx grompp , gmx mdrun&lt;br /&gt;
&lt;br /&gt;
gmx grompp generates a single .tpr file that contains all information necessary for running a MD simulation or minimization using gmx mdrun.&lt;br /&gt;
&lt;br /&gt;
Minimization parameters are provided in martini_new-rf_min.mdp. The system will be minimized in 500 steps using steepest descent. The protein structure will be frozen during minimization.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-min.tpr - MD run input file&lt;br /&gt;
&lt;br /&gt;
-min.log - Output log file from minimization&lt;br /&gt;
&lt;br /&gt;
-min.trr - Minimization trajectory&lt;br /&gt;
&lt;br /&gt;
-min.gro - Minimized system coordinates&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Simulate coarse-grained system&lt;br /&gt;
&lt;br /&gt;
MD simulation parameters are provided in martini_v2.x_new-rf.mdp. Strong position restraints are applied on the protein structure during the simulation. The system will be simulated for 50ns.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;martini&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-md.tpr - MD run input file&lt;br /&gt;
&lt;br /&gt;
-md.log - Output log file from simulation&lt;br /&gt;
&lt;br /&gt;
-md.trr - lossless trajectory of simulation&lt;br /&gt;
&lt;br /&gt;
-md.xtc - coordinates of simulation trajectory&lt;br /&gt;
&lt;br /&gt;
-md.gro - coordinates of final simulation snapshot&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;The simulation will run for roughly 3 hours.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= 3) Converting coarse-grained system to atomistic resolution and select lipid atoms for grid generation =&lt;br /&gt;
&lt;br /&gt;
This is automated in the script:&lt;br /&gt;
&lt;br /&gt;
/mnt/nfs/home/stefan/zzz.scripts/INSERT-MEMBRANE/FILES/0003-backmap-and-lpd-selection.sh&lt;br /&gt;
&lt;br /&gt;
== 3.1) Run the script ==&lt;br /&gt;
&lt;br /&gt;
Copy the script above to your working directory.&lt;br /&gt;
&lt;br /&gt;
./0003-backmap-and-lpd-selection.sh&lt;br /&gt;
&lt;br /&gt;
=== Workflow ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;a.&#039;&#039;&#039; Backmapping from coarse-grained to atomistic&lt;br /&gt;
&lt;br /&gt;
Used tool: gmx trjconv, initram.sh&lt;br /&gt;
&lt;br /&gt;
gmx trjconv can perform a variety of conversions of MD trajectory, e.g. making molecules broken over the periodic boundary conditions whole again. &lt;br /&gt;
&lt;br /&gt;
initram.sh calls the backward.py program which performs the backmapping of input coarse-grained to atomistic systems, and performs a small series of short minimizations and simulations to relax the backmapped system.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-0-backmapped.gro / projected.gro - initial backmapped coordinates&lt;br /&gt;
&lt;br /&gt;
-backmapped.top - Topology of atomistic system&lt;br /&gt;
&lt;br /&gt;
-1-EM*/2-EM* - Output from minimizations &lt;br /&gt;
&lt;br /&gt;
-3-mdpr*/4-mdpr*/5-mdpr*/6-mdpr* - Output from simulations&lt;br /&gt;
&lt;br /&gt;
-backmapped.gro - Coordinates of final backmapped and relaxed system&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;This may need a few attempts to work all the way through. There is a while-loop that only stops until all relaxation steps have finished.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;b.&#039;&#039;&#039; Replacing backmapped protein with initial atomistic protein structure&lt;br /&gt;
&lt;br /&gt;
Used tool: PyMOL script align.pml&lt;br /&gt;
&lt;br /&gt;
The pymol script will align the initial &amp;quot;Gromacs&amp;quot;-protein structure (conf.pdb) onto the backmapped structure and combine the fitted protein coordinates with the coordinates of the lipid and solvent environment.&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap/prepare_AA_system&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-conf-fitted.pdb - Fitted initial protein structure&lt;br /&gt;
&lt;br /&gt;
-backmapped-environment.pdb - All membrane and water coordinates&lt;br /&gt;
&lt;br /&gt;
-fitted_system.pdb - Complete system containing fitted protein and environment coordinates&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Be sure that fitted_system.pdb has the same number of coordinates as backmapped-mol.pdb.&#039;&#039;&#039; If there is a discrepancy there might be an issue with the PyMOL version you&#039;re using to run align.pml. Using PyMOL v2 or newer seems to avoid any issues. You can also generate backmapped-environment.pdb manually by taking all POPC and Water cooridnates from backmapped-mol.pdb.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;c.&#039;&#039;&#039; Run minimizations of atomistic system&lt;br /&gt;
&lt;br /&gt;
Used tools: gmx grompp, gmx mdrun&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the &#039;&#039;backmap/prepare_AA_system&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
Tow minimizations will be calculated. &lt;br /&gt;
&lt;br /&gt;
1) Minimization with frozen protein coordinates: 1,500 steps steepest descent (min_freeze.mdp).&lt;br /&gt;
&lt;br /&gt;
-min_freeze* - Output files of first minimization&lt;br /&gt;
&lt;br /&gt;
2) Minimization of full system: 500 steps (min.mdp).&lt;br /&gt;
&lt;br /&gt;
-min* - Output files of second minimization&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;d.&#039;&#039;&#039; Select lipid atoms for DOCK grid generation&lt;br /&gt;
&lt;br /&gt;
Used tools: PyMOL script prepare.pml&lt;br /&gt;
&lt;br /&gt;
This will select carbon and hydrogen atoms of the hydrophobic lipid tail segments in a radius of 1.7 nm around the protein and assign them to the atom type &amp;quot;LPD&amp;quot;&lt;br /&gt;
&lt;br /&gt;
You need to provide the rec.pdb to want to use for docking (potentially with missing loops) at that step as xtal-prot.pdb&lt;br /&gt;
&lt;br /&gt;
Output files are stored in the generated &#039;&#039;backmap/prepare_AA_system/prepare_min&#039;&#039; directory.&lt;br /&gt;
&lt;br /&gt;
-shell-LPD.pdb - all LPD atoms selected for grid generation&lt;br /&gt;
&lt;br /&gt;
Add these coordinates to your docking protein structure and provide a amb.crg.oxt file adding&lt;br /&gt;
&lt;br /&gt;
C     lpd        0.000     LIPID SPHERE&lt;br /&gt;
&lt;br /&gt;
Now you can run blastermaster.&lt;/div&gt;</summary>
		<author><name>Stefan</name></author>
	</entry>
</feed>