Hey @AbrahamYezioro ,
Glad that you hear that you are getting a hang of the new workflows. To answer your questions:
-
The TimeIntervalOperation component is working fine on my end. For example, here’s total daily solar radiation:
… and here is average:
If you can post a specific example of what’s not working on your end, I can invetigate. -
All of the legacy functionality associated with splitting building masses to simulate-able Rooms has been moved from Honeybee to Dragonfly. If you look through Dragonfly “Create” tab, you will see components that are intended to make entire simulate-able buildings from Rhino solids or footprints. And every dragonfly building is translate-able to a Honeybee Model as you can see in the samples on the dragonfly-grasshopper repo. You can see that we even have more robust core/perimeter zoning implemented in Dragonfly, which Saeran recently put together:
The goal with moving all of this functionality to dragonfly was to make it much easier to build large, urban-scale energy and radiance models by giving people a “level of abstraction” above Honeybee. Within dragonfly, the finest level of detail that you work with is Room floor plates, representing extruded solids. And, if you need to go down to more detail below this, you just translate the Dragonfly model to (a) Honeybee model(s).
The start of this presentation that I gave yesterday has some more animated GIFs showing the dragonfly workflows.