Skip to content

Implement multi-site local sensitivity analysis workflow #1

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.

Sign up for GitHub

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

Open
divine7022 wants to merge 28 commits into
base: main
Choose a base branch
from
Open

Implement multi-site local sensitivity analysis workflow #1

Show file tree
Hide file tree
Changes from 18 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
fc9f282
update config
Nov 17, 2025
1b4fae2
update template.xml
Nov 17, 2025
cb141cf
add R scripts for local sensitivity analysis
Nov 17, 2025
8fc2243
add local SA analysis script
Nov 17, 2025
68e4be6
add processed data outputs for SA
Nov 17, 2025
a38efee
add design_points_198.csv for multisite SA
Nov 17, 2025
d82f2d6
add sa_design_points.csv for SA generation
Nov 17, 2025
000c14b
add workflow scripts for local SA
Nov 17, 2025
ae7e038
Revert "add processed data outputs for SA"
Nov 18, 2025
a5c942d
Revert "add sa_design_points.csv for SA generation"
Nov 18, 2025
36370ec
made sigma configurable
Nov 18, 2025
4fe8777
update sigma_level
Nov 18, 2025
6e5489b
corrected dplyr namespace
Nov 18, 2025
b38a22a
made quantile block as first entry of sensitivity.analysis
Nov 18, 2025
ff3eafd
save regression_results as csv
Nov 18, 2025
e3ecab6
updated analyze_environmental_gradient() to fits regressions of both …
Nov 18, 2025
481d540
update local sensitivity analysis report
Nov 18, 2025
17db11a
ensure data directory exists
Nov 18, 2025
d77d112
add the data/design_points.csv path
divine7022 Nov 26, 2025
7753a3d
add process_sa_file helper function and refactor doc
divine7022 Nov 26, 2025
76a2b6a
refactored to completely drop the clustering logic and it now acts pu…
divine7022 Nov 26, 2025
10d2acf
fix indent
divine7022 Nov 26, 2025
4aba622
remove XML dependency and replaced raw XML file re-parsing with direc…
divine7022 Nov 26, 2025
9b701ae
correct design_points path
divine7022 Dec 8, 2025
8692fdc
fix sa variables extraction logic
divine7022 Dec 10, 2025
2c0b932
address review comments
divine7022 Feb 27, 2026
57865a5
cleanup unused
divine7022 Feb 27, 2026
47621d3
update comment
divine7022 Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions 000-config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,5 +11,14 @@ default:
pecan_xml_template: "data_raw/template.xml"
sites:
design_points_file: "data_raw/sa_design_points.csv"
sensitivity:

@dlebauer dlebauer Nov 21, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The goal with this file was to handle settings that aren't in the pecan xml. Is there a reason that these are included here rather than the template.xml?

Minimizing config options here, and providing sensible defaults in the template.xml could make it more clear to end users.

@divine7022 divine7022 Feb 27, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good point, template.xml already holds most pecan specific defaults. The items in 000-config.yml fall into two categories,
1 ) project level paths (ccmmf_dir, design_points, pecan_outdir) -- these are system specific and shouldn't live in template.xml since can change per machine

2 ) run configs (n_ensemble, n_met, start_date, end_date) -- moved these here from being hardcoded in
002_build_xml.R so users can configure them in one place. They feed into the XML building step

I have minimized config, let me know if you still have any specifics

sigma_levels: [-3, -2, -1, 1, 2, 3] # Standard
# Or use [-2, -1, 1, 2] for faster runs
# ensemble:
# size: 20
# n_met: 10
# run:
# start_date: "2016-01-01"
# end_date: "2023-12-31"
projection:
ca_albers_crs: 3310
Loading