Opened 4 years ago
Closed 21 months ago
#575 closed defect (fixed)
Problems with CRU-NCEP/v7.2/twodeg with orchideedriver ("new driver")
Reported by: | jgipsl | Owned by: | xnwang |
---|---|---|---|
Priority: | major | Milestone: | Not scheduled yet |
Component: | Driver files | Version: | trunc |
Keywords: | Cc: |
Description
Following were corrected but there are still 1 known problem with the orchideedriver (new driver):
- [6040] : correction for initialization of XIOS
- [6041] : correction to run with forcing time step 6h. Note a variable could be used instead of one_day/3.0.
Following have been tested succesfully with ORCHIDEE/trunk rev 6041
- OOL_SEC_STO_FG3nd using WFDEI_GPCC/v2 halfdeg, on global and regional domain. Tests are done for a couple of days at irene.
- OOL_SEC_STO_FG3nd using CRU-NCEP/v7.2/halfdeg, on global and regional domain. Tests are done for a couple of days at irene.
Problem: Using CRU-NCEP/v7.2/twodeg forcing
Running on the global grid, using the default values do not work. Having following in run.def do not work:
WEST_EAST = -180.0, 180.0 SOUTH_NORTH = -90.0, 90.0
Error message:
Zoom forcing : lon = -180.000000000000 180.000000000000 Zoom forcing : lat = -90.0000000000000 90.0000000000000 forcing_givegrid:: nbpoint_loc= 5220 forcing_givegrid:: nbland_loc= 5219 FATAL ERROR FROM ROUTINE forcing_givegrid --> nbpoint_loc and nbland_loc do match --> The calculation of land points is not correct -->
Running on regional grid works. For example following works:
WEST_EAST = -180.0, 180.0 SOUTH_NORTH = -80.0, 80.0
Change History (6)
comment:1 Changed 4 years ago by jgipsl
- Milestone set to ORCHIDEE 3.0
comment:2 Changed 4 years ago by aducharne
- Milestone changed from ORCHIDEE 3.0 to ORCHIDEE 4.0
- Owner changed from somebody to jpolcher
- Status changed from new to assigned
comment:3 Changed 4 years ago by luyssaert
- Milestone changed from ORCHIDEE 4.0 to Not scheduled yet
- Version set to trunc
comment:4 Changed 3 years ago by xnwang
comment:5 Changed 2 years ago by jgipsl
- Owner changed from jpolcher to xnwang
Check if this is ok also in trunk and ORCHIDEE_2_2. If so, the ticket can be closed.
comment:6 Changed 21 months ago by jgipsl
- Resolution set to fixed
- Status changed from assigned to closed
This is ok in the trunk and ORCHIDEE_2_2 (3 years tested ok).
Note: See
TracTickets for help on using
tickets.
This bug is fixed now in the recent version r7119 of trunk, by modifying forcing_tools.f90.