#1795 closed Bug (invalid)
Boundary files for LIM3 are not found in a subdirectory
Reported by: | andrea.gierisch | Owned by: | nemo |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | LIM3 | Version: | v3.6 |
Severity: | Keywords: | BDY LIM* namelists open_boundaries v3.6 | |
Cc: |
Description (last modified by nicolasmartin)
I want to provide BDY sea ice data for LIM3 at the boundaries of a regional domain. If I put these files into a subdirectory, the file for siconcat is not found by NEMO.
I use http://forge.ipsl.jussieu.fr/nemo/svn/branches/2015/nemo_v3_6_STABLE/NEMOGCM/NEMO revision 7214
key_bdy key_lim3
Fix
The problem arises when NEMO checks whether the ice input is from LIM2 or LIM3. For me it helps to include the directory name cn_dir in front of the filename in NEMOGCM/NEMO/OPA_SRC/BDY/bdydta.F90 in lines 674, 676, and 679:
671 IF( nn_ice_lim_dta(ib_bdy) .eq. 1 ) THEN 672 ! Test for types of ice input (lim2 or lim3) 673 ! Build file name to find dimensions 674 clname= TRIM( cn_dir )//TRIM(bn_a_i%clname) 675 IF( .NOT. bn_a_i%ln_clim ) THEN 676 WRITE(clname, '(a,"_y",i4.4)' ) TRIM( cn_dir )//TRIM( bn_a_i%clname ), nyear ! add year 677 IF( bn_a_i%cltype /= 'yearly' ) WRITE(clname, '(a,"m" ,i2.2)' ) TRIM( clname ), nmonth ! add month 678 ELSE 679 IF( bn_a_i%cltype /= 'yearly' ) WRITE(clname, '(a,"_m",i2.2)' ) TRIM( cn_dir )// TRIM( bn_a_i%clname ), nmonth ! add month 670 ENDIF
Commit History (0)
(No commits)
Change History (7)
comment:1 Changed 7 years ago by nicolasmartin
- Description modified (diff)
comment:2 Changed 7 years ago by clem
- Resolution set to invalid
- Status changed from new to closed
The general rule for running simulations is to put all the forcing files and the executables (nemo, xios) in the same directory.
comment:3 Changed 7 years ago by nemo
- Keywords namelists added; namelist removed
comment:4 Changed 6 years ago by nemo
- Keywords LIM* added; LIM3 removed
comment:5 Changed 6 years ago by nemo
- Keywords release-3.6* added
comment:6 Changed 6 years ago by nemo
- Keywords release-3.6* removed
comment:7 Changed 22 months ago by nemo
- Keywords v3.6 added
When you insert a piece of fortran code in Trac, it's smarter to use the specific processor {{{#!f ... }}} to highlight the syntax.