Opened 12 months ago

Closed 7 months ago

#94 closed user support (migrated)

Python interface results does not match C-code

Reported by: ashkan Owned by: ferreau
Priority: VERY HIGH Milestone:
Component: python interface Version: 3.2.1
Keywords: Cc:

Description

Hi
It seems that the running example1.py, the results does not match the example1 from C code. In fact when running example1.py the results seem to be incorrect.

Here the output of example1.py.

xOpt = [ 0.000000e+00, 0.000000e+00 ]; objVal = 1.000000e+20

################### qpOASES -- QP OPTIONS ##################

printLevel = PL_NONE

enableRamping = BT_TRUE
enableFarBounds = BT_TRUE
enableFlippingBounds = BT_TRUE
enableRegularisation = BT_FALSE
enableFullLITests = BT_FALSE
enableNZCTests = BT_TRUE
enableDriftCorrection = 1
enableCholeskyRefactorisation = 0
enableEqualities = BT_FALSE
enableInertiaCorrection = BT_TRUE
rcondSMin = 1.000000e-14

terminationTolerance = 1.110500e-09
boundTolerance = 2.221000e-10
boundRelaxation = 1.000000e+04
epsNum = -2.221000e-13
epsDen = 2.221000e-13
maxPrimalJump = 1.000000e+08
maxDualJump = 1.000000e+08

initialRamping = 5.000000e-01
finalRamping = 1.000000e+00
initialFarBounds = 1.000000e+06
growFarBounds = 1.000000e+03
initialStatusBounds = ST_LOWER
epsFlipping = 2.221000e-13
numRegularisationSteps = 0
epsRegularisation = 2.221000e-13
numRefinementSteps = 1
epsIterRef = 2.221000e-14
epsLITests = 2.221000e-11
epsNZCTests = 6.663000e-13

Change History (1)

comment:1 Changed 7 months ago by stefan

  • Resolution set to migrated
  • Status changed from new to closed

This ticket has been migrated to GitHub and will be resolved there: https://github.com/coin-or/qpOASES/issues/94

Note: See TracTickets for help on using tickets.