- removed comment
python simfactory submit creates only the SubmitScript
Issue #271
closed
The python version of simfactory submit creates only the submitScript called PreparedSubmitScript. The RunScript is created at the moment of the simfactory run call at the end of the SubmitScript.
So a user has no possibilty to check whether his settings e.g. for mpirun have been correct or not for all the time where the job is only queued. I feel this is not a user friendly solution. The RunScript should be created together with the SubmitScript.
Keyword: simfactory
Keyword: submit
Comments (8)
-
-
reporter
- removed comment
I have updated today my python simfactory. I am using the Revision 1191, and I see the SubmitScript, not the PreparedSubmitScript. Thanks for the hint.
-
- assigned issue to
- changed component to SimFactory
- removed comment
-
- marked as enhancement
- marked as
- removed comment
-
reporter
- removed comment
Erik renamed PreparedSubmitScript to just SubmitScript. When submission happens, you can see the final output (after all the substitutions and variables have been expanded) submission script at <basedir>/<simulationname>/output-<xxx>/SIMFACTORY/SubmitScript
When submitting a simulation with the current revision r1220, you will see debug output similiar to the following:
Info: saving substituted submitscript contents to: /work/mwt/simulations/rr_test/output-0000/SIMFACTORY/SubmitScript
You can then look at that file to see the final contents of the SubmitScript.
-
- removed comment
Alexander, does this fix your problem? Can we close the ticket?
-
- changed status to resolved
- removed comment
Closing this ticket.
-
- edited description
- changed status to closed
- Log in to comment
- Assignee
-
anonymous
- Type
- Priority
- Status
- closed
- Component
- SimFactory
- Milestone
- –
- Version
- –
- Votes
- 0
- Watchers
- 0
If you see a PreparedSubmitScript, then you are using an older version of SimFactory 2.
Submitting a simulation interacts with the queuing system, while running a simulation interacts with MPI. These are now separated in SimFactory 2. To debug, I suggest to start the job interactively, which gives you immediate feedback.
Michael, could you briefly describe how to do that? Have you tested this on Damiana?