Role: user
Climate Options
This page explains every option in Climate Options for WEPPcloud end users:
- what each option is best for,
- what climate data it uses,
- where that data is available,
- how station selection modes work,
- how CLIGEN uses
.parand.prnfiles, - when to use each spatial mode,
- what each advanced option does and when to use it.
Where to find this in WEPPcloud
- Open your run.
- Open Climate Options.
- Choose a climate dataset, station selection mode, and (if available) spatial mode.
- Expand Advanced options only when you need to tune behavior.
Opinionated recommendations
If you want the shortest defensible answer instead of a full option review:
- For probability/risk assessments, start with Stochastic PRISM Modified.
- For historical modeling, start with Observed DAYMET (GRIDMET wind).
Climate Datasets (Each Climate Option)
Vanilla CLIGEN
Suitable for
- Long-term stochastic (probability/risk) analysis.
- Baseline climate generation when you do not need a specific observed historical sequence.
Recommendation
- Use this when you explicitly want plain CLIGEN behavior.
- If your main goal is a probability/risk assessment and Stochastic PRISM Modified is available, prefer that option instead.
Data it uses
- CLIGEN station statistics from the selected station.
- Your selected simulation length (
Number of years to simulate).
Where available
- Broadly available across interfaces/locales.
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1).
Spatial modes available
- Single (
0), Multiple (1). - Interpolated multiple (
2) is not available for this dataset.
Notes
- In Multiple mode, WEPPcloud applies a PRISM revision routine to create per-hillslope climates.
Stochastic PRISM Modified
Suitable for
- Recommended default for probability/risk assessments.
- Stochastic runs where you want PRISM-adjusted climate behavior.
- BAER-style risk/probability workflows when strict historical replay is not required.
Recommendation
- Start here when your question is probabilistic: "What is the range of likely runoff/erosion response over many possible years?"
- Prefer this over observed historical modes when you are not trying to reproduce a specific real-world period.
Data it uses
- CLIGEN station source + PRISM-informed adjustment workflow.
- Stochastic simulation years you choose.
Where available
- Available in many U.S.-centric contexts.
- Blocked in locales configured as GHCN-only in current catalog (
au,alaska,hawaii,nigeria).
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1).
Spatial modes available
- Single (
0), Multiple (1).
Notes
- Marked RAP-compatible in the current catalog.
- In Multiple mode, PRISM revision generates per-hillslope climate files.
Observed DAYMET (GRIDMET wind)
Suitable for
- Recommended default for historical modeling.
- Historical/observed-condition calibration.
- Streamflow and disturbance-validation work where observed weather is preferred.
Recommendation
- Start here when you want to model a real historical period rather than a stochastic climate sequence.
- This is the opinionated first choice for hindcasting, calibration, and other observed-period analyses.
Data it uses
- DAYMET observed daily climate.
- Optional GRIDMET wind fill (when
Use GRIDMET wind when applicableis enabled).
Where available
- Year window in catalog metadata: 1980 to 2024.
- Blocked in GHCN-only configured locales (
au,alaska,hawaii,nigeria).
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1).
Spatial modes available
- Single (
0), Multiple (1), Multiple Interpolated (2).
Notes
- In Multiple mode (
1), PRISM revision is applied after base build. - In Multiple Interpolated mode (
2), build is routed to the DAYMET interpolated hillslope workflow (no PRISM revision step in that branch). - Marked RAP-compatible in the current catalog.
Observed GRIDMET
Suitable for
- Historical/observed-condition modeling using GRIDMET.
- Workflows where observed wind/radiation/dewpoint fields from GRIDMET are desired.
Recommendation
- Use this when you specifically want GRIDMET-native observed fields or need to compare sensitivity against DAYMET.
- If you want one default historical option, prefer Observed DAYMET (GRIDMET wind) first.
Data it uses
- GRIDMET observed daily climate fields.
- Observed year window you provide.
Where available
- Catalog description: 1980 to present.
- Blocked in GHCN-only configured locales (
au,alaska,hawaii,nigeria).
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1).
Spatial modes available
- Single (
0), Multiple (1), Multiple Interpolated (2).
Notes
- In Multiple mode (
1), PRISM revision is applied after base build. - In Multiple Interpolated mode (
2), build uses the GRIDMET interpolated hillslope workflow. - Marked RAP-compatible in the current catalog.
Observed PRISM 800 m (GRIDMET wind)
Use this for continental-US historical modeling when daily rainfall differences between native PRISM cells matter. Select complete calendar years from 1981 through the previous year. Older stored project capability graphs may need an explicit refresh before this option appears.
PRISM supplies daily precipitation, minimum/maximum temperature, dewpoint and solar radiation. GRIDMET supplies shared watershed wind, and the selected CLIGEN station supplies within-day storm structure. Daily PRISM does not provide observed storm duration or intensity.
| Spatial choice | Behavior |
|---|---|
| Single | Uses the native cell nearest the watershed centroid. |
| Multiple | Revises centroid daily forcing with existing monthly PRISM hillslope precipitation ratios and temperature offsets. |
| Multiple climates (nearest PRISM cell) | Uses each hillslope's nearest native cell, with no neighboring-cell averaging or monthly revision. Hillslopes in one cell share unscaled daily weather. |
Existing precipitation scaling options still apply. With Multiple climates, each hillslope file uses the higher of the raw PRISM dew point and the hillslope’s revised daily minimum temperature. The PRN format rounds rainfall to 0.254 mm and temperature to whole Fahrenheit degrees, so trace rain can round to zero. The CLIGEN quality guard and any convergence warnings remain applicable.
Source parquet, conversion diagnostics and retained build attempts are
available under climate/ in the project browser and archives. OpenET and AgFields
accept this mode. OpenET comparisons use matching hillslope/calendar months within
available satellite coverage. AgFields uses each subfield parent hillslope's
prepared climate file and requires crop schedules for the observed years. See the
historic PRISM guide
for source inspection and recovery details.
DEP NEXRAD Breakpoint
Suitable for
- Observed breakpoint-style climate workflows where high-resolution breakpoint data is required.
- Cases where you may want to override daily variables with PRISM/GRIDMET/DAYMET options.
Data it uses
- DEP Mesonet breakpoint climate retrieval by centroid/hillslope coordinates.
- Optional daily-variable overrides:
- PRISM (
tmax,tmin,tdew) - GRIDMET (
tmax,tmin,rad,tdew,w-vl,w-dir) - DAYMET (
tmax,tmin,rad,tdew)
- PRISM (
Where available
- Help text indicates 2007 to present coverage.
- Blocked in GHCN-only configured locales (
au,alaska,hawaii,nigeria).
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1).
Spatial modes available
- Single (
0), Multiple (1).
Notes
- Not marked RAP-compatible in the current catalog.
Future MACA CMIP5
Use this option for climate-change impact analysis with approximately 4 km MACAv2-METDATA projections. Select MACA driving model and scenario above Future start year and Future end year. Twenty models are available with RCP4.5 and RCP8.5, for complete years from 2006 through 2099. New projects and older projects without a saved choice use GFDL-ESM2G · RCP8.5.
MACA supplies daily precipitation and maximum/minimum temperatures. The selected CLIGEN station supplies storm structure and the remaining weather characteristics. The existing PRN representation rounds rain to 0.254 mm and temperatures to whole Fahrenheit degrees before CLIGEN processing.
The data provider is Katherine Hegewisch and John Abatzoglou's Climatology Lab at UC Merced; MACA was originally developed at the University of Idaho and is served through Idaho infrastructure. CCSM4 uses its published r6i1p1 ensemble member; the other offered models use r1i1p1.
Auto, Distance ranking and Multi-factor ranking station choices remain available,
with the existing Single and Multiple spatial choices. This dataset is not
RAP-compatible and remains unavailable in configured GHCN-only locales
(au, alaska, hawaii, nigeria). If a saved selection is invalid, choose a
valid projection explicitly before building. A provider failure does not switch
to another model automatically.
User-Defined Climate (.cli)
Suitable for
- Research and validation runs where you already have a vetted CLIGEN
.clifile.
Data it uses
- Your uploaded
.clifile.
Where available
- Generally available as a user-exposed dataset.
Station selection modes available
- User-defined (
4) only.
Spatial modes available
- Single (
0), Multiple (1).
Notes
- In this mode, Upload .cli is the primary action.
- The Climate summary shows the single-storm deprecation advisory for a file with one event record. WEPP can run a valid individual event file. A successful replacement refreshes the summary and its advisory. The previous climate stays in place if an upload is rejected or its file cannot be parsed.
- Climate build button behavior differs from other modes (upload-driven flow).
- If spatial mode is Multiple, PRISM revision is applied after upload processing.
E-OBS Modified (Europe)
Suitable for
- European observed-climate workflows.
Data it uses
- E-OBS-based modified climate build path for EU locales.
Where available
- EU-only (
allowed_locales = eu).
Station selection modes available
- Auto (
-1), Distance ranking (0), Multi-factor ranking (1), EU heuristic (2).
Spatial modes available
- Single (
0), Multiple (1).
Notes
- Default spatial mode is Multiple in current catalog metadata.
- Not marked RAP-compatible in current catalog.
Region/System-Managed Climate Options
These catalog options exist in code but are not normally exposed in the standard Climate Options dataset picker:
Observed Climate Database(observed_db, mode 6)Future Climate Database(future_db, mode 7)AGDC (Australia)(agdc, mode 10)
These are ui_exposed=False in the current catalog and are primarily system/configuration driven.
Station Selection Mode
Station selection mode controls how WEPPcloud chooses or ranks station candidates for the selected dataset.
Auto (-1)
What it does
- Uses FindClosestAtRuntime behavior.
- The station dropdown is not actively refreshed from ranking endpoints in this mode.
When to use
- Default workflow when you do not need to inspect or force ranked station choices.
Where available
- Most non-user-defined datasets.
Distance ranking (0)
What it does
- Calls the closest-stations endpoint and ranks candidates by distance to the watershed centroid.
When to use
- When nearest-station proximity is your primary criterion.
Where available
- Most standard datasets and several system-managed datasets.
Multi-factor ranking (1)
What it does
- Calls heuristic station ranking.
- For
eulocale this routes to EU heuristic logic; foraulocale it routes to AU heuristic logic.
When to use
- When representativeness is more important than pure distance.
Where available
- Available where the selected dataset includes station mode
1.
EU heuristic (2)
What it does
- Uses the dedicated EU heuristic endpoint.
When to use
- European runs where explicit EU heuristic ranking is desired.
Where available
- In the current catalog, effectively tied to
E-OBS Modified (Europe).
AU heuristic (3)
What it does
- Dedicated AU heuristic endpoint exists in backend.
When to use
- Australia-specific heuristic ranking (advanced/specialized contexts).
Where available
- Backend supports it, but current shipped dataset metadata does not generally expose mode
3directly. - In
aulocale, multi-factor mode (1) already routes to AU heuristic search logic.
User-defined (4)
What it does
- Used with uploaded user-defined
.cliworkflows. - Station list refresh is skipped and station select options are cleared in that flow.
When to use
- When supplying your own climate file.
Where available
User-Defined Climate (.cli)dataset.
Tenerife-specific station mode constraints
When a run uses the Tenerife station catalog (tenerife_stations.db), runtime constraints intentionally narrow options:
- Supported dataset options are reduced to
vanilla_cligenanduser_defined_cli. - Station modes are reduced to:
(-1, 0)forvanilla_cligen(4)foruser_defined_cli
- Unsupported climate/spatial/station combinations are rejected by backend validation.
How CLIGEN Uses .par and .prn Files
CLIGEN is the weather engine that produces the .cli file WEPP uses.
.par files
A station .par file stores long-term monthly climate statistics (for example mean precipitation, wet/dry transition probabilities, and monthly temperature arrays). In WEPPcloud:
- Your station selection resolves to station metadata that includes the
.parpath. - The Station PAR preview panel in Climate Options shows the active station
.parcontents.
.prn files in observed workflows
In observed modes, WEPPcloud typically:
- Builds daily observed series from a source dataset.
- Writes those daily values into CLIGEN
.prnformat. - Calls CLIGEN
run_observed(...)to generate the final.cli.
This pattern is used across observed DAYMET, observed GRIDMET, PRISM-observed style paths, SNOTEL-support paths, and interpolated observed workflows.
Input file specifications
Spatial Climate Modes
Single climate (0)
What it does
- Builds one climate for the watershed.
When to use
- Fastest option.
- Good default for many small-to-medium watersheds.
Multiple climates (1)
What it does
- Produces per-hillslope climate outputs.
- For many modes, this applies the PRISM revision routine after base climate build.
What PRISM revision does (plain language)
- Retrieves PRISM
ppt,tmin, andtmaxrasters for the watershed extent. - Computes watershed-level monthly values and hillslope-level monthly values.
- Revises the base climate to hillslope-specific climates using monthly precipitation scaling plus monthly temperature offsets.
Multiple climates (Interpolated) (2)
What it does
- Uses dedicated interpolated observed-climate build paths.
- For observed DAYMET / observed GRIDMET, uses interpolation (
ObservedPRISM/GridMetPRISM). - For observed PRISM 800 m, the label changes to Multiple climates (nearest PRISM cell) and each hillslope uses its nearest native cell without smoothing or monthly revision.
When to use
- When spatial heterogeneity is important and you are on supported observed modes.
Performance and practical guidance
- Slower than Single.
- In operator experience, this mode has produced some of the best calibrated results for certain Pacific Northwest watersheds.
- It is often a strong candidate for larger watersheds or watersheds with micro-climate variation.
Select an available observed DAYMET, GRIDMET or PRISM 800 m dataset to enable this option; no page reload is needed. It is disabled for datasets that do not support this spatial method. The calibration experience above concerns the existing interpolated methods, not a validation claim for the new PRISM method.
Recommended spatial-mode decision path
- Start with Single for speed and first-pass calibration.
- Move to Multiple when hillslope-scale variation appears important.
- Try Multiple Interpolated on supported observed modes when you need higher spatial climate fidelity and can afford extra runtime.
Advanced Options
The CLIGEN seed is available for every station catalog, including Tenerife. The remaining advanced controls are visible only for non-Tenerife station-catalog workflows.
CLIGEN seed
Function
- Optionally sends an explicit integer random seed to CLIGEN. Valid values are
0through99999.
Purpose
- Reproduce the same CLIGEN random stream when the climate inputs, selected station, CLIGEN binary, and seed are unchanged.
Recommended use cases
- Enter a seed when a stochastic climate must be repeatable across rebuilds or when comparing scenarios that should use the same generated weather stream.
- Leave the field blank to preserve WEPPcloud's established mode-specific
defaults. Plain stochastic and observed builds let CLIGEN choose its normal
default behavior; PRISM/E-OBS/AGDC modified builds retain their established
effective seed of
12345.
Important behavior details
- The seed is stored with the project and is passed through queued climate builds, batch clones, and supported spatial build paths.
- A seed supports reproducibility, not secrecy or cryptographic security. Changing the CLIGEN version, station parameters, observations, or other climate inputs can still change the generated climate.
- Clearing the field removes the explicit override and restores the default behavior above.
Use GRIDMET wind when applicable
Function
- Toggles the run-level
use_gridmet_wind_when_applicablebehavior.
Purpose
- Injects GRIDMET wind fields for observed workflows that require wind support.
Recommended use cases
- Enable when observed mode requires wind forcing and GRIDMET wind is appropriate.
Adjust MX .5 P Values
Function
- Toggles
adjust_mx_pt5behavior during CLIGEN observed processing.
Purpose
- Scales monthly
MX .5 Pintensity values based on observed/localized monthly precipitation ratio logic.
Recommended use cases
- When station-normal intensity assumptions appear mismatched with your local observed precipitation behavior.
Important behavior details
- Scaling is constrained in code (clamped to a bounded factor range).
- Very low-precipitation months can be skipped by adjustment logic.
- If CLIGEN still fails to converge, the run surfaces:
CLIGEN failed to converge, try selecting different station or setting Adjust MX .5 P Values.
Silent-pass observed quality guard
Function
- Toggles
silent_pass_observed_quality_guardfor observed CLIGEN build paths.
Purpose
- When enabled, WEPPcloud keeps the generated
.clieven if CLIGEN logs quality-guard convergence markers.
Recommended use cases
- Advanced troubleshooting when you need a run to continue and can review warning context in the climate report summary and status panel.
Important behavior details
- Default is enabled (
true), so climate build continues when CLIGEN quality-guard markers are detected. - When this bypass occurs, WEPPcloud shows a warning in the climate report summary and publishes the same warning to the climate status stream.
- Disable this option if you want quality-guard failures to stop the build with a user-facing convergence message.
Post-CLIGEN precipitation scaling modes
No scaling (0)
Function/Purpose
- No precipitation scaling is applied after build.
Recommended use case
- Baseline control runs.
Scalar scaling (1)
Function/Purpose
- Applies one scalar multiplier (
precip_scale_factor) to precipitation.
Recommended use case
- Fast sensitivity analysis (for example +/- 10%).
Monthly scaling (2)
Function/Purpose
- Applies 12 month-specific multipliers.
Recommended use case
- Seasonal bias correction.
Reference scaling (3)
Function/Purpose
- Derives monthly scaling from a selected reference dataset (
prism,daymet, orgridmet) over your observed year window.
Recommended use case
- Aligning generated precipitation totals with an external gridded climate reference.
Important constraints
- For PRISM reference scaling, start year must satisfy PRISM availability constraints in validation.
Spatial scaling from map (4)
Function/Purpose
- Uses a scale-factor raster map path to apply spatially varying precipitation scaling.
Recommended use case
- Advanced workflows with vetted external scale-factor maps.
Important constraints
- Map path must exist.
- Out-of-range scale factors are skipped.
- In current UI this option is present but disabled/read-only for most users.
Practical tuning guidance
- Change one advanced setting at a time.
- Rebuild climate and rerun WEPP.
- Compare calibration metrics after each change.
- Record the setting change and rationale for reproducibility.