Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

”calendar dates must be increasing“ for compset CIAF

Hi, everyoneQuestion 1:I am running CESM1_2_0. The model is ok when I only set " id="RUN_STARTDATE"  value="1948-01-01" " for compset B. But it cannot run if I run it for compset CIAF. Error can be seen as followed. More details can be seen in attachment. --------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1001.NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--------------------------------------------------------------------------
(shr_sys_abort) ERROR: (shr_stream_verifyTCoord) ERROR: calendar dates must be increasing
(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping
--------------------------------------------------------------------------
mpiexec has exited due to process rank 0 with PID 28730 on
node gg2319 exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpiexec (as reported here).
-------------------------------------------------------------------------- If I set " id="RUN_STARTDATE"  value="0001-01-01", then model for compset CIAF run successfully. But it is not reasonable, because the inputdata for compset CIAF is COREv2. And COREv2 is observed data which are from 1948 to 2009.I searched the error in this forum. Someone said that time coordinate variable must be strictly increasing for each time. Here is a similar question in website "https://bb.cgd.ucar.edu/node/1002084". And I checked the time coordinate variable of some data. There are all increasing. But all of these are ok on one machine of westgrid in Canada. I think it may be a problem with input data. But I think that the input data should be the same.
Question 2:From one thread, I know two input nc files in directory /home-gg/users/nscc670_YZX/CESM/inputdata/lnd/clm2/ndepdata/. fndep_clm_simyr1849-2006_1.9x2.5_c091106.ncfndep_clm_simyr1849-2006_0.9x1.25_c091106.ncThe time coordinate variable of these two files are not strictly increasing. Using ncdump -v time fndep_clm_simyr1849-2006_1.9x2.5_c091106.nc to see detail,time = 674885, 675250, 675615, 675980, 676345, 676710, 677075, 677440,
677805, 678170, 678535, 678900, 679265, 679630, 679995, 680360, 680725,
681090, 681455, 681820, 682185, 682550, 682915, 683280, 683645, 684010,
684375, 684740, 685105, 685470, 685835, 686200, 686565, 686930, 687295,
687660, 688025, 688390, 688755, 689120, 689485, 689850, 690215, 690580,
690945, 691310, 691675, 692040, 692405, 692770, 693135, 693500, 693865,
694230, 694595, 694960, 695325, 695690, 696055, 696420, 696785, 697150,
697515, 697880, 698245, 698610, 698975, 699340, 699705, 700070, 700435,
700800, 701165, 701530, 701895, 702260, 702625, 702990, 703355, 703720,
704085, 704450, 704815, 705180, 705545, 705910, 706275, 706640, 707005,
707370, 707735, 708100, 708465, 708830, 709195, 709560, 709925, 710290,
710655, 711020, 711385, 711750, 712115, 712480, 712845, 713210, 713575,
713940, 714305, 714670, 715035, 715400, 715765, 716130, 716495, 716860,
717225, 717590, 717955, 718320, 718685, 719050, 719415, 719780, 720145,
720510, 720875, 721240, 721605, 721970, 722335, 722700, 723065, 723430,
723795, 724160, 724525, 724890, 725255, 725620, 725985, 726350, 726715,
727080, 727445, 727810, 728175, 728540, 728905, 729270, 729635, 730000,
730365, 730730, 731095, 731460, 731460, 731825 ;Two to last and three to last are the same. Is there any problem with these two nc files?
Thanks.zhixiong
 
 
Top