I’m trying to generate Adaptive thermal comfort maps in a house with a living room adjacent to a conservatory.
A thermal curtain is specified indoors, against the interior window.
It is used only during winter nights and we’ve been using a dynamic window construction with the equivalent Uvalue for usual thermal simulations.
However, the Adaptive Thermal Comfort Map returns the following error:
Which seems to point to the fact that Dynamic interior apertures are blocking points for both the Longwave MRT and Shortwave MRT.
Did you ever come across this issue?
Do you see a way around it?
Could we run the view factor separately using HB radiance with the HB Dynamic states and reconstruct an annual view factor file ?
This is a discussion that should also involve @mikkel since he’s the master of the Radiance methods that are raising the NotImplementedError. We’ve had discussions about when and how to support dynamic interior apertures in our Radiance simulations but, as far as I know, you are the first who has tried to actually run such a case. Or you’re at least the first to report a case about it to us on this forum.
Supporting dynamic interior apertures is a lot of work for us and it may be hard to justify our time on this if you are the only person asking us for it now.
This might be even more work depending on the error that EnergyPlus is throwing there. I can’t remember but it’s possible that E+ does not support dynamic interior apertures either. I feel like, when I modeled things like double-skin facades in the past, I always had to assign the dynamic shades to the exterior apertures. What error do you get when you simulate your model with the HB Model to OSM component?
If we’re able to get a successful E+ simulation with your blinds there, then I can probably help you find some workaround to make an adaptive comfort map, albeit without all of the fancy reflections of shortwave solar that Radiance can do.
We can remove the limitation in the writer in honeybee-radiance to avoid the NotImplementedError. I know that this will not work with any recipe depending on two-phase-daylight-coefficient, which is only annual-daylight-enhanced in the LBT plug-in, but we could add a handler for the model input to check for interior aperture groups. It should not affect any of the other HB Radiance recipes.
I am not sure if it will work for the HB Energy recipes, @chris.
Thanks for the explanation, @mikkel . So is seems like things could work out on the Radiance side if I were to switch over the comfort recipes to use the two-phase-daylight-coefficient recipe as a dependency or some edited variation of it.
However, I did a test and confirmed that EnergyPlus does not support dynamic interior apertures. You’ll get a fatal error if you do so:
Program Version,EnergyPlus, Version 23.2.0-7636e6b3e9, YMD=2024.05.31 12:51,
************* Beginning Zone Sizing Calculations
** Warning ** Weather file location will be used rather than entered (IDF) Location object.
** ~~~ ** ..Location object=SITE 1
** ~~~ ** ..Weather File Location=New York J F Kennedy IntL Ar NY USA TMY3 WMO#=744860
** ~~~ ** ..due to location differences, Latitude difference=[40.65] degrees, Longitude difference=[73.80] degrees.
** ~~~ ** ..Time Zone difference=[5.0] hour(s), Elevation difference=[500.00] percent, [5.00] meters.
** Warning ** ProcessScheduleInput: Schedule:Constant="ALWAYS ON DISCRETE", Blank Schedule Type Limits Name input -- will not be validated.
** Warning ** ProcessScheduleInput: Schedule:Constant="ALWAYS OFF DISCRETE", Blank Schedule Type Limits Name input -- will not be validated.
** Warning ** ProcessScheduleInput: Schedule:Constant="ALWAYS ON CONTINUOUS", Blank Schedule Type Limits Name input -- will not be validated.
** Warning ** GetHTSurfaceData: Surfaces with interface to Ground found but no "Ground Temperatures" were input.
** ~~~ ** Found first in surface=ROOM_1_2AEDCA1E..FACE4
** ~~~ ** Defaults, constant throughout the year of (18.0) will be used.
** Severe ** InitialAssociateWindowShadingControlFenestration: "APERTURE_5FE8E21A", invalid because it is not an exterior window.
** ~~~ ** .. It appears on WindowShadingControl object: "SHADING CONTROL 1
** Severe ** InitialAssociateWindowShadingControlFenestration: "AJD_APERTURE_5FE8E21A", invalid because it is not an exterior window.
** ~~~ ** .. It appears on WindowShadingControl object: "SHADING CONTROL 2
** Fatal ** GetSurfaceData: Errors discovered, program terminates.
...Summary of Errors that led to program termination:
..... Reference severe error count=2
..... Last severe error=InitialAssociateWindowShadingControlFenestration: "AJD_APERTURE_5FE8E21A", invalid because it is not an exterior window.
************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
************* EnergyPlus Sizing Error Summary. During Sizing: 5 Warning; 2 Severe Errors.
************* EnergyPlus Terminated--Fatal Error Detected. 5 Warning; 2 Severe Errors; Elapsed Time=00hr 00min 0.07sec
!