jbuzan@purdue_edu
Member
Hello Everyone,
I am reposting this to POP because this specific error in the cesm.log specifically states POP.
I manually extended the ac_CO2 file for the aircraft to 2300 by repeating the last year and using the NCL cd_inv_calendar function.
However, the simulation executed from 2101--2104-06 and then blew up. The CESM log says that POP was aborting due to "model date maps too far beyond last date". Did anyone encounter this issue with the ocean model? The ocn.log does not have useful information (see below).
Cheers,
-Jonathan
cesm.log.
------------------------------------------------------------------------
------------------------------------------------------------------------
POP aborting...
model date maps too far beyond last date in file
------------------------------------------------------------------------
------------------------------------------------------------------------
ocn.log
data appended to tavg file:
./PR_SSP126_AERA_02_Type_1_Targ_1_5_YEAR_2100_x1_60_5.pop.h.ecosys.nday1.2104-0
7-01.nc
(shr_dmodel_readstrm) file ub: /scratch/snx3000/jbuzan/inputdata/ocn/pop/gx1v6/forcing/ecosys_restore_POP_gx1v6_20170113.nc 1
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) filename = /scratch/snx3000/jbuzan/inputdata/lnd/clm2/isotopes/atm_delta_C14_CMIP6_SSP126_3x1_global_1850-2100_yearly_c181209.nc
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) model_date = 2.1045001141552511E+03
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) mapped_date = 2.1045001141552511E+03
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) nbval = 251
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) time_yr(nbval) = 2.1005000000000000E+03
I am reposting this to POP because this specific error in the cesm.log specifically states POP.
I manually extended the ac_CO2 file for the aircraft to 2300 by repeating the last year and using the NCL cd_inv_calendar function.
However, the simulation executed from 2101--2104-06 and then blew up. The CESM log says that POP was aborting due to "model date maps too far beyond last date". Did anyone encounter this issue with the ocean model? The ocn.log does not have useful information (see below).
Cheers,
-Jonathan
cesm.log.
------------------------------------------------------------------------
------------------------------------------------------------------------
POP aborting...
model date maps too far beyond last date in file
------------------------------------------------------------------------
------------------------------------------------------------------------
ocn.log
data appended to tavg file:
./PR_SSP126_AERA_02_Type_1_Targ_1_5_YEAR_2100_x1_60_5.pop.h.ecosys.nday1.2104-0
7-01.nc
(shr_dmodel_readstrm) file ub: /scratch/snx3000/jbuzan/inputdata/ocn/pop/gx1v6/forcing/ecosys_restore_POP_gx1v6_20170113.nc 1
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) filename = /scratch/snx3000/jbuzan/inputdata/lnd/clm2/isotopes/atm_delta_C14_CMIP6_SSP126_3x1_global_1850-2100_yearly_c181209.nc
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) model_date = 2.1045001141552511E+03
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) mapped_date = 2.1045001141552511E+03
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) nbval = 251
(forcing_timeseries_mod:forcing_timeseries_dataset_update_data) time_yr(nbval) = 2.1005000000000000E+03