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
Most of the existing Transform subclasses assume import and export state consist of a single ESMF Field each. But in the case of TangentVector, each of these states will instead have a FieldBundle with 2 items.
A simple check in the run method can determine whether to act on a single field or to loop over 2 fields. In the worst case, we could instead capture the distinction in the constructor and then use different procedures for the 2 cases.
The text was updated successfully, but these errors were encountered:
Most of the existing Transform subclasses assume import and export state consist of a single ESMF Field each. But in the case of TangentVector, each of these states will instead have a FieldBundle with 2 items.
A simple check in the run method can determine whether to act on a single field or to loop over 2 fields. In the worst case, we could instead capture the distinction in the constructor and then use different procedures for the 2 cases.
The text was updated successfully, but these errors were encountered: