Hi everyone, I am running a parametric study with the Fly component, simulating 365 different window configurations. Each configuration corresponds to one specific day of the year.
Run 1 (Jan 1st) → Window Construction A
Run 2 (Jan 2nd) → Window Construction B
… and so on.
I have all 365 simulation results (hourly operative temperature). Now I need to filter the data so that for Result 1, I only see the hours of Jan 1st; for Result 2, only Jan 2nd, etc.
Ultimately, I want to calculate the number of hours where Top>25°C for each specific day and its corresponding construction. What is the best way to “slice” this data tree diagonally?
@Jsnbl with due respect: Why are you simulating a day? Are you going to change windows every day or do you want a realistic performance mark for each different window?
If you are wanting to simulate dynamic window constructions there are components for that, or you could utilize E+ EMS.
I mean no negative waves, just trying to get a handle on what your trying to do m8, and help if I can.
best
-trevor
Thanks, @TrevorFedyna . I am currently writing my thesis on the effect of deciduous plants in front of windows as a shading system. So far, I only have values that represent the reduced solar heat gain coefficient. Since this varies daily throughout the year (due to leaf fall/plant growth), I have a different SHGC for each day. In order to draw conclusions, I would like to have the oper temperature of the daily varying SHGC. For example, if I have an SHGC of 0.6 on January 1, how many excess temperature hours are there on that day, and if I have an SHGC of 0.2 on June 10, how many excess temperature hours are there in the room on June 10? And then I need the amount of hours, when the room exceeds a given temperature. So my way was to construct 365 windows, and running fly but now i have 365 output with the whole year, but i only want one day for one cnstruction. Do you have any Idea how i can get only the hours of the day (1-365) where i want to use my construction. With the HB to doy its not working becaus I only have the day (day 60…). But prefered in one output diagramm, if that is possible
@Jsnbl if you use this component you can just add 365 constructions to it and the necessary schedule, then you could run 1 simulation and then use hb to doy since its a full 8760 simulation.
The report of the model to osm says the following:
Program Version,EnergyPlus, Version 25.1.0-1c11a3d85f, YMD=2026.03.15 22:13,
************* Beginning Zone Sizing Calculations
** Warning ** Weather file location will be used rather than entered (IDF) Location object.
** ~~~ ** …Location object=SITE 1
** ~~~ ** …Weather File Location=HAMBURG - DEU IWEC Data WMO#=101470
** ~~~ ** …due to location differences, Latitude difference=[53.63] degrees, Longitude difference=[10.00] degrees.
** ~~~ ** …Time Zone difference=[1.0] hour(s), Elevation difference=[1600.00] percent, [16.00] meters.
** Warning ** CheckUsedConstructions: There are 12 nominally unused constructions in input.
** ~~~ ** For explicit details on each unused construction, use Output:Diagnostics,DisplayExtraWarnings;
** Severe ** Errors found parsing EMS Runtime Language program or subroutine = STATECHANGEDYNAMICWINDOW
** ~~~ ** Line 403: Detected ELSEIF series that is longer than allowed; terminate earlier IF instruction. “ELSEIF (SENSORDYNAMICWINDOW < 202)”
** ~~~ ** Missing an ENDIF instruction needed to terminate an earlier IF instruction.
** Fatal ** Errors found in parsing EMS Runtime Language input. Preceding condition causes termination.
…Summary of Errors that led to program termination:
… Reference severe error count=1
… Last severe error=Errors found parsing EMS Runtime Language program or subroutine = STATECHANGEDYNAMICWINDOW
************* 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.
************* ===== Final Error Summary =====
************* The following error categories occurred. Consider correcting or noting.
************* Nominally Unused Constructions
************* …The nominally unused constructions warning is provided to alert you to potential conditions that can cause
************* …extra time during simulation. Each construction is calculated by the algorithm indicated in the HeatBalanceAlgorithm
************* …object. You may remove the constructions indicated (when you use the DisplayExtraWarnings option).
************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
************* EnergyPlus Sizing Error Summary. During Sizing: 2 Warning; 1 Severe Errors.
************* EnergyPlus Terminated–Fatal Error Detected. 2 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 0.12sec
Runtime error (PythonException): ** Fatal ** Errors found in parsing EMS Runtime Language input. Preceding condition causes termination.
And as i mentioned in my previous post. I tried the simulation without the dynamic window and made with the fly component 365 simulation, but only want to have one day for each construction.
