Forum Discussion
FICO
6 years agoCommunity Manager
xpress.InterfaceError: Incorrect control name error
I upgraded FICO Xpress Optimization from version 8.8.0 to 8.9.3. The following used to work in the python3 interface of version 8.8.0: import xpress as xp
xp.controls.outputlog = 0 # disable all s...
FICO
6 years agoCommunity Manager
Hi Joris,
My guess is that Xpress is picking up an OEM license. In this case, the Python interface cannot read the control names until Xpress has been initialized by calling the xp.license() function. I assume you are using Linux, in which case, please check that the XPRESS environment variable is pointing to the license file that you want to use. Note that Xpress might also look for a license file at /opt/xpressmp/bin/xpauth.xpr, so I suggest you check this too.
Regards,
Chris
Related Content
Related Content
Rare occurrences of exception xpress.InterfaceError: Incorrect control name
We have an optimization job that ~2% of the time fails with xpress.InterfaceError: Incorrect control name when trying to set xp.controls.miprelstop. This is the first line of code in our solver funct...3 years agoPlace FICO® Xpress Optimization ForumFICO® Xpress Optimization Forum3 unread comments3 unread0Views0likes3CommentsHow to resolve traceback: "xpress.InterfaceError: Incorrect control name; check name and license type"?
We are trying to access xpress in Python via Pyomo. We have no issues installing xpress and solving a simple model with the xpress interface. However, when we attempt to access xpress via pyomo we re...2 years agoPlace FICO® Xpress Optimization ForumFICO® Xpress Optimization Forum1 unread comment1 unread1View0likes1CommentOptimizer controls in Python
Could you please point to a reference of the solver controls that can be set from Python API (package xpress)? It seems that the names are not the same as in Mosel (e.g., XPRS_MIPRELSTOP and XPRS_VE...4 years agoPlace FICO® Xpress Optimization ForumFICO® Xpress Optimization Forum5 unread comments5 unread0Views0likes5Comments