You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that in Cylc 8 it is non-trivial to pass certain types of variables around within the global, workflow, or task configuration, even within the same file. And it becomes even more difficult to do this within conditional statements, user environment variables, or cylc runtime environment variables.
The Cylc 8 docs are littered with examples of using Jinja2 conditional statements to do all kinds of nifty things within the workflow, but these conditional statements have harsh limitations about which types of variables you can use. Cylc's implementation of Jinja2 also limits which features are available in the global configuration, thus causing one to not be able to do much passing back and forth without the configuration failing. This issue is mostly to document a bunch of testing that was done for the purposes of using these conditional statements within the global config for various purposes, including customization of runtime configurations based on platform selection (will be covered more in another issue).
Description of Problem
It turns out that in Cylc 8 it is non-trivial to pass certain types of variables around within the global, workflow, or task configuration, even within the same file. And it becomes even more difficult to do this within conditional statements, user environment variables, or cylc runtime environment variables.
The Cylc 8 docs are littered with examples of using Jinja2 conditional statements to do all kinds of nifty things within the workflow, but these conditional statements have harsh limitations about which types of variables you can use. Cylc's implementation of Jinja2 also limits which features are available in the global configuration, thus causing one to not be able to do much passing back and forth without the configuration failing. This issue is mostly to document a bunch of testing that was done for the purposes of using these conditional statements within the global config for various purposes, including customization of runtime configurations based on platform selection (will be covered more in another issue).
Testing
(TODO: Will add more details here)
References
From the docs
Stack Overflow Questions
Environment Variables
Note that all of these methods were tested and failed due to Cylc's specialized implementation of Jinja2
Logic operators
Other
The text was updated successfully, but these errors were encountered: