Skip to content
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

Open
wants to merge 79 commits into
base: develop
Choose a base branch
from
Open

add FlexibleHVAC to MPC module #84

wants to merge 79 commits into from

Conversation

NLaws
Copy link
Member

@NLaws NLaws commented Jun 27, 2022

this branch includes changes in rcmodels and so should be merged after #30

rathod-b and others added 30 commits March 14, 2022 17:33
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
@NLaws NLaws requested a review from rathod-b June 27, 2022 23:07
See the [ElectricLoad](@ref) docs for `city` options.


!!! note
Copy link
Collaborator

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
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants