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

Skagit Model Updates #10

Open
1 task
ChristinaB opened this issue Jun 6, 2018 · 7 comments
Open
1 task

Skagit Model Updates #10

ChristinaB opened this issue Jun 6, 2018 · 7 comments

Comments

@ChristinaB
Copy link
Contributor

ChristinaB commented Jun 6, 2018

Goal for September - @keckje

Historical time period next steps

  • 1980-2010 hourly NNRP model runs for distributed 241 stations
@ChristinaB
Copy link
Contributor Author

ChristinaB commented Jun 27, 2018

Updates from AESI-USIT:
Model run location Hyak: /civil/shared/ecohydrology/Skagit/network

  • Restart 1915, 1960, MACA model runs
    Skagit.150.SA.modellist.historic_1915_1960
    Skagit.150.SA.modellist.MACA1
    Skagit.150.SA.modellist.MACA2
    Skagit.150.SA.modellist.MACA3
    see putput/output1915, output1960, outputMACA

  • SkagitRiver_nr_Newhalem_abv_Thunder is output from DHSVM listed in the 'Other' location list
    C:\Users\cband\Google Drive\UW Projects\SkagitClimateConsortium\SCLDataTables_January2018draftdelivery\SCLflows\Other_locations_19_historic_draft.zip

  • On the historical files, the first day is often REALLY high. I just ended up deleting those days. -- the initial boundary condition for 1915 was updated to a realistic model output for October (from 2006) rather than totally arbitrary initial conditions.

  • The others thing I noticed: all future files stop at 12/30/2099 … why not 12/31?
    The original model runs had a start date ending at hour 00, but should have been ending on hour 21. This has been updated.

  • Update Nookachamps streamflow output for upstream of Skagit network. The network output should be 10564, now updated from May 2018 version set a 10443
    <NetworkFile_update2017.txt>

10564 32 0.000070 1360.660156 2 10443 SAVE "Nookachamps"
image

  • There were two locations for the Sauk River above Clear Creek. (One was called SaukRiver_abClearCreek_nrDarrington, the other is called
    SR_aboveClearCreek = 13344 = Sauk River above Clear Creek => renamed Sauk_abvClearCreek

SaukRiver_abClearCreek_nrDarrington is actually ClearCreek. = 13375 =>renamed ClearCreek
This has been renamed in <NetworkFile_update2017.txt>
Updates made to names in process_skagit.txt

image

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Jun 27, 2018

Batch Model runs submitted 06/29/2018
Walltime 264 hours to complete before July 11 reboot

[cband@ikt1 Skagit]$ qsub -W group_list=hyak-hydro Skagit.150.SA.historic_1915_1960.pbs
8490849.mgmt2.hyak.local
[cband@ikt1 Skagit]$ qsub -W group_list=hyak-hydro Skagit.150.SA.MACA1.pbs
8490850.mgmt2.hyak.local
[cband@ikt1 Skagit]$ qsub -W group_list=hyak-coenv Skagit.150.SA.MACA2.pbs
8490851.mgmt2.hyak.local
[cband@ikt1 Skagit]$ qsub -W group_list=hyak-uwbstem Skagit.150.SA.MACA3.pbs
8490852.mgmt2.hyak.local

@ChristinaB ChristinaB changed the title Skagit Model September Goals Skagit Model Updates Jun 27, 2018
@ChristinaB
Copy link
Contributor Author

ChristinaB commented Jun 28, 2018

Seattle City Light Update

  • Post 'Existing' and 'Other' sites to HydroShare Resource - Ronda to review

  • Rerun Existing and Other for 1950-2099. Use original time periods for 50 yr (?)
    Compare 1975-2025 to 2025-2075
    [1950,2000]
    [1975,2025]
    [2000,2050]
    [2025,2075]
    [2050,2099]

or
time(1,:)=[1961 2010]; historic observed data only, no GCM data
time(2,:)=[2000 2050]; GCM
time(3,:)=[2025 2075]; GCM
time(4,:)=[2050 2099]; GCM

  • Get list of additional sites as delivered for the Landslide Project - Landslide Hazard Deliverable Read and write updated DHSVM forcing files & matching config inputs #1

  • Run Matlab code for extreme statistics for original scope and locations listed for no-bias correction.

  • Compare updated hybrid forcing no-streamflow bias correction results to bias corrected previous results.

  • TBD - streamflow bias correction

  • Deliver Tableau table to ESA

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Jun 28, 2018

@RondaStrauch -

  • please see list above and comment when you are at SCL

  • Review original contract and scope of work.

  • Determine how to scope the final deliverable

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Aug 9, 2018

Compare updated hybrid forcing no-streamflow bias correction results to bias corrected previous results.

  • make new nat flow input files

  • Read in old model, old model bc, new model, nat flows monthly ave figure - for Location X

  • Review structure for bc on pogolinux and code needed to update files - to get scope of work

  • Get Gorge updated raw files into appendix to compare %change into the future

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Aug 20, 2018

  • make new copy of old bias correction code on Pogolinux /data1/mount_sea/Skagit_streamflowbiascorrection

  • Update matlab postprocessing or make new python script to read in C:\Users\cband\Skagit\DHSVM\hydrology_results

concatenate daily streamflow and monthly streamflow 1960-2099
rename into simple format
move into the folder names 'ModelHistoric', 'ModelFuture'
test old code

@ChristinaB
Copy link
Contributor Author

ChristinaB commented Feb 27, 2019

image

2018 Model runs had an error in the network and selecting the link to output Nookachamps. This input has been corrected for future runs, but rerunning all 40 175 years of model runs is outside of the scope of current projects. The 2018 results for Nookachamps have been processed based on 1.98 scaling to the East Fork Nookachamps Creek.
location={'EastForkNookachamps'}
scaledlocation={'Nookachamps'}
Nookachamps_area=88.72 + 94.24 %sqkm
EastForkNookachamps_area=94.24 %sqkm
Nookachamps_frarea=Nookachamps_area/EastForkNookachamps_area

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

1 participant