-
Notifications
You must be signed in to change notification settings - Fork 4
HIVE_RC_simulator
An energy simulation has three main components:
- Element: The parts which separate the zone from outside (eg. wall, window, roof). Internal elements are assumed to be adiabatic. Window element components calculate solar gains, which are one of the Simulation inputs.
- Zone: The zone being simulated. Takes any number of elements. Parameters for systems, setpoints, ventilation rates, etc. are defined by this component.
- Simulation: Takes all the important data streams and calculates internal temperature, heating and cooling in the zone.
The workflow is described in terms of the components developed for each stage.
-
Shading design for a specific window Directly visualise the effect of window shading on energy demand. Shading geometry can be rapidly optimized to minimize enregy consumption. There is a lot of potential: PV shading, dynamic shading, adding cost functions to shading elements, etc.
-
Overall window layout for a building Calculate the ideal window/wall ratio for a building for diferent window types, by minimizing the energy demand. Explore the tradeoff between higher thermal losses and solar gains.
-
Model adjacent unconditioned spaces When simulating single zone models, the temperatures in adjacent unconditioned spaces need to be assumed or calculated to calculate the conductivity reduction factors on elements separating them from conditioned spaces. Rapidly modelling the adjacent unconditioned spaces in Grasshopper could provide more accurate estimates of boundary conditions, possibly reducing modeling error. This hypothesis needs to be tested.
-
Design passive and active shading Based on the Energie & Klimasysteme coursework
- Replicate Python unit tests for the single-hour model
GHPython does not seem to support unittests, so a master/slave system was devised to run various scenarios. The values in the tests are exactly the same as in the python-based tests. Rather than fitting each test in a function, a set of dictionaries are created with test parameters and expected results. To add new tests, simply modify the dictionaries in the test master component.
- Sun position calculations relative to Ladybug value. This is currently accurate to one decimal place (Based on the sunpath version in ASF_control)
- Compare direct and diffuse components (separately) on different orientations between Ladybug, Hive and the radiation model in RC_BuildingSimulator.
-
Compare direct and diffuse components (separately) on different window tilts between Ladybug, Hive and the radiation model in RC_BuildingSimulator.
-
Test shading geometry
-
Test shading geometry with window tilt
-
Compare the Perez and simple diffuse irradiation models using AIC or F-tests.
-
polysurface inputs for shading device
-
multiple shading input
-
Automate all tests into a one-click processs
- Check if occupancy schedules and internal gains fall within a reasonable range
- Check sensitivity of all inputs
- Conduct speed tests to find bottlenecks
- Export inputs and results into Python and run a unit test asserting equal results.
- Run the RC model through Besttest
For all future developers, here's a handy set of tutorials to making Ladybug Components, by Mostapha Sadeghipour Roudsari. This approach is r Hive.
For maximum compatibility between the Python version and the RC tool, the classes for Building, Supply and emission systems each have their own component. When a new version of the building_physics.py, supply_system.py or emission_system.py is created, the code can be pasted in place of the old code in the corresponding Grasshopper user objects.