-
Notifications
You must be signed in to change notification settings - Fork 64
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
Implement variable action class in capgen (30 hours) #403
Comments
These classes are likely to be based on the |
@gold2718 @climbfuji |
@dustinswales, I believe this is still planned. @peverwhee? |
@dustinswales @gold2718 Still planned, #410 addressed it, but the implementation still remains un-done. |
@dustinswales your PR #504 will resolve this issue, I made the necessary connection. |
This PR adds automatic conversions for supported unit and type transforms. Also, included is a new ccpp variable property to indicate a scheme variables vertical orientation vertical, top_at_one. As default, top_at_one is set to .false.(GFS ordering convention). Adding top_at_one = .true. to a variable in a schemes metadata file will trigger automatic array flipping: Addresses #329 and #403 Conversions supported: https://github.com/NCAR/ccpp-framework/blob/main/scripts/conversion_tools/unit_conversion.py --------- Co-authored-by: dustinswales <dswales@ucar.edu> Co-authored-by: Grant Firl <grantf@ucar.edu> Co-authored-by: Dom Heinzeller <dom.heinzeller@icloud.com>
Closed via #504 |
Description
The variable action class (aka
var_action
) needs to be implemented incapgen
. This class will provide the ability to manipulate variables prior to entering physics schemes and posterior to returning from physics schemes.Solution
The
var_action
class must support combinations of data manipulations at the same time, for example blocking/de-blocking of arrays and unit conversions. The current implementation inccpp_prebuild
handles this explicitly for each possible combination of data manipulations, which requires a lot of redundant code and is not maintainable going into the future.Related to (optional)
The var_action class is a requirement for implementing the following items: #314, #329, #348, #349, #325
The text was updated successfully, but these errors were encountered: