# File DOME\_domcfg.nc\* not found **URL:** \ **Category:** v4.2.x\ **Created:** [31 October 2023 13:58 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582 "2023-10-31T13:58:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![banmianyu](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@banmianyu](https://nemo-ocean.discourse.group/u/banmianyu)\ **Post date:** [31 October 2023 13:58 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/1 "2023-10-31T13:58:47Z")
Hi everyone I want to run the test “DOME” in NMEO-4.2.0. The compilation went very smoothly, but when I ran the ./nemo, ocean.output file showed an error “File DOME\_domcfg.nc\* not found”. Anyone can tell me how can I find or generate this file? Thanks~ ---
**Author:** ![robinson](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@robinson](https://nemo-ocean.discourse.group/u/robinson)\ **Post date:** [1 November 2023 08:55 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/2 "2023-11-01T08:55:54Z")
Hei, It’s not included in the input files when you download the config ? /robinson ---
**Author:** ![banmianyu](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@banmianyu](https://nemo-ocean.discourse.group/u/banmianyu)\ **Post date:** [1 November 2023 13:27 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/3 "2023-11-01T13:27:47Z")
Hi Robinson Thank you for your reply. All files in the DOME file do not include the “DOME\_domcfg.nc” file. Other tests usually run without input files, or provide python scripts for generating input files (e.g. ICE\_AGRIF). Can someone tell me if I’m missing something? ---
**Author:** ![robinson](https://avatars.discourse-cdn.com/v4/letter/r/848f3c/32.png) [@robinson](https://nemo-ocean.discourse.group/u/robinson)\ **Post date:** [1 November 2023 18:36 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/4 "2023-11-01T18:36:27Z")
Hei, I don’t know the DOME config, but this input file contains the domain grid, bathymetry etc… so it is rather user dependant. However, if you check the tools available in your mo code, you’ll notice there are indeed dedicated tools. Hope this helps, ---
**Author:** ![jchanut](https://yyz2.discourse-cdn.com/free1/user_avatar/nemo-ocean.discourse.group/jchanut/32/9_2.png) [@jchanut](https://nemo-ocean.discourse.group/u/jchanut)\ **Post date:** [3 November 2023 15:15 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/5 "2023-11-03T15:15:00Z")
Hi, The DOME case has been designed to test the embedding procedure. As such, it indeed requires that input parent and child grids are provided and adjusted, hence created offline thanks to the DOMAINcfg tool. If you go in the `/tool/DOMAINcfg/tests/DOME` directory you’ll find namelists to create parent and child meshes. After compiling the `DOMAINcfg` tool, you should be able to retrieve the input files by typing `./make_domain_cfg.exe` in the same directory. Nevertheless, if your wish is to run DOME without any zoom, you can simply set the first line of `AGRIF_FixedGrids.in` file to 0 (or compile without `key_agrif` defined), and set `ln_read_cfg=.false.` in your `namelist_cfg`. Domain will be created online in that case. ---
**Author:** ![banmianyu](https://avatars.discourse-cdn.com/v4/letter/b/8baadc/32.png) [@banmianyu](https://nemo-ocean.discourse.group/u/banmianyu)\ **Post date:** [12 November 2023 15:32 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/6 "2023-11-12T15:32:53Z")
Hi Thank you for your detailed instructions. I can run DOME without agrif for now, but there are still some problems with the addition of agrif. There are three namelist files in the /tool/DOMAINcfg/tests/DOME directory, and it is clear that namelist\_cfg is used to generate the parent mesh. I am not sure which of the other two(1\_namelist\_cfg and 1\_namelist\_cfg\_z180) is used to generate the child mesh, so I generated two domain\_cfg.nc files based on these two namelist\_cfg files as the child mesh files for the DOME test. Unfortunately, no matter which child mesh file is used, running . /nemo produces the following error: ```auto ===>>> : E R R O R =========== ==> Child Bathymetry is NOT correct near boundaries. ===>>> : E R R O R =========== ==> Averaged Bathymetry does not match parent volume ``` Can you tell me what the problem is? All namelist files I have not made changes. Thanks~ ---
**Author:** ![jchanut](https://yyz2.discourse-cdn.com/free1/user_avatar/nemo-ocean.discourse.group/jchanut/32/9_2.png) [@jchanut](https://nemo-ocean.discourse.group/u/jchanut)\ **Post date:** [14 December 2023 14:49 UTC](https://nemo-ocean.discourse.group/t/file-dome-domcfg-nc-not-found/582/7 "2023-12-14T14:49:42Z")
Hi, I don’t know if you still have the problem ? I just checked in branch\_4\_2@ecd77527 that: - Generating input meshes for `DOME` with `DOMAINcfg` tool and with default namelists (i.e. `namelist_cfg` for parent and `1_namelist_cfg` for child in `/tools/DOMAINcfg/tests/DOME`) is ok. - Using these meshes as inputs (e.g. `domain_cfg.nc` and `1_domain_cfg.nc` files) and the default namelists, `AGRIF_FixedGrids.in`, etc… contained in `/tests/DOME/EXPREF`), nemo passes sucessfully the initialization phase.