-
Notifications
You must be signed in to change notification settings - Fork 14
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
add FlexibleHVAC to MPC module #84
base: develop
Are you sure you want to change the base?
Conversation
Add the ability to read JSON file to extract inputs for FlexHVAC struct when doe reference profile is provided
s.t. we can reuse the city in FlexibleHVAC; should probably do the same in the thermal loads from DoE CRBs
sometimes getting 0.99999, which fails in Bool(binFlexHVAC)
original FlexibleHVAC model had input_node = control_node; that is no longer the case for the DoE CRB RC models
- was using x[t+1] = x[t] + A x[t] + B u[t] but the DoE RC models were fit to the form x[t+1] = A x[t] + B u[t] - also removed the `input_vec` - model form also required changing the FlexHVAC test: convert continuous SS model to discrete instead of doing an Euler approximation of the continuous model
b/c it has MAE > 1 deg C
when not modeling FlexibleHVAC
some outputs were moved to "Outages" awhile back
not modeling FlexibleHVAC in problem yet
require users provide their RC model, don't use DoE RC models because it is wired for 8760 models
See the [ElectricLoad](@ref) docs for `city` options. | ||
|
||
|
||
!!! note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should these docs be updated to reflect _cooling or _heating suffixes to say either temperature_upper_bound_degC_cooling
or temperature_lower_bound_degC_heating
are required inputs?
get(d["FlexibleHVAC"], "temperature_upper_bound_degC_cooling", nothing), | ||
get(d["FlexibleHVAC"], "temperature_lower_bound_degC_cooling", nothing), | ||
) | ||
elseif flex_hvac_from_json # then have to convert vector of vectors to matrix |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can tell, flex_hvac_from_json
boolean has to be provided programmatically to Scenario function. Should we move this boolean as an input key under Settings or under FlexHVAC struct so future API users can interact with this functionality via JSON posts?
this branch includes changes in
rcmodels
and so should be merged after #30