Open jatkinson1000 opened 1 month ago
For implementing the case correctly we need to know what and where the CAM state variables are updated.
Is it as part of gw_drag_prof()
which will complicate things, or is it an output from this routine that is applied somewhere subsequently?
My understanding is that utgw
and vtgw
are intent(out)
from gw_drag_prof() so could be written to file and overwritten by another scheme.
Yes, these variables are tendencies that are added to a ptend
variable for u and v a few lines later, so can hopefully be overwritten as appropriate.
This has been updated so that the logic is in place for the different options to be run.
Currently they all call the non-ML scheme, with a TODO
in-code for modifying later once the coupling interface is written.
See comments above regarding where the tendencies are added to ptend
- will require additional logic loops to select which is run.
Closes #8
Note that this is build on top of (rebased) #4 and #5
Modifications the code in gw_drag.f90 in preparation to call the alternative ML code.