#291: new python simfactory does not overtake the "-roe" option of Cactus is used with submit -----------------------------------------------+---------------------------- Reporter: alexander.beck-ratzka@… | Owner: mthomas Type: defect | Status: new Priority: minor | Milestone: ET_2010_11 Component: SimFactory | Version: ET_2010_11 Resolution: | Keywords: -----------------------------------------------+----------------------------
Comment (by eschnett):
The expected behaviour of Simfactory is the following:
- When a Cactus configuration is built and the --runscript option is given (or if the configuration does not have a run script), then Simfactory's runscript template is copied into the directory containing the Cactus configuration.
- When a simulation is created, then the run script (and the submit script) accompanying the Cactus configuration is copied into the simulation, and is partly expanded
- When a restart is submitted, then the simulation's run script is copied into the restart directory, and is fully expanded
The rationale behind the behaviour is that both Cactus configurations and simulations should be self-consistent if other things on the system change. The submit script and run script very likely depend on the configuration options that were used to build the Cactus configuration, and should therefore remain associated with the executable.