-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Bug]: Error from parameter checking: raise ParameterNotProvidedError(relevant_parameter) #666
Comments
@chengzhuzhang Please refer to https://github.com/E3SM-Project/zppy/blob/main/zppy/defaults/default.ini. These are actually slightly different parameters: # End year (i.e., the last year to use) for the reference data
# Required for "tropical_subseasonal" runs
ref_end_yr = string(default="")
# Final year (i.e., the last available year) for the reference data
# Required for "qbo" runs
# Required for run_type="model_vs_model" "enso_diags"/"streamflow"/"tc_analysis"/"tropical_subseasonal" runs
ref_final_yr = string(default="") |
Yes, I checked this file. This seems to be a newly introduced change, or it is not tested before? It is confusing to have two parameters defined for one set, notice that ref_end_yr and ref_final_yr are both required here. |
@chengzhuzhang Yes, I believe in #628 I was just trying to pass through parameters to Actually looking at https://github.com/E3SM-Project/zppy/blob/main/zppy/templates/e3sm_diags.bash, and I see you started fixing this in #668, but is there a corresponding change in the |
I understand that |
Oh, I understand now. |
@chengzhuzhang See my review at #668 (review) |
What happened?
When testing v3.0.0 rc2, I ran into error below. Not sure how this problem is introduced, but the checker is expecting
ref_end_year
fortropical_subseasonal
set but what always provided as a parameter isref_final_year
.What machine were you running on?
Ruby at LC.
Environment
zppy v3.0.0 rc2 within e3sm-unified v1.11.0rc3
What command did you run?
Copy your cfg file
What jobs are failing?
What stack trace are you encountering?
The text was updated successfully, but these errors were encountered: