Nesting problems with AGRIF online

nesting
1

Dear all,
I run a CROCO config on one grid forcing by tide. Initial and boundary conditions are also provided, and everything works well.
I want then go to a nesting config, adding a child grid into the previous config. I produced the child grid and corresponding initial conditions. I created also croco.in.1 and AGRIF_FixedGrids.in. I actived AGRIF and AGRIF_2WAY keys in cppdefs.h.
Normaly, in the doc, it is indicated that only initial conditions are needed for online AGRIF configs, by when I launch the compiled croco config, it stop immediately with these two following messages:
ERROR: keyword not found: forcing
ERROR: keyword not found: boundary
It seems that it complains about forcing and boundary conditions, which should not be.
Does anybody have an idea of what going on ?
Regards

2

Hello, a nested simulation requires the grd, ini, bry, and frc files (or clm and bulk, depending on your cppdefs.h) for the parent domain, and the grd.1, ini.1, and frc.1 files (or bulk.1) for the child domain.

First, check that all the necessary files are present. If the problem persists, there may be a problem with the structure of the croco.in.1 file. Could you share croco.in and croco.in.1 so we can check them?

3

Thanks for interest,
I do not produced the frc.1 file yet for the child grid. Will do it and test.
Regards
croco.in.txt (2.5 KB)
croco.in.1.txt (2.4 KB)

4

Thanks for sharing your files. Your croco.in.1 file has some apparent errors. The NRREC value is set to -1, which defines the initial condition record. If your file croco_ini_mercator_Y2023M11.nc.1 contains only one record, this value should be 1. Another issue I noticed is that the names for boundary and forcing files are missing (even if the boundary file is not used), mainly for structural consistency.

I recommend copying the croco.in file as croco.in.1 and only replacing the names of the child domains. For the NetCDF files that are not used, you could explicitly set them as xxxxx_xx.xx, as they are not being utilized.

5

Thanks for answer.
as I needed to go on, I turn around the problem by using child grids each alone on they own run, using initial and boundary conditions from previous mother grid run. It works :slight_smile: However, I will come back to AGRIF with your recommandations to see if it’s work then.
Regards

1 Like