Hi, I am using lbt-grasshopper v1.8.42 and used it without problem running the recipe leed-daylight-option-one version 0.0.30. After updating lbt-grasshopper to the latest version v1.8.47, I am getting error from the HB Automatic Aperture Group component which says ‘Runtime error (AssertionException): Illegal character “/” found in’. To check what the error is, I opened the component in the ScriptEditor. Attached is the screenshot of the Test output showing the details of the error.
Since I cannot resolve this error, I reverted back to the old lbt-grasshopper version.
I wanted to try the latest leed-daylight-option-one version 0.1.1 on the same model but when I tried to run the pollinate component, I got the error message shown in the attached file. I also cannot resolve this error.
I will appreciate your advice on how to resolve the above errors. I would like to use the latest versions of lbt-grasshopper and the leed-daylight-option-one recipe. Thank you.
Did you run the LB Versioner component within the last five hours? If not, please try to update the core libraries with LB Versioner and let me know if it solves the issue.
If it’s still not working please try to upload the attachment again. It seems like it did not go through.
I updated the core libraries with the LB Versioner and it solved the HB Automatic Aperture Group component error. I tried to run the model using the leed-daylight-option-one version 0.1.1 recipe but still got an error after completing the run I think, because previously with the old LB version, it just ran for a very short time when the error showed up. Attached is the error message from the run.
@dannyllim, for the recursion error when trying to delete a file is it possible that your hard drive is almost full and out of storage when you run the simulation?
Also, the error in the screenshot is different, and complains about illegal characters in the path. Can you share your model and the Grasshopper script with us?
The screenshot is for the HB Automatic Aperture Group component error and it has been fixed after I updated the LB core libraries. The html file is from the pollination component error message after I ran version 0.1.1 of the leed-daylight-option-one recipe. There is no error when I ran version 0.0.30 of the recipe.
Regarding the hard drive, my C drive where grasshopper is installed has 98 GB free space and drive D where I keep my simulation files has 69.9 GB free space.
Attached is the Grasshopper script having this issue. It is a practice file I am using to try things from tutorials.
Thanks! I was able to recreate the issue and found the error in the log file. If you update your core libraries with the LB Versioner component in ~1 hour you should be able to run version 0.1.1 of the recipe locally.
The issue was that the grid in the room “Corridor” returned an empty array of illuminance (because there is no illuminance). While waiting for the fix to get through to lbt-grasshopper you can remove “Corridor” from the grids if you want to test the new recipe.
