PATHSAMPLE: Difference between revisions
Jump to navigation
Jump to search
import>Mp466 No edit summary |
import>Mp466 |
||
| (One intermediate revision by the same user not shown) | |||
| Line 14: | Line 14: | ||
* [[Removing minima and transition states from the database]] |
* [[Removing minima and transition states from the database]] |
||
* [[Relaxing existing minima with new potential and creating new database]] |
* [[Relaxing existing minima with new potential and creating new database]] |
||
* [[Relaxing existing transition states with new potential and creating new database]] |
|||
* [[If things go wrong...]] |
* [[If things go wrong...]] |
||
* [[If you lost file min.data, but still you have points.min]] |
* [[If you lost file min.data, but still you have points.min]] |
||
* [[path.info file is not read, causes PATHSAMPLE to die]] |
|||
Latest revision as of 18:16, 13 October 2009
A driver for OPTIM to create stationary point databases using discrete path sampling and perform kinetic analysis. PATHSAMPLE is currently documented for two versions, 2.0 and 2.1.
Tutorials
These tutorials are under development. Please correct any mistakes you find and, of course, feel free to add more!
- Adding a model for PATHSAMPLE
- List of output files for PATHSAMPLE
- Using BHINTERP to find minima between two end points
- Finding an initial path between two end points (minima)
- Adding partially finished OPTIM stationary points to a PATHSAMPLE database
- Optimising a path
- Calculating rate constants (GT and fastest path)
- Calculating rate constants (SGT, DGT, and SDGT)
- Removing minima and transition states from the database
- Relaxing existing minima with new potential and creating new database
- Relaxing existing transition states with new potential and creating new database
- If things go wrong...
- If you lost file min.data, but still you have points.min
- path.info file is not read, causes PATHSAMPLE to die