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
Say that I want to calibrate CATKE using the mismatch between the gradient of observed and modeled TKE, rather than the absolute value. This is reasonable if we really care about the "shape" of the profile, rather than its absolute magnitude.
For this I think we can allow users to specify transformations on data that get loaded into field_time_series. This is what it might look like:
under the hood, we can first load the "file-based" FieldTimeSeries, and then use that data to make the list of computed_fields. The first argument to Computation is a function that transforms dependencies (one of or a list of the fields that were loaded from file) into another field or abstract operation.
It's probably also possible to design a macro that allows us to write (since the code gives us the names of the inputs.
Say that I want to calibrate CATKE using the mismatch between the gradient of observed and modeled TKE, rather than the absolute value. This is reasonable if we really care about the "shape" of the profile, rather than its absolute magnitude.
For this I think we can allow users to specify transformations on data that get loaded into
field_time_series
. This is what it might look like:For shear we might write
under the hood, we can first load the "file-based"
FieldTimeSeries
, and then use that data to make the list ofcomputed_fields
. The first argument toComputation
is a function that transformsdependencies
(one of or a list of the fields that were loaded from file) into another field or abstract operation.It's probably also possible to design a macro that allows us to write (since the code gives us the names of the
inputs
.The text was updated successfully, but these errors were encountered: