Opened 3 years ago
Closed 3 years ago
#2633 closed Bug (duplicate)
Domcfg not compatible with NEMO trunk/future 4.2
| Reported by: | cbricaud | Owned by: | systeam |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | DOM | Version: | trunk |
| Severity: | major | Keywords: | |
| Cc: |
Description
Context
For NEMO trunk/future 4.2 , halo ( north-fold and E-W cyclic bands ) need to be removed from configuration files ( bathy, runoffs, weight,...)
Domcfg has not been changed and apply the E-W and north foldings, whereas the halos have disappear
Remark: setting jperio=0 (no north and cyclic E-W foldings) in DOMcfg namelist instead of 4 (north and cyclic E-W foldings) is not a good solution because:
jperio is writtend in domain_cfg.nc and read by NEMO
jperio=0 set all the boundary cells to 0.
Analysis
...
Fix
...
Commit History (0)
(No commits)
Change History (2)
comment:1 Changed 3 years ago by cbricaud
- Component changed from TOP to DOM
- Severity changed from minor to major
comment:2 Changed 3 years ago by jchanut
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
Changes done in #2638 make DOMAINcfg now compatible with 4.2_RC (hence with online addition of halos depending on boundary conditions). Hence input coordinates and bathymetry files, provided as inputs to the tool, must be cropped offline if jperio/=0. Namelist input sizes Ni0glo/Njglo0 refers to the global domain excluding halos.