Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read and write updated DHSVM forcing files & matching config inputs #1

Open
4 tasks done
ChristinaB opened this issue Mar 26, 2018 · 3 comments
Open
4 tasks done
Assignees

Comments

@ChristinaB
Copy link
Contributor

ChristinaB commented Mar 26, 2018

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Apr 3, 2018

Purpose: Test sensitivity of a 3hr DHSVM model to various forcings. (Save 1hr for future model work in the Model Update Issue)

  • Review synching https://www.atlassian.com/git/tutorials/syncing

  • Make a shorter version starting October 1- Nov 31 2006 3hrly timesteps & 1 hrly datasets for each test

  • add up 3hrly values to get daily total values, apply to first hour in the day, all other hours = zero. Forcing Test 1 (3 hr + 1 hr)

  • Get hourly precip data from station in Skagit for the same time period, convert to 3hr time periods Forcing Test 2

  • Get precip data from WRF NNRP hourly data (not daily) convert to 3hr time periods Forcing Test 3

@ChristinaB
Copy link
Contributor Author

See https://github.com/ChristinaB/Incubating-a-DREAM/blob/master/Sauk_DHSVM_modeldata/Input.sauk.base.2006flood

Line 174 -181 have one location for the lowest elevation in the Sauk.

I recommend make the following names consistent with your climate forcing tests (e.g. 1sthour):
climate forcing folder name or input file name (see line 181 e.g. DHSVMinput_Sauk57_raw_liv/sauk_base_station.data_48.34375_-121.34375 yours could be
sauk_1base_1sthour/sauk_base_station.data_48.34375_-121.34375

output forcing folder name (see line 5396 output/DHSVMout_sauk_1sthour) Go to the output folder. Type > mkdir DHSVMout_sauk_1sthour now the folder exists and when you run the model check for results there.
title of config file (e.g. sauk_1base_1sthour.config)
climate forcing file - this is fine for when you have one station. sauk_base_station.data_48.34375_-121.34375

to be coded up for the full grid, the name should be data_48.34375_-121.34375

@ChristinaB
Copy link
Contributor Author

Modelstate -
the config file looks in the folder in Line 5397

Initial State Directory = modelstate/

In the modelstate/ directory, it must have the date name in the file the same as the start date
on Line 90
Model Start = 10/01/2006-00 # Model start time (MM/DD/YYYY-HH)

If you change the start date, copy and rename the files in the modelstate directory. There can be a different version for each start date in your experiments.

Channel.State.11.01.2006.00.00.00
Interception.State.11.01.2006.00.00.00.bin
Snow.State.11.01.2006.00.00.00.bin
Soil.State.11.01.2006.00.00.00.bin

@ChristinaB ChristinaB changed the title Read and write updated DHSVM forcing file Read and write updated DHSVM forcing files & matching config inputs May 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants