Final solution of a nonlinear non-convex problem solved with Knitro (via Xpress) looks worse than the initial solution

Hi Tristan,

I followed your instructions but I have a new question related to the setinitval procedure.

I load my initial solution by setting the value of each variable (not every but most of them).

Then I set the parameter xslp_log = 5 in order to see the initial point passed to Knitro but the point is not what I expected.

Beside some variables that completely changed their initial values, and I know this could be because of some preprocessing made by xpress, there are some other variables whose values look shifted from one position.

Here is an example.

What I load into the model and read in the .mps file of the problem is:

flowOn((77_278_83_313)_ENERGY,0)= 111.446

flowOn((77_278_83_313)_ENERGY,1)= 111.346

flowOn((77_278_83_313)_ENERGY,2)= 111.246

flowOn((77_278_83_313)_ENERGY,3)= 112.939

What I read in the mosel log file is:

flowOn((77_278_83_313)_ENERGY,0)= 111.346

flowOn((77_278_83_313)_ENERGY,1)= 111.246

flowOn((77_278_83_313)_ENERGY,2)= 112.939

flowOn((77_278_83_313)_ENERGY,3)= 0

I also tried to solve the .mps directly from the console and again I found this mismatch, please see the attached picture.

Do you know what is happening? Could this be an error in the logging procedure? Or the initial point is actually shifted?

This would explain why Knitro cannot complete the search and reaches the time limit even when the initial point I provide is a feasible one.

Thank you!

Br, Caterina