Opened 10 years ago
Closed 9 years ago
#49 closed defect (fixed)
Troubles when date up to 9999 years
Reported by: | ymipsl | Owned by: | ymipsl |
---|---|---|---|
Priority: | minor | Component: | XIOS |
Version: | 1.0 | Keywords: | |
Cc: | acc@… |
Description
Actually string date match only 4 digits. Extend it to take more digits
Yann
Change History (2)
comment:1 Changed 9 years ago by ymipsl
comment:2 Changed 9 years ago by ymipsl
- Cc acc@… added
- Resolution set to fixed
- Status changed from new to closed
Solved in rev r494
Note: See
TracTickets for help on using
tickets.
Mail from Andrew Coward about the ticket
Seb/Yann?, I have a colleague who has hit a snag with the io servers for a GYRE run doing more than 10,000 years.
The server throws up this error from date.cpp:
I can avoid the problem by putting a mod operator on nyear in iom_init:
becomes:
but this only works if the run restarts at the 10000 year boundary and I'm unclear what happens to the time axis on the server side in this case. Looking at the XIOS code, it appears that the year may be hard-limited to 4 characters, e.g.:
date.cpp, line 63:
but I'm unclear whether or not this matters.
Maybe all that is needed is to adapt the cldate string format in the same way as is done in iom_sdate:
but I need confirmation that the XIOS servers can cope.
I haven't raised a ticket because I can't decide if this is a NEMO or a XIOS issue.
Best regards