-
Notifications
You must be signed in to change notification settings - Fork 55
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
Include more schedules in csv file #735
Comments
On setpoints: Option A
Option B
Option C
Option D
|
@shorowit Seems like we could pursue Option A above if we separated out pieces of the stochastic generator into their own methods. ResStockArguments could call these method(s) and gather relevant information for creating the setpoint schedule csv. The rest of the workflow downstream (in terms of measure calls), therefore, would be untouched. What do you think? |
Yes, that is a definite possibility. Though option B may be easier to implement and has some appeal if indeed there are some simple, high-level inputs to construct the 8760 setpoint schedules. @ejhw can you list the inputs that are being proposed? |
It is possible that we could refactor to make it simpler by using 0ºF offset to represent Has Offset = False:
cc @ekpresent |
I'm trying to minimally prove this approach out here: NREL/OpenStudio-HPXML#994. |
|
@joseph-robertson I think it was
I think the motivation was for one of @ekpresent 's projects. |
Related to #931 |
Examples:
For vacancy, are we zeroing out everything we want to (i.e., all schedules that are currently in the schedules csv file)?
For power outage, would this work?
We could move away from rulesets altogether, but there'd be a runtime penalty associated with that.
The text was updated successfully, but these errors were encountered: