algorithmic modeling for Rhino
A question about setting up the proper controls for conducting a night flush sequence during the summer. I recognize that the Honeybee_Set EP Airflow component allows me to set the maxOutdoorTemp and maxIndoorTemp for natural ventilation but it seems using these controls does not produce a logical sequence to determine when to flush.
For example, just using the maxOutdoorTemp, if I set it to 33C (studied comfort threshold for Indian populations), the flush sequence will not start until outdoor temp drops below 33C even if outdoor temp is significantly lower than indoor. I am seeing this occur in the late-night and early hours of the day when indoor temps rise above 33C from daily heat gains. The indoor temp may be around 37C and outdoor temp can be 34C, yet no cooling will occur since outdoor has not dropped below 33C yet. The zone remains in a closed state until the outdoor temp drops below 33C which may occur at 4am, which leads to minimal flush hours.
What I desire is the ability to write a sequence/conditional statement that will operate the ventilation based on the indoor-outdoor temperature difference. If outdoor temperature is ever lower than indoor in the cooling season, night flush should ensue.
Is there currently a way to create this type of logic diagram?
Replies are closed for this discussion.
To illuminate this issue more, I plotted the outdoor and indoor temp in excel and annotated the graph below. The time frame is nine days in the summer.
The brown line represents the indoor temperature when the 33C maxOutdoorTemp is used. It is obvious that the nightflush does not start in the evening until outdoor temperature drops below 33C, even when indoor is above 37C. However, in the morning, it is not clear to me why the zone does not always reach a closed state when outdoor temperature exceeds 33C. Instead, it looks like it occurs around 35C.
I see that these conditions are not persistent so perhaps some clues to why these few instances stand out would be helpful.
This is a very good question. I realized that there is an E+ input that allows you to make the exact control strategy that you have specified here, which I forgot to expose on the EPAirflow component. If you need the result right now, you can get it by editing this input in the IDF file that Honeybee writes:
... And then use the rerunIDF component to run the simulation with your new IDF.
I'll try to expose this DeltaTemperature input shortly and post back here once it's added to the github.
Thanks for the reply, Chris. I've been able to get back into the model and try out some IDF editing. However, it seems that there are some errors in re-running the IDF within grasshopper. See below for the error message I get from the HB component as well as my ZoneVentilation:DesignFlowRate parameters I used to set the nightflush using the deltaT approach.
It looks like the file address to your weather file is not correct. Everything with the deltaT variable seems good. I think I've finally gotten a bit of time to add this in and I'll try to do it now. It it proves to be an issue that's solveable in a couple of hours, you should have it soon.
DeltaTemperature is now a part of Honeybee:
See attached for a file that shuts off natural ventilation any time the outdoor temperature gets above the indoor temperature.
Awsome Chris! This can really help with this component, especially in climates like the one I am in where diurnal variations are not really a thing.