Radiance definitions using 'alias' and 'inherit'

For many years now Radiance's text based system has permitted 'sets' of materials to be created which have a similar base definition but might be modified slightly differently - perhaps due to their placement in the building.

I have created a radiance material file in the Ladybug directory with a bunch of material definitions. I note that any the have alias in them cause the Honeybee "Fly" component to have conniptions...

I am guessing we need to think through how these base definitions might be subsequently modified by another GH module?

Is there any guidance somewhere on this?

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Sarith Subramaniam on May 3, 2017 at 7:43pm

Hi Michael,

This issue is related to parsing Radiance materials from strings. Inside the Honeybee source-code, parsing of Radiance materials from strings is done by the functions called createRadMaterialFromString and analyseRadMaterials. The parsing logic within these functions is only compatible with the basic Radiance primitive format documented in page 4 of the Radiance File Formats.

modifier type identifier

n S1 S2 S3 ..Sn

m R1 R2 R3 ..Rm

Aliases, which are mentioned in Page 5 of the same document, are not implemented in Honeybee. In the Grasshopper scheme of things, it is easier to implement a simple script that swaps out the name of the original (stored) material with the name of material in the scene.

RSS