I am using AMPL for teaching via the windows bundle with the IDE (not the community edition).
In the latest bundle I downloaded, I see that I can call Baron both as baron and as baronmp. Yet, the later does not seem to recognize the bundle’s licence.
Using “option solver baron;” I get “BARON 24.5.8 (2024.05.08)” running and everything goes well.
On the other hand, using “option solver baronmp;” I get “BaronMP 24.10.10” and the message
“Sorry, a demo license is limited to 10 variables and 10 constraints and objectives for non-linear problems.”
Is there a way to fix this and run the more recent baronMP?
Thanks in advance.
Best regards,
Julio.
Thank you for reporting this issue. We have just adjusted the bundle generation to also add the license to baronmp. You need to rebuild your course bundle or, alternatively, use the course license via the Option 1 shown on the bundle download page using the license UUID and the regular installers.
I have tried to regenerate and download the bundles but I get the following error “Failed to generate bundle for Windows 64-bit. Please try again and report the issue if the problem persists”.
I tried a couple of times with no success (and I had regenerated them with no problem earlier today).
Now I have been able to regenerate the bundle with no problems and, moreover, I do not get the licensing error for baronmp anymore.
Yet, I have run into a new error (maybe unrelated). After solving some toy examples with baronmp as a solver, I gave to it a much more challenging one (the one I am interested to have Baron working on). If I set the solver to baron everything is fine but, if I set the solver to baronmp, I get:
##########################
BARON version 24.10.10. Built: WIN-64 Thu Oct 10 23:02:44 EDT 2024
Running on machine JULKIN
BARON is a product of The Optimization Firm.
For information on BARON, see About BARON | The Optimization Firm
baronin.exe: syntax error on line 113603
BARON: Syntax error
BaronMP 24.10.10: not solved, could not call Baron process
##########################
Not sure if this issue will have such an easy fix as the previous one…
Thanks anyway for our time.
Best,
Julio.