Skip to content

Identify complete list of internal-only parameters #555

@dayantur

Description

@dayantur

This list identifies parameters currently marked as internal_only. It also shows where the parameters have been used (either in data_model scripts or sample_config.yml file).

This is a necessary first step toward separating user-facing and developer-facing YAML configuration files.
The goal is to provide users with a simplified YAML interface (excluding internal parameters) while still allowing full access for developers.

We now need to review the list and consider whether additional parameters should also be flagged as internal_only.

param_name file_location in_sample_config
cdd_accum state.py:621 No
cdd_daily state.py:677 No
days_since_rain state.py:713 No
days_since_rain_accum state.py:657 No
diagnose model.py:667 Yes
dqndt state.py:815 Yes
dqnsdt state.py:820 Yes
dt_since_start state.py:825 Yes
hdd_accum state.py:612 No
hdd_daily state.py:668 No
kdownzen model.py:657 No
lenday_id state.py:830 Yes
precip_accum state.py:648 No
precip_daily_total state.py:704 No
qn_av state.py:835 Yes
qn_s_av state.py:843 Yes
snowfallcum state.py:877 Yes
temp_5day_accum state.py:639 No
temp_5day_mean state.py:695 No
temp_accum state.py:630 No
temp_daily_mean state.py:686 No
tmax_id state.py:856 Yes
tmin_id state.py:864 Yes
tstep_prev state.py:872 Yes

Metadata

Metadata

Assignees

Labels

1-questionUser question/support/dev query2-infra:data-modelPydantic data models & validation2-infra:inputInput data handling and validation3-P0Critical priority4-needs-discussionAgenda item for weekly catch-up meeting4-needs-scienceRequires scientific input/decisionhelp-wantedExtra attention is needed

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions