Hello! Don't we need to set 'myIterIn=nIter0' in mit_run.F ?

[ajinn05]

Hello Rui,

I had some difficulties while restarting the simulation with diagnostics package.
I can't restart the simulation whenever I use diagnostics package. The error messages were like below:
(PID.TID 0000.0001) *** DIAGNOSTICS_STATUS_ERROR *** from: DIAGNOSTICS_FILL call
(PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: diagName="ETAN ", expectStatus= 20, pkgStatus= 10
(PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: <== called from the WRONG place, i.e.
(PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: before DIAGNOSTICS_SWITCH_ONOFF call in FORWARD_STEP

This error was caused in subroutine DO_STATEVARS_DIAGS because of 'drag_pkgStatus != ready2fillDiags.'
The model did not set diag_pkgStatus = ready2fillDiags in subroutine DIAGNOSTICS_SWITCH_ONOFF since myIter != nIter0.

And I figured out I can solve this problem by changing some lines in mitCode/mit_run.F.
Since the problem was related to the nIter0 which is not zero for the restart case, I found that there's two lines commented out in 'mit_run.F':
173 ! myTimeIn=startTime
174 ! myIterIn=nIter0

So I just wonder if I have to comment out those lines, or it is okay to uncomment to solve the problem.

Best,
Ajin

[iurnus]

Hi Ajin, First, you can take a look at the restart case in L3C1 case: https://github.com/iurnus/scripps_kaust_model/tree/master/coupler/L3.C1.coupled_RS2012_ring/runCase.restart Maybe you can take a look at data file: # Time stepping parameters &PARM03 # startTime = 1800., # endTime = 3600., nIter0 = 30., nTimeSteps = 60., In my case, I used the diagnostic package and it is working. I think this illustration case could help you debug this issue, although you may use different setups in your coupled model. You can go ahead to see if uncommenting these lines could help with your case. If these lines are changed, I think you should reset the time in data.cal every time you restart the case. We can further discuss if your restart simulations are still not working. Best, Rui

…

On Mon, Jun 19, 2023 at 7:08 PM ajinn05 ***@***.***> wrote: Hello Rui, I had some difficulties while restarting the simulation with diagnostics package. I can't restart the simulation whenever I use diagnostics package. The error messages were like below: (PID.TID 0000.0001) *** DIAGNOSTICS_STATUS_ERROR *** from: DIAGNOSTICS_FILL call (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: diagName="ETAN ", expectStatus= 20, pkgStatus= 10 (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: <== called from the WRONG place, i.e. (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: before DIAGNOSTICS_SWITCH_ONOFF call in FORWARD_STEP This error was caused in subroutine DO_STATEVARS_DIAGS because of 'drag_pkgStatus != ready2fillDiags.' The model did not set diag_pkgStatus = ready2fillDiags in subroutine DIAGNOSTICS_SWITCH_ONOFF since myIter != nIter0. And I figured out I can solve this problem by changing some lines in mitCode/mit_run.F. Since the problem was related to the nIter0 which is not zero for the restart case, I found that there's two lines commented out in 'mit_run.F': 173 ! myTimeIn=startTime 174 ! myIterIn=nIter0 So I just wonder if I have to comment out those lines, or it is okay to uncomment to solve the problem. Best, Ajin — Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUOYU7KXNL3H4DMGQ6FOA3XMEA2BANCNFSM6AAAAAAZMTGKVQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Rui Sun

[iurnus]

Hi Ajin, I think you can also restart the coupled model in this way: 1. restart WRF run as the example case; 2. run MITgcm as a "new case", but use the pickup files to initialize it. Maybe this can help get rid of the issue that you are having now. Best, Rui

…

On Mon, Jun 19, 2023 at 10:24 PM Rui Sun ***@***.***> wrote: Hi Ajin, First, you can take a look at the restart case in L3C1 case: https://github.com/iurnus/scripps_kaust_model/tree/master/coupler/L3.C1.coupled_RS2012_ring/runCase.restart Maybe you can take a look at data file: # Time stepping parameters &PARM03 # startTime = 1800., # endTime = 3600., nIter0 = 30., nTimeSteps = 60., In my case, I used the diagnostic package and it is working. I think this illustration case could help you debug this issue, although you may use different setups in your coupled model. You can go ahead to see if uncommenting these lines could help with your case. If these lines are changed, I think you should reset the time in data.cal every time you restart the case. We can further discuss if your restart simulations are still not working. Best, Rui On Mon, Jun 19, 2023 at 7:08 PM ajinn05 ***@***.***> wrote: > Hello Rui, > > I had some difficulties while restarting the simulation with diagnostics > package. > I can't restart the simulation whenever I use diagnostics package. The > error messages were like below: > (PID.TID 0000.0001) *** DIAGNOSTICS_STATUS_ERROR *** from: > DIAGNOSTICS_FILL call > (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: diagName="ETAN ", > expectStatus= 20, pkgStatus= 10 > (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: <== called from the > WRONG place, i.e. > (PID.TID 0000.0001) *** ERROR *** DIAGNOSTICS_FILL: before > DIAGNOSTICS_SWITCH_ONOFF call in FORWARD_STEP > > This error was caused in subroutine DO_STATEVARS_DIAGS because of > 'drag_pkgStatus != ready2fillDiags.' > The model did not set diag_pkgStatus = ready2fillDiags in subroutine > DIAGNOSTICS_SWITCH_ONOFF since myIter != nIter0. > > And I figured out I can solve this problem by changing some lines in > mitCode/mit_run.F. > Since the problem was related to the nIter0 which is not zero for the > restart case, I found that there's two lines commented out in 'mit_run.F': > 173 ! myTimeIn=startTime > 174 ! myIterIn=nIter0 > > So I just wonder if I have to comment out those lines, or it is okay to > uncomment to solve the problem. > > Best, > Ajin > > — > Reply to this email directly, view it on GitHub > <#2>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABUOYU7KXNL3H4DMGQ6FOA3XMEA2BANCNFSM6AAAAAAZMTGKVQ> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- Rui Sun

-- Rui Sun

[ajinn05]

Hi Rui,

I agree that the way you mentioned above will solve this issue because it was working when I tested with nIter0=0 using pickup files.
But I should update data.cal every restart for that case, right?

Also, I tested my simulation with nTimeSteps instead of nEndIter.
And it is still not working..
Should I check other things?

Best,
Ajin

[iurnus]

Yes. You should update data.cal file every time if you run it as "new start".

…

On Mon, Jun 19, 2023 at 10:56 PM ajinn05 ***@***.***> wrote: Hi Rui, I agree that the way you mentioned above will solve this issue because it was working when I tested with nIter0=0 using pickup files. But I should update data.cal every restart for that case, right? Also, I tested my simulation with nTimeSteps instead of nEndIter. And it is still not working.. Should I check other things? Best, Ajin — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABUOYU3RQIUZ2AW53M4GA73XME3P7ANCNFSM6AAAAAAZMTGKVQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Rui Sun