Ah, I see. Sorry that I was looking at the wrong Radiance command and didn’t realize that you were trying to customize the annual simulations and not the PIT ones. We don’t have anything exposed on the SDK layer that would allow you directly access the gendaymtx -c option from Grasshopper but everything’s open source and so you only have to edit a line of code in a .py file of the core libraries if you want to access this.
Here is where the recipe is setting the options for gendaymtx command:
If you’re on Windows, you should be able to find this file in this location:
Is there a way to do it though so that the RGB values in the tuple are input from Grasshopper?
And an additional question: Are the opt.d (sun only) and opt.s (no sun) accessible from Grasshopper?
I would like to create a workflow where I run a sun-only simulation with the -c option for color of the sun and a no-sun simulation with the -c option for the color of the sky and as a result I get the 3-channel irradiance values (for sun and for sky) instead of illuminance. Can I create my own recipe for this to make it a bit more flexible without having to change the sky.py file every time? I see that the HB Annual Daylight component uses this:
recipe = Recipe(‘annual-daylight’)
Can I make my own ‘colored-annual-daylight’ recipe to do what I described?
The short answer is “not easily but there’s always a way to hack it.” The fastest/hackiest way to do it is just write a GHPython component that edits that .py file, adding in the lines of Python that you want when the component runs. Then, when you go to run the recipe, the new/edited Python code would be used.
If you’re interested in implementing a longer-term solution that’s not nearly as hacky, I think we’d accept a code contribution that exposes the Radiance parameters for sky generation. The first step would be to expose these radiance-paramters on that command in the .py file that you’re editing. If you end up sending a Pull Request to the Honeybee-Radiance repo that does this, I would be happy to review and merge if it’s all good. Then, we can work towards exposing these parameters on the recipe.