I want to optimize number and locations of luminaire (4 parameters) in MOGA. Locations can be achieved because there is _ptList in HB_Luminaire Zone component.
But how about the number of luminaires? Also, the points of each new added luminaires should be different and should be able to be connected to Octopus’ Genome input.
The luminaire component in Honeybee is fairly simplistic and not that suited for such optimization methods (unless you are prepared to wait for the simulations to keep popping on and off!). That being said, I would suggest turning off ambient calculations completely to speed up the process.
On the issue of optimizing number and locations, in Honeybee the luminaire is specified purely as a function of it’s location and is then used in calculations through reverse ray-tracing. So you’d have to devise a way in which you can switch between increasing/decreasing number of points and also moving those points around.
What might be more relevant in your case is to use the zonal cavity based Lumen method like the one employed in Lithonia Photometric Viewer.
There are no grasshopper implementations of this as far as I know. A few years ago I had written such a function in excel to evaluate upto 10,000 luminaire combinations at a time but I never got around to porting it into Honeybee.