Model Declaration Error "curtailment_cost_per_pwh" #1266
Replies: 2 comments 1 reply
-
I also tried to re-build the .tab files and I think there are some tables, while should be created according to db_schema.sql, is not present in the .db created, including the two curtailment cost tables, two ramp-up tables, and two ramp-down tables. After manually adding them to the generated .db, the error goes away. However, I am still getting errors due to mismatch between headers and column names, e.g., project/opchar/41_1_with_hydro_ramps.csv, 7_project_operational_chars_2zones2.csv, which are also related to curtailment and ramp up/ramp down names. |
Beta Was this translation helpful? Give feedback.
-
The curtailment_cost_per_pwh has been replaced by curtailment_cost_scenario_id on the develop branch, but not as part of an official release yet. Please ensure you have input CSVs consistent with the GridPath version you are using. For v2025.5.0, you can find the input CSVs under db/csvs_test_examples if you donwload the source code here https://github.com/blue-marble/gridpath/releases/tag/v2025.5.0. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
GridPath repeatedly returns "Model declaration 'curtailment_cost_per_pwh' not found in returned query columns" with all the examples I tried (test, 2 horizons, 2 periods). I have just completed the installation and is trying to run some examples. I am using a Conda virtual environment (Python 3.10, GridPath 2025.5.0).
Thanks for the help!
Beta Was this translation helpful? Give feedback.
All reactions