You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
February 2025 Release:
**Finish PR #1358 **
The PriceTaker class must still be merged into the main codebase. This class and associated workflow can be useful for projects related to DISPATCHES-type work. For example, modeling flexible desalination in WaterTAP is of interest, and we could make use of the Pricetaker class.
Here is a to-do list based on @andrewlee94 's suggested changes and @radhakrishnatg 's suggestions for enhancement.
Add test file for design_and_operation_model.py @radhakrishnatg
Strengthen unit tests across the board (e.g., test add_startup_shutdown and other methods); consider simpler dummy cases for unit testing all the methods in isolation @adam-a-a
Enable addition of startup, shutdown, ramping, etc. constraints when representative days (as opposed to full-year price signal) are used
Enable addition of cash flow/cost expressions when representative days are used
The text was updated successfully, but these errors were encountered:
February 2025 Release:
**Finish PR #1358 **
The PriceTaker class must still be merged into the main codebase. This class and associated workflow can be useful for projects related to DISPATCHES-type work. For example, modeling flexible desalination in WaterTAP is of interest, and we could make use of the Pricetaker class.
Here is a to-do list based on @andrewlee94 's suggested changes and @radhakrishnatg 's suggestions for enhancement.
Add technical reference for Pricetaker class @MarcusHolly Price taker model for DISPATCHES, Rehashed #1358
Add test file for design_and_operation_model.py @radhakrishnatg
Strengthen unit tests across the board (e.g., test add_startup_shutdown and other methods); consider simpler dummy cases for unit testing all the methods in isolation @adam-a-a
Enable addition of startup, shutdown, ramping, etc. constraints when representative days (as opposed to full-year price signal) are used
Enable addition of cash flow/cost expressions when representative days are used
The text was updated successfully, but these errors were encountered: