Urban opt simulation not working, does anyone know how to solve the problem?
As the message suggests, it seems you need your IT to greenlight the URBANopt executables or turn off something in your antivirus software that is blocking the URBANopt executable from running.
Thank you but it didn t work, I am still getting the same message…
Hello, I also encountered the following error when running DF URBANopt:
The same error also occurs with the template file.
Yeah I tried so much already…
Could you find a way to solve it?
Hello, my friend~ I haven’t got it working yet. I’m using the OSM+OSW modules for batch simulation of group buildings, as Urbanopt and its other features are still unavailable.
Hi, I also tried with OSM+OSW but the results are “empty”, I don t know what I am doing wrong… did you manage to do your simulations?
Hi all,
I´m also getting the same message,I uninstalled 0.11.1 version and install the 0.14.0 but it doesn´t run either.
Could anuybody help us with this issue?
Thanks in advance.
Patricia
The full error message reads
Blockquote
Failed to create folder:
The value cannot be an empty string. (Parameter ‘path’)
Runtime error (IOException): Access to the path ‘C:\Program Files\Rhino 8\System.check_uo_version.bat’ is denied.Traceback:
line 110, in write_to_file_by_name, “C:\Program Files\ladybug_tools\python\Lib\site-packages\ladybug\futil.py”
line 127, in write_to_file, “C:\Program Files\ladybug_tools\python\Lib\site-packages\ladybug\futil.py”
line 326, in _urbanopt_version_from_cli, “C:\Program Files\ladybug_tools\python\Lib\site-packages\dragonfly_energy\config.py”
line 141, in urbanopt_version, “C:\Program Files\ladybug_tools\python\Lib\site-packages\dragonfly_energy\config.py”
line 252, in check_urbanopt_version, “C:\Program Files\ladybug_tools\python\Lib\site-packages\dragonfly_energy\config.py”
line 271, in prepare_urbanopt_folder, “C:\Program Files\ladybug_tools\python\Lib\site-packages\dragonfly_energy\run.py”
line 149, in script
I was wondering if the issue is the . before the check_uo_version.bat filename, but then I also wondered why on earth it would be checking in a Rhino system file directory, so I am left wondering whether the call assert os.path.isfile(_epw_file), in the script is looking in the wrong place? Is looking up the Operating System path the right lace to look?
No solution as yet, except to note that the most recent downloadable version of urbanopt is version 1, which is almost twice the size of version 0.14
Hello. I had the same issue and have a fluke fix on my machine but perhaps it will work for others too. The cli 0.14 folder was missing setup-env.bat no matter how it was installed. What fixed it was:
Installed cli 0.13 > copied setup-env.bat file over to cli 0.14 install folder> ran the bat file inside 0.14 folder > uninstalled 0.13
Hope this helps
Hi all,
Has anyone managed to fix the error? I also get the same error and don’t know how to fix it.
Runtime error (ValueErrorException): An URBANopt installation was found at C:\URBANopt-cli-0.14.0
but the URBANopt executable is not accessible.
‘uo’ is not recognized as an internal or external command,
operable program or batch file.
Traceback:
line 266, in check_urbanopt_version, “C:\Users\w22021416\ladybug_tools\python\Lib\site-packages\dragonfly_energy\config.py”
line 271, in prepare_urbanopt_folder, “C:\Users\w22021416\ladybug_tools\python\Lib\site-packages\dragonfly_energy\run.py”
line 149, in script
Thanks, @jeune_qui .
Michael Don and I think that we got to the bottom of the issue, which is that URBANopt switched to using Powershell files (.ps1) instead of Batch files (.bat) to set up the user environment starting in URBANopt 0.14.0.
For many people, this has been fine but native support for running Powershell files was only introduced in Windows 10. So anyone with an older operating system will not be able to run URBANopt until they manually install Powershell. This could be part of the problem but I would venture a guess that this is probably not the issue most people are experiencing here since I’m sure most people are using Windows 10 or 11.
Instead, I suspect that many peoples’ Windows installations do not “trust” Powershell files as much as they “trust” Batch files. After all, Powershell is a newer format and Batch files are a format the Microsoft developed whereas Powershell is more cross-platform. So I am sure that Microsoft and IT groups have an incentive to just block these types of files purely because they are newer and scarier. I am pretty sure that there is some setting that has to be flipped for you to be able to run the powershell file and make “the urbanopt executable accessible” as the message tells you. I don’t know exactly what that switch is at the moment but I’ll try to investigate. I’ll also see if NREL can put back the older Batch file that they were using since the Powershell file has clearly caused some challenges.
In the meantime, here is a workaround that is similar to what @jeune_qui . You can copy the following Batch file into the directory C:\URBANopt-cli-1.0.1 and then run it:
setup-env.bat (898 Bytes)
After that, everything for URBANopt runs with Batch files so you should be good to go.
FYI, I got a response from the NREL team that they will work on making an URBANopt installer that uses batch files again “after April 25th.”
So, hopefully, it won’t be too much longer that you have to use the workaround above.
