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

ERROR: LVD not found, all data is before yearfirst

Dear all:


I want to run standalone CAM5 with historical SST forcing. I had successfully performed FAMIPC5 compset running as the ccsm.exe type building.

Now I choose to build the model under atm/cam/bld/, the conventional cam build method. In this type run, I have successfully run with climate-sst.

I change several namelist parameters for running historical SST. I add sstcyc = .false. in atm_in, then change the sst data to

" sst_HadOIBl_bc_0.47x0.63_1850_2009_c101028.nc" in docn.stream.txt.

And set docn_ocn_in as:
&shr_strdata_nml
dataMode = 'SSTDATA'
domainFile = '......./inputdata/atm/cam/ocnfrac/domain.camocn.0.47x0.63_gx1v6_090408.nc'
streams = 'docn.stream.txt 1850 1850 2009 '
vectors = 'null'
/

Then I change several timemgr paras as
&seq_timemgr_inparm
atm_cpl_dt = 1800
restart_option = 'monthly'
start_ymd = 19790101
stop_n = 31
stop_option = 'nyears'

The above are the only namelist modification I changed, all other settings is generated by:

./build-namelist -csmdata .../inputdata -config config_cache.xml

The ERROR: LVD not found, all data is before yearfirst

after (seq_mct_drv) : Model initialization complete.
 

tcraig

Member
This is definitely a problem with the stream input file and/or stream data.

it looks like the dataset is 1850-2009 based on the name, i'll assume that.

and it looks like you want to start in 1979, right?

the stream input,

streams = 'docn.stream.txt 1850 1850 2009 '

is setting the stream align year to 1850, first year to 1850, and last year to 2009.
that looks ok. there should be more output in other log files, in particular, look in the
ocn.log file and see what's there.
 
Top