Trees | Indices | Help |
|
---|
|
object --+ | Workflow
Here we assume the user launches the workflow from the top level directory of a mapper job. We then expect the individual perturbation files to be in <jobname>_PERTURBATION_STAGE directory
Each edge will have a unique msj created from the top-level complex/solvent msj
|
|||
|
|||
|
|||
|
|||
|
|||
bool |
|
||
|
|||
|
|||
Inherited from |
|
|||
Inherited from |
|
x.__init__(...) initializes x; see help(type(x)) for signature
|
This will check for the presence of the multisim log file. When we launch a workflow we backup the original by moving it, therfore, if we launch a second workflow before the first is done the file will not be found and we will not allow the second job to be launched. |
This prepares all the necessary files for running the remote job. This will generate a tgz file which is tx to the remote host for running. If the prep_only option is given to the workflow the tgz file generated can be manually tx and run. |
This prepares the perturbation directory which contains the subjob stages. This is the stage 3 directory in the master workflow. This really just does a lot of file massaging.
|
Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1 on Mon May 19 23:05:09 2014 | http://epydoc.sourceforge.net |