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
cable_cbm is basically the per timestep model_driver. It has been called in both UM/offliine apps. However,
#defines and if() conditions everywhere direct which parts of the driver are to be activated at which point.
This alone is not ideal as it is getting messy. However, in JAC we are aiming to specifically send ONLY
necessary variables to parts of the model, rather than entire TYPEs. Thus the "call" in JAC has arg lists
populated by specific variables. The idea is to pass that same variable in the offline version as a specific
member of a type. These two should have identical value. Thus we can maintain the two methods across versions.
However, the arg lists will sytactically be populated by different KINDS that don't necessarily exist in both
versions. It is necessary at this time to therefore have two different versions of this "driver" which should
not involve any science anyway.
Issue migrated from trac:265 at 2023-11-27 11:34:15 +1100
The text was updated successfully, but these errors were encountered:
keyword_keepgit
owner:[email protected]
type_JAC readiness
| by [email protected]cable_cbm is basically the per timestep model_driver. It has been called in both UM/offliine apps. However,
#defines and if() conditions everywhere direct which parts of the driver are to be activated at which point.
This alone is not ideal as it is getting messy. However, in JAC we are aiming to specifically send ONLY
necessary variables to parts of the model, rather than entire TYPEs. Thus the "call" in JAC has arg lists
populated by specific variables. The idea is to pass that same variable in the offline version as a specific
member of a type. These two should have identical value. Thus we can maintain the two methods across versions.
However, the arg lists will sytactically be populated by different KINDS that don't necessarily exist in both
versions. It is necessary at this time to therefore have two different versions of this "driver" which should
not involve any science anyway.
Issue migrated from trac:265 at 2023-11-27 11:34:15 +1100
The text was updated successfully, but these errors were encountered: