Closed seb-wahl closed 2 years ago
Hi @seb-wahl ,
This is indeed weird. I would have expected that naming the two subjobs
the same (postprocessing
) would have resulted into running one or the other, not both in the same script. Can you try changing the names of the subjobs? postprocessing_echam
and postprocessing_nemo
, or something on those lines?
Once we have a clue on how this really works then I'll add some error handling and documentation so no one else has to run into the same trap.
If I change the name of the subjobs it works as expected. I guess somewhere in the code of the workflow manager all scripts behind a name are concatenated.
Describe the bug If I add a postprocessing section for two components (echam and nemo in foci.yaml) of a coupled setup (see https://github.com/esm-tools/esm_tools/blob/ab2e86ead81a83e6f043ff8d403056378cf8c9d1/configs/setups/foci/foci.yaml#L281-L299 and https://github.com/esm-tools/esm_tools/blob/ab2e86ead81a83e6f043ff8d403056378cf8c9d1/configs/setups/foci/foci.yaml#L385-L403 then, one postprocessing script is generated that contains the call to both postprocessing scripts:
This script is called TWICE add exactly the same time by the workflow manager. To Reproduce see above
Expected behavior Two scripts that are executed independent of each other as separate jobs. I went through the code a bit and there a things such as
subjob_clusters
etc. but I couldn't find any documentation on how to use those settings.Screenshots If applicable, add screenshots to help explain your problem.
System (please complete the following information):