thank you for this great tool.
I have a question concerning view dependant legends.
I see that legends are placed with a reference point in 2d-space.
And I found the quite interesting module orienttocam which can be used for text.
Sadly, both cannot be connected in a proper way when operating in 3dspace trying to place a legend for an animated sequence.
Is there a workaround to accomplish something similar?
Thanks. The ideal solution is to develop a component that generates the legend as a graphic (and not a geometry). I tried it a number of times and it is not that hard to create the legend however it is really hard to dispose! You can easily end up having the legend up there with no way to remove it. This is something that I can give it another try later but I hope someone else does it before me!
The current workaround is to find coordinate of a Point2D on the screen and then use that as the legend basepoint. It will work as far as you animate in a single viewport. Attached is a quick and dirty example. It should work as far as you are creating gentle camera moves!
Hope it helps,
reMaplegendBasePt.gh (7.48 KB)
thank you for the example.
As far as I could understand the procedure, the legend parameters are handed through to the re-color mesh component. Unfortunately, the format of origin and z-axis is not understood by the component. What is the proper editor for ghuserobjects, so I can take a dive? Although I must say I am a complete newbie to python!
Every Ladybug/Honeybee components is a single GHPython component, just double click on the component and you will see the code.
I made some modifications and put an example together that shows how you can use the boundingbox and morph to do what you are looking for.
reMaplegendBasePt_II.gh (56.8 KB)
your solution works like a charm. Should have thought about this myself. Shame on me. Now, I only have to check for alternative fonts.
One last thing, I was wondering why the totalradiation output of the radiation analysis component and the radiationresult output of the rt radiation analysis component tend to differ in its values after massaddition of the first and comparing it with the latter. Did I miss out on something, conceptually?
Thank you for all the time you put in this valuable work.
You can change the font in line 83. Current font is ‘Veranda’.
Radiation values are in kWh/m2 (for annual analysis) and Wh/m2 for hourly studies. In both case you need to multiply the numbers with the area of mesh faces if you want to find the totalRadiation. This is exactly what I do inside the component. Here is an old example:
yes, I understand what you mean. But I was thinking about the comparison between the results of the real time module and the radiation module. See the two panels in the picture below. Did I misinterpret the added values?
Hi Ante, Here also you need to multiply the results with the area of Mesh faces if you want to compare them to total radiation. Output from realTime component is also in kWh/m2 for each test point so it should be multiplied by the area to be compared to totalRadiation (kWh). -Mostapha