algorithmic modeling for Rhino
The new electric lighting components for Honeybee are now available for download. You can either get them with the next release of Honeybee or update them in your existing installation by using the Honeybee_Update Honeybee component.
The video below (best viewed in full-screen mode) provides an idea of what these components are capable of being used for:
The video below shows how these components can be used in an existing Honeybee project (for additional links please open this video in youtube):
I have uploaded two examples as Hydra files that show how these components can be used for grid-point and image-based simulations:
Finally, a more esoteric application is demonstrated in this video:
These components are still in the beta-testing stage. Some of the limitations of the components are:
1. Only Type C photometry IES files are supported at present.
2. Rhino is likely to get sluggish if there are too many luminaires (i.e. light fixtures) present in a scene.
3. Due to the spectral limitations of the ray-tracing software (RADIANCE), simulations involving color mixing might not be physically realizable.
Additional details about photometric and spectral calculations are probably an overkill for this forum. However, I'd be glad to answer any related questions. Please report any bugs or request new features either on this forum or on Github.
Update 16th January 2017:
An example with some new components and bug fixes since the initial release announcement can be found here
Replies are closed for this discussion.
Superb, congrats and thanks for a superb components :)
Great work, very excited to experiment with this!
Well done, this is one of the much wanted aspects in HB/LB!
Thanks for the amazing work!
hey this is quite interesting, great work! as a lighting designer and heavy grasshopper user, this has been a long time coming. first, we got a few issues when testing the example files:
1) missing the embryoA image viewer - using firefly's image viewer in the mean time but can you share that?
2) we ran into a snag when loading ies file from a network location - it only worked on local disk. you should include that in your documentation? is it possible to make the links work over network?
3) support for all ies file types?
second, some initial thoughts:
1) change some of the nomenclature in the various components to not refer to 'Run daylight simulation' but just 'radiance lighting simulation.'
2) would be very helpful to have an output stating lumens (yes it's in luminaire details) but have the read-out show resulting lumens after LLF + calndelaMultiplier would be great.
3) possible incorporation of accelerad for GPU calc?
4) for the ies photometric web view, it would be nice to show the point grid of all the candela readings - this would show me if the ies file was created with a few real readings in an integrating sphere, or output from a digital software like photopia (generally useful when doing fixture research). it'd also be cool to be able to turn on the vector or point of peak candela.
5)in the 'Run Daylight Simulation' component - it'd be cleaner to separate out the inputs for geometry from the inputs for lights.
will submit more comments as i try it out on a few real projects...
First up, you can download Embryo Viz from here: http://www.grasshopper3d.com/xn/detail/2985220:Comment:1101387 ( I am not sure if there is a proper link for it. Perhaps Mostapha can clarify).
I had updated the components a few weeks ago but then got too lazy/busy to properly document that anywhere. Some of the additional features are:
1. It is now possible to substitute an IES file with a text string. For example one can paste the contents of an IES file into a text panel and connect that to the input for _iesFilePath. Alternatively, you can read a text file using the native Grasshopper "Read File" component, then embed (and internalize) that information inside the "Text" component.
So, either of the below two options will(should) qualify as an input for the _iesFilePath:
This makes it possible to embed IES data inside a GrassHopper file, thus doing away with the need for connecting to a file on a local drive.
2. I created a new component called Honeybee_IES Project which does the following:
1. It consolidates all the electric lighting RAD files for a simulation in one place. The single radFilePaths output from the component can be connected to the daylight simulation instead of connecting individual radFilePath outputs from every luminaire.
2. It creates a BOQ and luminaire schedule for all the luminaires used in the simulation. The schedule can either be viewed in a Grasshopper text panel or exported as excel.
The values for LLF, Candela Multiplier and Lamp Depreciation factor are printed out for each luminaire.
The effect of the multipliers on power consumption can be seen in the BOQ in the Total Power column:
Adding lumens to the output will be minor fix. I will update that within a few days.
I think the point-grid for the photometric and peak candela display are a great idea. I will add that functionality within a couple of weeks.
Are you implying the inclusion Type B photometry by "support for all ies file types" ? If so, that has been on my to-do list for a while. It might, however, be a while before I can get to it as it would require writing a convertor from Type C to Type B so that it can be visualized as a photometric mesh inside the Rhino viewport. I think the hackish way to get Type B photometry to work in Honeybee is to first convert the Type B photometry to Type C using something like the Photometric Toolbox.
Finally, the electric lighting components were initially written as a hack and they are still pretty much work-in-progress. I agree that calling the simulation a lighting simulation and adding separate inputs for electric lights would be a cleaner way of approaching these simulations. Mostapaha and I weren't sure of the traction that these new features might get. Based on the feedback received we will be simplifying and enhancing these components and the workflow to do electric lighting simulations.
(PS: Although I have heard a lot about Accelerad, due to the lack of compatible resources, I have never run a gpu-based simulation myself. I am not sure if Nathaniel requires additional flags or information to run Radiance simulations through Accelerad. If not, it should be possible to use files written through Honeybee to run Accelerad simulations. I will defer to Mostapha on the possibility of incorporating Accelerad in the Honeybee project).
great work! will check out the new IES_project component - i'm running some first real-project tests right now. so far i also found that if i path to an ies file, the file name can't have spaces (duh). but being able to link in how you suggest would obviously solve this issue.
you are correct about the Type 2 ies - we've run into this problem a few times, and yes, we typically transform in photometric toolbox. it's just a pain. if it's on your to-do list, then awesome.
A few new comments:
More generally, i'm not totally sure how we'll use this yet - in the office we've been transitioning from AGI to using iray in 3ds max (for some people quicker than others), which obviously puts out much higher quality renderings than radiance. but i think for more analytical studies this will, for me at least, be a total game-changer, and totally replace AGI. I also think it'll be a great replacement for photometric toolbox for photometric analysis. But if you're looking for further capabilities to add, AGI is a good place to start.
i'll keep a running log of issues/ideas as i find them and keep you posted.
thanks a ton
You can find a related discussion and a relevant Grasshopper file here: https://github.com/mostaphaRoudsari/Honeybee/pull/485
Hi Dan and Sarith,
If we can solve the licensing issues for distributing Accelerad libraries then it's pretty easy to do so. Currently the license is just for a single user. I briefly talked to Nathaniel about this at the Radiance workshop last year. If they change the licensing then we can think about adding it as an option. You may want to get in touch with Nathaniel and ask if there has been any changes about the licensing.
Hello everyone, I am having a look at the new IES luminaire components. I was wondering whether it would be possible to input a different multiplier for each value in the candela table. In this way one can control the luminaire web shape through other grasshopper parameters (I.E: on a given spatial coordinate lighting will be omnidirectional, on another it will be a directional spotlight).
Hi Sarith ,
I'm trying to learn how to use electrical lighting component of HB , all the steps are like your file but the illuminance is zero . So , If you don't mind, tell me what my file is missing !!! and I'd like to know a good website to download IES files from .
Thank you ,