Opened 2 years ago

Closed 8 months ago

#2127 closed Bug (fixed)

BDY boundary Forcing files not read correctly

Reported by: markhg77 Owned by: sciliberti
Priority: low Milestone:
Component: BDY Version: release-3.6
Severity: major Keywords: BDY, SBC
Cc: markhg77@…

Description

Context

When trying to run a regional configuration using external data, the model crashes when trying to open the boundary file:

File ./bdy_s @@@@@@@@.nc* not found

The error is reproducible with the latest revision of 3.6.

Analysis

After extensive debugging efforts, I was unable to locate where the file name is corrupted. #2103 seems to be a fairly similar issue, but is related to trunk not 3.6.

Fix

Since I am not aware of the source of this issue I've attached a tarball containing all the input files and namelist I use. After unpacking these can be found in NEMOGCM2/CONFIG/MY_ORCA2_LIM3/EXP00

Commit History (0)

(No commits)

Attachments (6)

bdy_s.nc (66.5 KB) - added by markhg77 2 years ago.
bdy_t.nc (65.1 KB) - added by markhg77 2 years ago.
namelist_cfg (16.8 KB) - added by markhg77 2 years ago.
coordinates.drake.bdy.nc (1.8 KB) - added by markhg77 2 years ago.
coordinates.east.bdy.nc (1.8 KB) - added by markhg77 2 years ago.
coordinates.north.bdy.nc (1.8 KB) - added by markhg77 2 years ago.

Download all attachments as: .zip

Change History (10)

Changed 2 years ago by markhg77

Changed 2 years ago by markhg77

Changed 2 years ago by markhg77

comment:1 Changed 2 years ago by markhg77

I should also add that the default input files for the reference configuration of ORCA2_LIM3 are used and simply subsetted to the desired region. Please email me if you would like me to send a link where you can download all the files.

Changed 2 years ago by markhg77

Changed 2 years ago by markhg77

Changed 2 years ago by markhg77

comment:2 Changed 2 years ago by markhg77

In the end I was able to find the source of the problem, which was simply related to the order of the dimensions of the variables in the boundary files. The spatial dimension needs to be the last dimension. However, the error which is reported by NEMO does not point the user at all in this direction, instead reporting a "file not found" error. I think it would save a lot of time if the dimensions of bdy files where checked, and errors related to this reported as such. Somehow the incorrect dimension ordering leads to the file name becoming corrupted, perhaps this should be looked into…

comment:3 Changed 2 years ago by clevy

  • Owner set to sciliberti
  • Status changed from new to assigned

comment:4 Changed 8 months ago by smasson

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.