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

Status
Not open for further replies.

samrabin

Sam Rabin
Member
I'm getting this error message when trying to perform a single-point run. The case directory is at /glade/u/home/samrabin/cases_ctsm/ts_20220602_285_-10. I extracted (I think) all relevant data via subset_data, and indeed did this for a different point without any issues earlier in the day. Any suggestions?
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I don't have much experience with this nuopc configuration yet, but it seems like your forcing data is for 1979-1982, but you are setting your model run for 1991 to 2010, so all of your data is before yearFirst.
 

samrabin

Sam Rabin
Member
Huh. How are you determining that, and how do I fix it? Here's what I see from the relevant group in ./xmlquery -p DATE:
Code:
Results in group run_begin_stop_restart
    REST_DATE: -999
    RUN_REFDATE: 0001-01-01
    RUN_STARTDATE: 1978-01-01
    STOP_DATE: -999
 

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I see this in your datm.streams.xml, e.g., for solar:

<year_first>1991</year_first>
<year_last>2010</year_last>
<year_align>1991</year_align>

I think these are being set in env_run.xml:

<entry id="DATM_YR_ALIGN" value="$DATM_YR_START">
<entry id="DATM_YR_START" value="1991">
<entry id="DATM_YR_END" value="2010">

So try changing those settings.
 

samrabin

Sam Rabin
Member
Great, thanks! I have no idea why those were set to those values. I also got tripped up by doing ./xmlquery -p YEAR instead of ./xmlquery -p YR
 
Status
Not open for further replies.
Top