Switching from Honeybee Plus - 3 phase to LBT to use Pollination

[vanageso]

Something with using the LB versioner is making the file corrupt. That was the reason I was not able to upload the file anywhere (including the forum or email)

The error when I run LB versioner says “User object source file is corrupt”. And after I open Grasshopper the following error pops up (it doesn’t if I run it as an administrator)

I tried using both the new fixed LB versioner and one-click installer to install everything again (Ladybug update problem - #3 by chris - ladybug-tools - Ladybug Tools | Forum).

So a few posts ago when I was able to run the WIP method, I had to run Rhino as an administrator.

[mostapha]

Hi @vanageso, this is a permission issue. Running Rhino as an admin should solve the problem. Also, see the discussion here:

Issues with updating Pollination/LBT

Hi team, My company’s IT restricts admin rights (I’m one of the lucky few who has them) and I work with them to deploy Pollination Grasshopper Plugin to the approved “Software Centre”. The one issue I face with this is when updating LBT via the Versioner component, opening Rhino as admin and then running the versioner is successful, but then when I close and reopen Rhino normally (not admin) I get this error. LBT Plugin: System.UnauthorizedAccessException: Access to the path 'C:\Program File…

In case you can wait for a few more days, we should create a new release of the Rhino plugin in a few days which should include all the updates that you are trying to install.

[vanageso]

Still facing the same error after using the LB versioner and running as admin. I have added the file for reference.

sensitivity_5.0_pollination_PO_sim_v3_forum_MK_2.gh (840.1 KB)

[mikkel]

Hi @vanageso,

If doing as shown in the image below does not work, please try the following:

1. Download dynamic.py (8.0 KB).
2. Go to the following folder C:\Program Files\ladybug_tools\python\Lib\site-packages\honeybee_radiance_postprocess.
3. Replace the file called dynamic.py with the one you downloaded in step 1.

[vanageso]

Thank you for your response. The error went away.

However, the illuminance values are always zero when using the aperture groups.

I used the same modifiers with static apertures, and it works for both BSDF-based and normal trans-material modifiers.

But with dynamic aperture groups, the illuminance values are zero even with default modifiers/non-BSDF based modifiers/BSDF-based modifiers

sensitivity_5.0_pollination_PO_sim_v3_forum_MK_2.gh (853.4 KB)

[mikkel]

Hi @vanageso,

Can you try to create the grid from the Room in the HB Add Surface component?

[vanageso]

HB sensor Grid from rooms works when used this way for workplace sensors.

I am also trying to use the vertical sensor to calculate glare. I tried using the HB sensor grid from apertures to values for vertical sensors, and the illuminance values are zero. (results are not generated for apertured groups shown in screenshot below)

Also, there is no way to set a particular height for the vertical sensor as they use apertures [I want to set it to 1.2 meters at eye level]). I tried using the HB Sensor Grid component, not using the rooms HBobj as input but just points and directions (illuminance values a zero using that method too!)

I think this is the last step I need to figure out before my model is complete for running. As always, I really appreciate your help.

[vanageso]

I forgot to upload the model

sensitivity_5.0_pollination_PO_sim_v3_forum_MK_2.gh (830.0 KB)

[mikkel]

Hi @vanageso,

The results are not generated for aperture groups because the vertical sensor grid does not have a room identifier. The two “from Rooms” components for sensor grids will take care of this automatically, but you can edit the room identifier of the grid with one line of code. I have attached the custom Python script in the Grasshopper file.

If you need the sensors at 1.2 meters then you should use HB Sensor Grid.

grid_room_identifier.gh (837.6 KB)