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
While working on PR #772, I encountered the issue of not able to create additional dimensions in the restart file. It seems to me the issue is related to the save_restart subroutine in MOM_restart.F90. Specifically, the extra_axes to be created in the restart file is generated in lines 1427 to 1429:
However, this call is placed within a loop, such that extra_axes generated for a restart field will be overwritten by the next restart field. As a result, when creating the restarting file in lines 1505 to 1511:
the extra_axes is always the one associated with the last restart field.
In PR #722, I was able to get around of this issue by registering the restart fields of the MOM_streaming_filter module after all other restart fields/pairs are registered, but I think there should be a better solution. I've looked around and see that the MOM_internal_tides module also defines additional axes in the restart file, and I think there could be a problem if both modules are being used in the simulation.
The text was updated successfully, but these errors were encountered:
While working on PR #772, I encountered the issue of not able to create additional dimensions in the restart file. It seems to me the issue is related to the
save_restart
subroutine inMOM_restart.F90
. Specifically, theextra_axes
to be created in the restart file is generated in lines 1427 to 1429:However, this call is placed within a loop, such that
extra_axes
generated for a restart field will be overwritten by the next restart field. As a result, when creating the restarting file in lines 1505 to 1511:the
extra_axes
is always the one associated with the last restart field.In PR #722, I was able to get around of this issue by registering the restart fields of the
MOM_streaming_filter
module after all other restart fields/pairs are registered, but I think there should be a better solution. I've looked around and see that theMOM_internal_tides
module also defines additional axes in the restart file, and I think there could be a problem if both modules are being used in the simulation.The text was updated successfully, but these errors were encountered: