...
Running Kepler interactively with FC2K actors inside the workflow. We have to make sure that current directory can be set to any location outside of the Kepler. We run simple cases, then ETS-like ones, where some might read/write files in current directory
In order to run test case for ETS make sure to follow these steps:
| Code Block |
|---|
# prepare env.
> module load itmenv/ETS_4.10b.10_v5.6.0
> mkdir $ITMWORK/isolated_kepler_test
> cd $ITMWORK/isolated_kepler_test
> source $ITMSCRIPTDIR/ITMv2 test
> setenv KEPLER /gss_efgw_work/work/g2michal/cpt/development/isolated_kepler/ETS_4.10b.10_v5.6.1/kepler
> svn co https://gforge6.eufus.eu/svn/keplerworkflows/tags/ETS_4.10b.10_v5.6.0
# do not go inside $KEPLER!
> $KEPLER/kepler.sh ETS_4.10b.10_v5.6.0/ETS_WORKFLOW.xml
# execute the workflow |
you should be able to execute the whole workflow and see the results as below
Standalone mode
Running these actors in standalone mode (checking the behaviour of the copy of sources/exec from initial place in Kepler to KEPLEREXECUTION/sandbox)
...