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
PrognosticData holds the main prognostic variables as initial, write-only values, while other model subroutines (e.g., IceGrowth and Dynamics) hold a copy of them as intermediary, read-write values.
There is no need to carry two data versions, which may give rise to unexpected errors.
The text was updated successfully, but these errors were encountered:
The temporary damage variable damageUpd was not correctly initialised in
PrognosticData::update. This commit just sets it to the value of
m_damage (as it should be done), but a proper fix would address issue
#725
PrognosticData holds the main prognostic variables as initial, write-only values, while other model subroutines (e.g., IceGrowth and Dynamics) hold a copy of them as intermediary, read-write values.
There is no need to carry two data versions, which may give rise to unexpected errors.
The text was updated successfully, but these errors were encountered: