NTIMES should always be 1 in croco.in.1 (for AGRIF child)?

Hi all,
I would like to understand how to set the value of NTIMES in croco.in.1 whild using AGRIF. Is it always NTIMES=1 ?

Here is the benguela configuration I use:
parent

BENGUELA TEST MODEL
720 ntimes Total number of timesteps for 3D equations.
3600.00 dt Timestep [sec] for 3D equations
60 ndtfast Number of 2D timesteps within each 3D step.
1 ninfo Number of timesteps between runtime diagnostics.

Child:
BENGUELA TEST MODEL ZOOM LEVEL #1
1 ntimes Total number of timesteps for 3D equations.
1200.00 dt Timestep [sec] for 3D equations
60 ndtfast Number of 2D timesteps within each 3D step.
1 ninfo Number of timesteps between runtime diagnostics.

I’m a little confused because @andres use:
ratio_grid=3 (for exemple)
NTIMES_child=NTIMES_parent*3

But for me, NTIMES=1 works well. I checked the netcdf output, with a record every step:
parent file
history: LDEFHIS, NWRT, NRPFHIS / filename
T 1 0
CROCO_FILES/croco_his.nc

scrum_time = 0, 3600, 7200, 10800, 14400, 18000, 21600, 25200, 28800, 32400,
36000, 39600, 43200, 46800, 50400, 54000, 57600, 61200, 64800, 68400,
72000, 75600, 79200, 82800, 86400,

=> we have a record every dt=3600 s (dt of parent child)

child file
history: LDEFHIS, NWRT, NRPFHIS / filename
T 1 0
CROCO_FILES/croco_his.nc.1

scrum_time = 0, 1200, 2400, 3600, 4800, 6000, 7200, 8400, 9600, 10800,
12000, 13200, 14400, 15600, 16800, 18000, 19200, 20400, 21600, 22800,
24000, 25200, 26400, 27600, 28800, 30000, 31200, 32400, 33600, 34800,
36000, 37200, 38400, 39600, 40800, 42000, 4

=> we have a record every dt=1200 s (dt of parent child)

This seems to be ok with ntimes=1. So when do we need to change this value of ntimes?

Thanks a lot,
Camille

Hi @cmazoyer yes, that is weird indeed. Maybe is not a bug, it is a feature :wink: If it works, it works, don’t fix it.

It also works if you define the way I suggest, and I think it allows you to save the output at a different time step.

1 Like

ok thank you @andres !