Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
You may want to re-title your question and tags. Seems like you have handle on the rotation, question, which is a good one seems more about a metric for building without an HVAC system. One simplified approach would be to put in thermostats and look at unmet hours for different rotations, but a more robust approach could be weight both for the size of the the zones that are outside of the thermostat range, and by how much they are out of range . The standard report bins hourly temperatures by zone. You could use the code that gathers this as a starting point, and process in a reporting measure to come up with a metric, or a number of metrics. You won't see this metric in PAT results, will be in individual simulation reports, but if you were doing a large analysis you could use runner.registerValue and then make it an objective function.
| | 2 | No.2 Revision |
You may want to re-title your question and tags. Seems like you have handle on the rotation, question, which is a good one seems more about a metric for building without an HVAC system. One simplified approach would be to put in thermostats and look at unmet hours for different rotations, but a more robust approach could be weight both for the size of the the zones that are outside of the thermostat range, and by how much they are out of range . The standard report bins hourly temperatures by zone. You could use the code that gathers this as a starting point, and process in a reporting measure to come up with a metric, or a number of metrics. You won't see this metric in PAT results, will be in individual simulation reports, but if you were doing a large analysis you could use runner.registerValue and then make it an objective function.
I third approach would be to add ideal air loads to your model, that is more straight forward. Is there a reason you don't want to do that?
| | 3 | No.3 Revision |
You may want to re-title your question and tags. Seems like you have handle on the rotation, rotation. Your question, which is a good one one, seems more about a metric for building without an HVAC system. One simplified approach would be to put in thermostats and look at unmet hours for different rotations, but a more robust approach could be weight both for the size of the the zones that are outside of the thermostat range, and by how much they are out of range . The standard report bins hourly temperatures by zone. You could use the code that gathers this as a starting point, and process in a reporting measure to come up with a metric, or a number of metrics. You won't see this metric in PAT results, will be in individual simulation reports, but if you were doing a large analysis you could use runner.registerValue and then make it an objective function.
I third approach would be to add ideal air loads to your model, that is more straight forward. Is there a reason you don't want to do that?
