PATHSAMPLE: Difference between revisions

From Docswiki
Jump to navigation Jump to search
import>Dw34
(New page: Example setup for BLJ60 - DJW 1/2/11 In this example the objective was to link a crystal structure to a minimum from the amorphous region. OPTIM was first used to create min.data.info fi...)
 
No edit summary
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
A driver for OPTIM to create stationary point databases using discrete path sampling and perform kinetic analysis. PATHSAMPLE is documented [http://www-wales.ch.cam.ac.uk/PATHSAMPLE.2.1.doc/ here].
Example setup for BLJ60 - DJW 1/2/11


== Tutorials ==
In this example the objective was to link a crystal
These tutorials are under development. Please correct any mistakes you find and, of course, feel free to add more!
structure to a minimum from the amorphous region. OPTIM was first used to
create min.data.info files using odata files such as:


* [[Adding a model for PATHSAMPLE]]
DUMPDATA
* [[List of output files for PATHSAMPLE]]
BFGSSTEPS 5000
* [[Loading OPTIM's min.data.info files into PATHSAMPLE]]
BFGSMIN
* [[Using BHINTERP to find minima between two end points]]
ENDHESS
* [[Finding an initial path between two end points (minima)]]
MAXBFGS 0.2 2.0
* [[Adding partially finished OPTIM stationary points to a PATHSAMPLE database]]
UPDATES 100 100
* [[Optimising a path]] -- SHORTCUT, UNTRAP and FREEPAIRS
BFGSCONV 0.000001
* [[Calculating rate constants (GT and fastest path)]]
BINARY 48 1.5 0.5 0.8 0.88
* [[Calculating rate constants (SGT, DGT, and SDGT)]]
PARAMS 3.587037905 3.587037905 3.587037905 1.79
* [[Removing minima and transition states from the database]]
NORESET
* [[Relaxing existing minima with new potential and creating new database]]
POINTS
* [[Relaxing existing transition states with new potential and creating new database]]
LS -11.46001238000000 5.188783135000000 10.47622879000000
* [[If things go wrong...]]
LS -2.955568051000000 1.530923988000000 8.223564292000001
* [[If you lost file min.data, but still you have points.min]]
etc.
* [[path.info file is not read, causes PATHSAMPLE to die]]

* [[BLJ60 example input]]
This produced min.data.info.finish and min.data.info.start, which were copied
to a clean directory and read into min.data and points.min using READMIN with
this pathdata file:

NATOMS 60
COPYFILES perm.allow
BULK 3.587037905 3.587037905 3.587037905
PERMDIST
SYSTEM LS
TEMPERATURE 0.71
CONNECTIONS 1
SEED 1
PERTURB 0.40
ETOL 1.0D-7
ITOL 0.01D0
DIRECTION AB
EXEC /home/wales/bin/OPTIM
TRIPLES
ADDTRIPLES
STARTTRIPLES
READMIN min.data.info.start
CYCLES 0
CPUS 1

A single OPTIM connect run was then started for DIJINITCONT. This initial
cycle is necessary before tryin multiple cycles, because there is only one
possible connection attempt with only two minima. The relevant pathdata lines were:
DIJINITCONT EXP
CYCLES 100
JOBSPERNODE 1
PAIRLIST 1
with a qsub file:
#!/bin/csh
#PBS -N BLJ60.1.3.37
#PBS -q h8
#PBS -j oe
#PBS -l nodes=1:ppn=8

cd $PBS_O_WORKDIR
cat $PBS_NODEFILE >& output
wc output > nodes.info
cat $PBS_NODEFILE >> nodes.info
echo $USER >> nodes.info
echo $PBS_O_WORKDIR >> nodes.info

/home/wales/bin/PATHSAMPLE >>& output

echo
qstat -f ${PBS_JOBID}@volkhan
echo

A subsequent run with CYCLES 100 on 8 cores found an initial path in five cycles,
which took a few minutes wall clock time.

Latest revision as of 10:33, 14 May 2019