Pollination model export as IESVE gem behaving differently to the DUMP gem grasshopper component

Thank, @milog ,

We are definitely interested in understanding your current TM59 workflow and please put together a post about it. At a minimum, it will help us understand whether there are any changes we can make on our end to improve your quality of life with this workflow.

I also forgot to tell you that I was randomly mulling over the problem of how to use simplified E+ ventilation objects for TM59 compliance per our original discussion here and I think I might have found a better way of doing it. In our original discussion, I had given up on using the EMS to control the simple ventilation objects because (at the time) the only place I had found where I could place an EMS actuator was on the total ventilation flow rate, which would have ignored the effects of temperate, wind, etc. that we want to capture for natural ventilation. However, I forgot that these simple ventilation objects also support an “Opening area fractional schedule” and any E+ schedule can have an EMS actuator placed on it to set the exact value of the schedule. This means that I can write an EMS program to control the window opening, which effectively accounts for all of the TM59 logic (including the pesky chance in criteria that happens between day and night).

Long story short, if you start a new discussion and lay out your full workflow, I might be able to respond with something that lets you use the Rhino plugin and Ladybug Tools for everything.

2 Likes