Honeybee_standards lacks a "modifiers" folder

Hi all, I desperately need to run a big study over the weekend so appreciate any help solving this issue!

I reinstalled LBT using the GH Pollination installer. Then downgraded to V1.4.0 using the versioner. Restarted Rhino/GH and this happens:

Any ideas?

Hi @MaxMarschall, if you create a subfolder called modifiers inside the folder in the error message the issue should go away.

Also, why did you need to downgrade?

Hey @MaxMarschall ,

You could create all of the sub-folders manually like Mostapha said, though, if you are going that far back in time, it might just be better to use the old Food4Rhino installer. Or it may be easier to upgrade your Grasshopepr script to the newer version rather than downgrade your installed version. Are you aware of the LB Sync Grasshopper File component? That can save you a lot of time with updating your older Grasshopper definitions.

@mostapha following the error messages I created a “modifiers” folder, then a “modifiersets” folder, but now it says this:

Why I’m downgrading:

  • I need to rerun some studies for a project that we did a while ago where we used 1.4.0 so I wanted to make sure everything is identical
  • For this project, I need to do some more extensive number crunching on annual daylighting results (we are comparing many different standards). For this I have a script that works with raw .ill files, but I believe after 1.4.0 you switched to numpy files and you can no longer output raw .ill - is that correct?

@chris & @mostapha I uninstalled Pollination and reinstalled 1.4.0 through food4rhino and everything works again perfectly - thanks!

(@chris re reasons for downgrading see above - if I’m missing something please let me know!)

Thanks for clarifying, @MaxMarschall .

For Radiance simulations, you should be able to get results that are “identical” to your original simulations whether you use the latest version of the plugin or LBT 1.4. Granted, Radiance uses stochastic methods to generate the rays so “identical” is always going to be a relative term. I should also note that, in the most recent version of Annual Daylight, we exposed the ability to turn on or off the enhanced_ part of the calculation, which models the direct sun with high accuracy. Previously, all simulations had to use the more time-consuming enhanced method.

For your point about the switch to numpy files, you are right that we made the change because the numpy files are much faster to parse into annual metrics and they take up a lot less space. If you don’t want to change your script to use the numpy matrices instead of text .ill files, I think @mikkel might have a command you can run on the numpy results to convert them to text files. Am I correct about this, @mikkel ?

1 Like

That is correct. @MaxMarschall, see more here if you want to convert the new results folder to the old format.