I am not sure what to do now, but it all started with a versioner update. I have also tried reverting to 1.4.1 without any luck. I have noticed people with similar problems in the last month, but they seem to have found a resolution with URBANOpt. I have not.
Thank you for the update @Junoh. It is probably not LBT then. I hope I did not do more harm than good trying to fix the interface. Unfortunately, I am supposed to have a production model done by Monday. Oops.
I found a reason. It was because sometimes it is not working with .bundles folder.
Nothing is in the .bundle/install/ruby/2.7.0 folder.
The problem is… I don’t know how to solve this…
What path is this .bundle folder on for you? @mostapha are other people reporting this problem after 1.4.3? I cannot find any version of LBT to run URBANOpt right now.
There is a problem with some bundler conflicts for URBANOpt CLI. I went back and deleted an old version of OSS, downgraded to 1.4.0 LBT, uninstalled URBANOpt CLI and reinstalled. Now the CLI is running again.
Sorry for the late reply and thank you bother for getting to the bottom of this. It seems something has changed in URBANopt’s dependencies that triggers this issue. I will try to recreate it when get home and see if I can push a fix.
I’m not able to recreate the issue on my end and I have no issues running things with the latest URBANopt and Ladybug Tools (via the versioner).
If you are re-using an URBANopt project folder, which had previously been created with an old version of Ladybug Tools and URBANopt, the .bunlde folder in the project folder could be out of date and manually deleting it should get things to run smoothly again.
Dear Chris… I think DF model component has a bug… Becuase If I want to run Urban OPT component I have to change the name of DF model component… Maybe you can check the deatil of that compenet.