#1256 closed Bug (fixed)
Position of Gibraltar in ORCA1 configuration
| Reported by: | PiR | Owned by: | nemo |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | OCE | Version: | v3.4 |
| Severity: | Keywords: | OPA straits v3.4 | |
| Cc: |
Description
In the various routines where some straits features are hard-coded (e.g. dommsk.F90, domhgr.F90, diafwb.F90...), it seems that the specified latitudinal index for Gibraltar Strait is not correct in the ORCA1 configuration.
An example -my nemo version is v3.4 revision 4142-
In /DIA/diafwb.F90, line 166 :
Gibraltar is specified as:
! ! =======================
CASE ( 1 ) ! ORCA_R1 configurations
! ! =======================
ii0 = 283 ; ii1 = 283
ij0 = 200 ; ij1 = 200
But when plotting the bathymetry from bathymeter.nc, ij0=200 is a continental point, and the actual Gibraltar is at j=201.
Commit History (0)
(No commits)
Change History (7)
comment:1 Changed 10 years ago by clevy
comment:2 Changed 10 years ago by clevy
- Resolution set to fixed
- Status changed from new to closed
comment:3 Changed 8 years ago by nicolasmartin
- Keywords straits added; strait removed
comment:4 Changed 8 years ago by nicolasmartin
- Keywords nemo_v3_4* added
comment:5 Changed 6 years ago by nemo
- Keywords release-3.4* added; nemo_v3_4* removed
comment:6 Changed 6 years ago by nemo
- Keywords release-3.4* removed
comment:7 Changed 2 years ago by nemo
- Keywords OPA v3.4 added
Note: See
TracTickets for help on using
tickets.
Pierre,
This is a weird part of NEMO for now: some hard coded changes concerning some configurations. This is expected to disappear with the simplification process ongoing this year.
For now, you are using the v3.4 NEMO reference, and using some modified input files for ORCA1. This code is obsolete with these input files.
ORCA1 is not a reference configuration, so that you should get in touch with the person who gave you the files, or change the source code.
Olivier Marti, at LSCE so as you, knows about this