Conversation
* Remove redundant set membership checks * More efficiently create horizon, prev_tmp, and next_tmp parameters * More efficiently create availabilities * More efficiently create transmission operational periods and timepoints * Skip over non-active derates in availability_derate_cap_rule * Cache reserve variable, derate params, and reserve BA param names for efficiency * Fix some inefficient creation of opr tmp and horizon sets. stor_opr_bt_hrz_set_init in the stor module was the biggest offender. * Efficiency improvements in tuning modules * Efficiency improvements in project operations modules, including resolving op type rules and fuel group fuel burn rule resolution. * Check whether to skip reserve provision ramp limits before creating component and only resolve capacity rule once * A few additional efficiency improvements in stor.py
* Refactor updating results dataframes to use a new update_results_df() helper function This adds a results dataframe's columns to the consolidated frame at the source column's dtype and fills values in instead of first assigning None. This replaces the df[c] = None + .update() that created object-dtype columns with much higher memory requirements. * Use params for availability when possible If every required availability type produces a constant derate (no variables in the derate, e.g. all-exogenous), make the derate components Params rather than Expressions, as params are much more memory-efficient and we usually don't have endogenous availability. * Don't store zero-valued reserve to energy adjustments * Add option to skip duals * Use SetOf for AVL_EXOG_OPR_TMPS and VAR_OM_COST_ALL_PRJS_OPR_TMPS When we only have exogenous availability time, don't create AVL_EXOG_OPR_TMPS set, but use SetOf(m.PRJ_OPRT_TMPS). When we only have simple var costs, don't create VAR_OM_COST_ALL_PRJS_OPR_TMPS, but use SetOf(m.VAR_OM_COST_SIMPLE_PRJ_OPR_TMPS) * Remove defaults for var cost params * Tx_Availability_Derate as param, not expression, unless endogenous * Test common functions
Also record last updated by GP utilities in DB.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.