I am working with Ladybug Legacy components (“Honeybee_IES luminaire zone”, “Honeybee IES luminaire,” and “Honeybee_Run daylight simulation”) to create a lighting simulation in a scene with no windows (the only light source is electrical lighting from several luminaires). However, after running the simulation, it seems like only one of the luminaires is “active.” The other luminaires don’t seem to contribute to the light levels. Below is an image showing an example of the issue:
I have placed multiple luminaires on one plane, with their aiming points on a separate plane.
There is a test grid between the luminaires and their aiming points to display results.
I am not sure if it is the problem with IES file or rad simulation properties- but checked both without results. I will be gratefull for every hint and suggestion.
Here are the files I used in simulation: LBTF Question
The idea of an aiming point for a zone (as implemented in HB) is that all the luminaires within that the zone will aim to the same point. So, in your example it appears that the aiming point being picked up is just the first one on the list. If you specify individual zones for each aiming point then the results will be as you expect.
I tried with two:
Thank you Sarith for fast response. However I’m not sure if this is a definitive solution to the problem. I think so, because modifying the size of the lamp (or “luminous opening” represented as drawLuminairePoly in iesLuminaire component) in the IES file gives the effect I wanted (so five active luminaires) despite leaving only one (not five) iesLuminaire Zone component in the GH file.
My modified IES file is here: LBTF Question (“Hypothetical rad source- point3”)
I will be gratefull If you find the time and let me know what you think about it.
Hi @stan , you are right, my initial assumption was not correct. Actually, it is possible to specify individual aimings, spins etc within a zone if their number matches the number of luminaires in the zone (implementation in code).
Can you check if the units in your Rhino file are in meters or not? If not can you scale everything to meters and check if your error persists?
