Closed willu47 closed 1 day ago
Thank you for reporting this problem.
The relevant parts of the code have been adapted: an .env file is now only required when using a standard local license (its path has to be specified as an environment variable). For the Community Edition cloud-based license, the user simply has to activate it before running his first optimization. (https://github.com/IPESE/REHO/commit/82b76a4f09038fc0a27d8d9ba4af41ad9c189edb)
The "AMPL license" paragraph of "Getting started" section has been redesigned to clarify these instructions: https://reho.readthedocs.io/en/main/sections/5_Getting_started.html#ampl-license
Great, thanks for this.
Upon testing, while the recursion error has gone, the fundamental issue of not recognising that the .env
file is in my current working folder (so relative to where I call the test script from) and not in a location relative to where the REHO package is kept, is the main issue here. See note in #13 again.
I suspect you still had the error because you were using version 1.1.4 installed with pip and not the updated code on the main branch? (such confusion might be coming from the fact that I prefer to not deploy a new version of the package in PyPI, when discussions are still on going about potential changes, as I had indicated in this post on the JOSS review discussion)
As mentioned in my message above, an .env file is no longer required with the cloud-based Community Edition license.
And for someone with a standard local license, the .env file specifying the AMPL_PATH can now be located either at the root directory or at the current working directory (https://github.com/IPESE/REHO/commit/b0ba53c1118e49b7a52d66655314b7280491da82)
NB: For your convenience, I deployed a REHO 1.1.5 in PyPI. I hope it'll be fine with these errors 🤞
I installed the latest version from Github using pip install git+https://github.com/IPESE/REHO.git@main#egg=REHO
. It is a good idea to deploy pre-release versions to PyPI, which is automatic with a tag such as v1.5.2-alpha
(see this for examples of valid tags).
The latest version closes this issue.
Is there an existing issue for this?
What happened?
I've install v1.1.4 using pip, installed postgres via brew, and installed AMPL manually via the website (OSX version) and activated the cloud license. I have a
.env
file in my folder, although the .env file is empty - as I do not have a license file. AMPL provide a cloud license.Either the script does not recognise my local folder, and the presence of the
.env
file, or I have the wrong value in my .env file. Either way, the execution should stop on being unable to run AMPL (if that is the issue) and not produce this very long error trace.Version
1.0.2 (Stable)
Relevant log output
Anything else?
No response