-
Notifications
You must be signed in to change notification settings - Fork 180
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
Generate ecflow suites dynamically #501
Comments
WalterKolczynski-NOAA
pushed a commit
that referenced
this issue
May 9, 2022
Adds a preliminary version of an ecflow suite generator as an alternative to the standard rocoto system. The new workflow system is located in the workflow_generator directory. The suite is defined based on a YAML file, which is parsed to generate an ecflow suite definition, and the necessary scripts are located and placed into the necessary directory structure to support the ecflow suite. See the new README in the workflow generator directory for more details. Refs #501
WalterKolczynski-NOAA
pushed a commit
that referenced
this issue
May 12, 2022
Adds a preliminary version of an ecFlow suite generator in a new workflow_generator directory. The suite generator takes in a configuration as a YAML file and generates the appropriate ecFlow suite definition file, as well as copies the appropriate scripts into the correct structure as dictated by the suite. For full details on use, see the README in the workflow_generator directory. Refs #501
kayeekayee
pushed a commit
to kayeekayee/global-workflow
that referenced
this issue
May 30, 2024
…apabilities (NOAA-EMC#501) * Add the storm-following or specified moving-nesting capability for both the regional and global configuration. * Expand the UFS/HAFS FV3ATM-HYCOM ocean coupling to support the static and moving nesting configuration. * Expand the write grid component to support outputting the moving nest domain properly. * Five HAFS related moving-nesting regression tests are added to test these newly added features. The regional_hafs RT was removed. Co-authored-by: Dom Heinzeller <climbfuji@ymail.com> Co-authored-by: Dom Heinzeller <dom.heinzeller@icloud.com> Co-authored-by: Grant Firl <grantf@ucar.edu> Co-authored-by: Daniel Rosen <daniel.rosen@noaa.gov> Co-authored-by: man.zhang <Man.Zhang@noaa.gov> Co-authored-by: William Ramstrom <William.Ramstrom@noaa.gov> Co-authored-by: Ufuk Turuncoglu <ufuk.turuncoglu@noaa.gov> Co-authored-by: Dusan Jovic <dusan.jovic@noaa.gov> Co-authored-by: A-Kyle <kyle.ahern@noaa.gov> Co-authored-by: Gerhard Theurich <theurich@sourcespring.net> Co-authored-by: Dusan Jovic <48258889+DusanJovic-NOAA@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A meeting on 2021/11/12 indicated we need to design a solution to generate ecflow files from the global workflow python utility.
This solution should allow user to enter a supportable configuration to the global workflow python utility.
The global workflow python utility will dynamically create a set of ecflow files that allow user to start using ecflow to run an experiment.
The text was updated successfully, but these errors were encountered: