-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
postprocessing/subjob example needed #960
Comments
Hi @chrisdane, as a first reply to your issue. I followed the exercise in the ESM-Tools workshop (https://github.com/esm-tools/workshops/blob/main/202207_AWI_ESM-Tools/exercises/7.5_workflow_manager.md see the solution). And this worked for me as a first try:
I placed this in a runscript as a new component. What also worked is to put everything starting from If you have any other suggestions for the workflow manager, please also add them as a comment to the following discussion #1023. Thank you. |
This issue has been inactive for the last 365 days. It will now be marked as stale and closed after 30 days of further inactivity. Please add a comment to reset this automatic closing of this issue or close it if solved. |
This issue cannot yet be closed.
Maybe we can change this in the future, so that it doesn't have to be in a component. More on that when we resume the work on the workflow manager. |
Request/contribution description
I am confused by the documentation on how to set up post-processing jobs/subjobs as e.g. here: https://esm-tools.readthedocs.io/en/latest/workflow.html?highlight=tidy#example-1-adding-an-additional-postprocessing-subjob:
My question are:
next_run_triggered_by: tidy
andrun_after: tidy
necessary? Whats their difference?script_dir
andscript
; why both?call_function
andenv_preparation
?nproc
be provided by e.g. a usual sbatch-header in thescript
itself?I would find an explicit example very helpful.
Thanks a lot and cheers,
Chris
The text was updated successfully, but these errors were encountered: