Hi all. I was trying to run an annual daylight simulation on local using the new revit pollination panel. But its failing within 5 seconds. The same run is successful running on cloud. I am sharing some screenshot.
Just an update. When I opened the same model in rhino pollination, and ran locally, it ran successfully. Only having issue with revit plugin running locally.
Hi @asisnath - I had a quick look and the dependencies are actually there. Can you send me the full log file? It is in the same folder as the err.log file and is named logs.log. I believe one of the dependencies is missing but I’m not sure which one.
2023-04-27 01:01:31 INFO: ‘gendaymtx’ is not recognized as an internal or external command
I just checked, and we don’t ship Radiance with the Revit plugin. That’s the source of the issue.
@mingbo, can we add Radiance to the Revit installer? We are already including OpenStudio.
@asisnath, the temporary fix is to globally install Radiance on your system so it can find the Radiance commands from the global environment until we fix this issue.
You do but it is not added to the PATH. You can add the radiance folder to the PATH and that should also solve the problem. To test if it has worked you should be able to open a new CMD and type rtrace -version and it should show you a version.
Hi Antonello! The bug here is that the panel assigns the path to the Rhino’s ladybug-tools folder to the command for the local run. Mingbo has added Radiance to the installer and we should be using the new Radiance.
We did some more debugging on our end and it should have actually worked on your end because you already have the Rhino plugin installed. Can you check the local simulation settings in the Revit Pollination panel?
Where doe the ladybug_tools path set to? Does that folder exist? And can you see Radiance under that folder?
Can you try to activate the debug mode, then right-click inside the panel and click on inspect, and finally go to the console tab and see what is being printed out when you try to go to the page? Here is how.
@antonellodinunzio - we should probably start adding a logger to the panel to make it easier to debug cases like this and the one that @aminigam92 is facing.
Thanks! I think the only remaining option is to do the famous “did you try to turn it on and off” trick and if that didn’t work we can set up a live session to debug it together next week.