Draft
Conversation
* Initial commit * intermediate * rename task and add toggle * restore get_observations * fix toggle * Updated to link * Update naming and add task to 3dvar_atmos * add task * Add task to other suites * add runtime for getobsnotinr2d2
* Automatically set window length * Update 3dfgat_cycle, remove comment
…cs.nasa.gov:/home/manstett/swell-main into feature/mranst/workflows_for_comparison
…nasa.gov:/home/manstett/swell-main into se/mranst/workflow_templating_redux2
* Add eva yamls and suite config for cf * Fixes * Fix overlapping text * Remove increment file from clean patterns
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the most recent version of the concept of updating the workflow templating to use python. This approach should be more straightforward and easier to understand than the previous version, as it uses the same jinja templating in the graph section to make it easier to read (though it doesn't necessarily have to). This pr also merges the task_runtimes and task_questions objects used by the previous pr into one object for simplicity. I'm aiming for this approach to allow for greater independence of the tasks from the suite creation system, to allow generating configs for single tasks and having mock values for code tests for each task, but that's not ready to show off yet.
I still need to merge develop into this and update the docs, but I wanted to open this up as a draft