The maximum cap parameter triggers errors when implemented form the simulation server. This is an attempt to fix the problems
Changes proposed in this pull request:
OPTIMIZED_ADD_CAP replaced by "optimized_add_cap" in the assets keys returned to EPA after simulating
The if statement for adapting MAXIMUM_CAP for non-dispatchable production assets is now based on the value of DISPATCHABILITY and not on the existence of the key FILENAME in the asset_dict
"maximum_add_cap" to the keys returned to EPA after simulating got production assets
The following steps were realized, as well (if applies):
The maximum cap parameter triggers errors when implemented form the simulation server. This is an attempt to fix the problems
Changes proposed in this pull request:
OPTIMIZED_ADD_CAP
replaced by "optimized_add_cap" in the assets keys returned to EPA after simulatingMAXIMUM_CAP
for non-dispatchable production assets is now based on the value ofDISPATCHABILITY
and not on the existence of the keyFILENAME
in theasset_dict
The following steps were realized, as well (if applies):
black . --exclude docs/
)EXECUTE_TESTS_ON=master pytest
)Please mark above checkboxes as following:
:x: Check not applicable to this PR
For more information on how to contribute check the CONTRIBUTING.md.