# AGRIF nest & no cyclic east-west boundaries (host)

**URL:** <https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706>\
**Category:** v4.2.x\
**Tags:** AGRIF\
**Created:** [28 May 2024 07:34 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706 "2024-05-28T07:34:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sykim](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@sykim](https://nemo-ocean.discourse.group/u/sykim)\
**Post date:** [28 May 2024 07:34 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706/1 "2024-05-28T07:34:24Z")

</div>

Hi all,

I’m trying to refine a northwestern Pacific with NEMO4.2.x.  
Below is AGRIF\_FixedGrids.in  
1  
65 210 250 416 5 5 3  
0  
The parent domain (ORCA05) has no cyclic east-west boundaries (nx = 720 & ny = 510).

However, the model stopped with below error message.  
STOP  
AGRIF zoom is East-West cyclic, imin must = 1

This is strange, because the nest domain doesn’t cross the cyclic points (northwestern Pacific).  
Do I need to set additional options in namelist\_cfg or modify the number in AGRIF\_FixedGrids.in?

Meanwhile, this model stably runs with cyclic east-west boundaries in parent domain (722x511).

Many thanks for any hints or help!  
Sang-Yeob

---

<div class="post-metadata">

**Author:** ![Franziska](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@Franziska](https://nemo-ocean.discourse.group/u/Franziska)\
**Post date:** [30 May 2024 07:25 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706/2 "2024-05-30T07:25:21Z")

</div>

Hi Sang-Yeob,

although the parent domain “lost” its dublicated columns and rows along the boundaries with the transition from [NEMO4.0.x to 4.2.x](https://sites.nemo-ocean.io/user-guide/migration.html) it still has cyclic east-west bundaries. jperio should be 6 in domain\_cfg.nc.

Your nest obviously doesn’t have cyclic boundaries, consequently jperio must be 0 in 1\_domain\_cfg.nc.

How did you create your (1\_)domain\_cfg.nc files? [Here are the guidlines](https://sites.nemo-ocean.io/user-guide/zooms.html#mesh-preprocessing) for how to create a consistent set of input-files.

Franziska

---

<div class="post-metadata">

**Author:** ![sykim](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@sykim](https://nemo-ocean.discourse.group/u/sykim)\
**Post date:** [5 June 2024 06:43 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706/3 "2024-06-05T06:43:59Z")

</div>

Hi Franziska,

Thank you for your kind suggestions. Following your suggestion, I’ve tested the model with new domain cfg files (host’s jperio=6 and nest’s jperio=0). However, the model was stopped due to the volume (averaged bathymetry) mismatch between the host and nest. I’ve tried some more tests by changing some options, but it’s still in swamp.

Attached files are the (1\_)namelist\_cfgs, which are for the current model test.  
Many thanks again for any hints or help!

Best wishes,  
Sang-Yeob

 ![1_namelist_cfg](https://global.discourse-cdn.com/free1/uploads/nemo_ocean/original/1X/13a67f5141fac511efade8d639ec3fb10cc86e61.jpeg)  
 ![namelist_cfg](https://global.discourse-cdn.com/free1/uploads/nemo_ocean/original/1X/dc9547b81b27270d4c50fffb96e5e8d3c35dae73.jpeg)

---

<div class="post-metadata">

**Author:** ![Franziska](https://avatars.discourse-cdn.com/v4/letter/f/8797f3/32.png) [@Franziska](https://nemo-ocean.discourse.group/u/Franziska)\
**Post date:** [5 June 2024 11:40 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706/4 "2024-06-05T11:40:59Z")

</div>

Hi Sang-Yeob!

I don’t know all the details of how the connection between the parent and child bathymetries is done in the current version of the DOMAINcfg tool, so the following is kind of “just a guess” (maybe @jchanut could give some better advice):

In your namelist\_cfg I spotted `bathy_updated.nc` as topography file for the unnested ORCA05 configuration. From the file-name, I assume you provide the updated parent bathymetry from the old (NEMO3.6-based ?) NPAC10 configuration. This would include modifications according to the connection between parent and child, as implemented in earlier versions of the nesting tools and additionally according to the partial cells definition you had for that configuration. (Is the latter the same as in your current namelist\_ref? If not, don’t forget to add the correct values to namelist\_cfg.) I could imagine some interference here…  
So my suggestion is to provide the original ORCA05 bathy\_meter.nc (720x510) file to generate the new (1\_)domain\_cfg.nc files.

Franziska

---

<div class="post-metadata">

**Author:** ![sykim](https://avatars.discourse-cdn.com/v4/letter/s/dec6dc/32.png) [@sykim](https://nemo-ocean.discourse.group/u/sykim)\
**Post date:** [14 June 2024 04:29 UTC](https://nemo-ocean.discourse.group/t/agrif-nest-no-cyclic-east-west-boundaries-host/706/5 "2024-06-14T04:29:13Z")

</div>

Hi Franziska!

Many thanks again for your kind comments. The ocean only model (NWPAC10) with the host domain as 720x510 is now running!

Following your suggestion, the (1\_)domain\_cfgs were generated by using the original ORCA05 bath\_meter.nc (720x510).  
but,

1. the jperio is 4 in domain\_cfg.nc
2. ln\_dept\_mid should be .true. in AGRIF zoom. (Reference is false)
3. ppsur, ppa0, ppa1 = 999999.0 ( references are 999998.0)

(In the previous domain\_cfg, the updated parent bathymetry (bathy\_updated.nc) was from the (NEMO3.6-based) NPAC10 configuration =\> Yes)

Sang-Yeob
