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

in situ simulations PLUMBER2

S

ShannondeRoos

Shannon
New Member
Hello,

My question is related to single point runs for several selected PLUMBER2 sites (with agriculture) to run with CTSMv5.2 and I work on Derecho.
I am new to single point simulations, so I finally found this useful tutorial to generate the necessary inputdata and user_mods:
CTSM_tutorial_GenericSinglePoint, which helped me run for the points with GSWP3 forcings.

Now, I would like to do a spin-up with the GSWP3 of 20 years, and then run with PLUMBER2 MET-forcings from: /glade/campaign/cesm/cesmdata/inputdata/atm/datm7/CLM1PT_data/PLUMBER2/BE-Lon/CLM1PT_data/. But I noticed this is a single nc-file containing all the variables, which is different from the datmdata structure I see for GSWP3.

My question is if there maybe is also an up to date tutorial to run specifically for PLUMBER2 locations?
Or should I use to generic single point set up from the tutorial, and keep the structure of GSWP3 by splitting the PLUMBER2-file into monthly files and seperate them by PREC,SLR,TPQWL?

Kind regards,
Shannon
 
Sort by date Sort by votes
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
The reason the GSWP3 forcings are split is because since the time resolution is coarse (3-hourly), the different variables require different time-interpolation methods. Solar radiation uses a "coszen" interpolation so that all of the incident solar radiation in a 3-hourly block is partitioned properly into half-hourly time steps that the default model uses. Precipitation uses a "nearest" interpolation such that the same precip rate is used for each half-hourly time step. The other variables use "linear" interpolation.
For single-point site for which the met forcing is generally available at the time resolution of the default model, it is no longer necessary to split the forcing. Generally, the "nearest" interpolation can be used for all variables.
I don't think we have any tutorials specifically for PLUMBER2 sites and out-of-the-box implementation of PLUMBER2 capabilitiy is close but not quite there. But I think you could probably follow the NEON examples which should be fully functional. There is a NEON tutorial here:


@slevis , do you have anything to add here?
 
Vote Upvote 0 Downvote
You must log in or register to reply here.
Top