Originally posted by: Zele
Hi, EdKlotz.
Thanks for your time. First, sorry because I confused the file file.sav. I realized because you said that always solved within a seconds, and, usually, it is solved in minutes (about half an hour), with interactive optimizer. I have attached it again in previous post.
About you say: no, I don't set any non default CPLEX parameters. Even so, I have just written in my program line "status=CPXsetdefaults(env);" just before read the .sav file to ensure nothing escapes to me, and CPLEX is out of memory again.
About basic variables, both, interactive optimizer and with my program, CPLEX says the same warning (of course, file is the same), but the behavior is different.
I will try to explain why I use it, because these details could be useful: I have these basis variables because I am programming a heuristic that solves a big problem by parts. I mean, in the c++ program, I have a big problem, and, iteratively,by steps, I fix some variables to 0,1 each time. So, in the file.sav I attach, I am in a intermediate step: some variables are fixed to 0 or 1, and some variables (2000) are declared binary. So, the program solves this new problem, I save the solution, and later, in the next step for the algorithm, I save some 0-1 values for some variables, fix them, and declared another ones binary, etc, etc.
First, I thought that, how I am always with the same problem, fixing some variables,declaring binaries another ones, solving it again, etc, this affected the way CPLEX works. So, I tried, in each step, free the problem (using CPXfreeprob()), reading the .sav file I built in the previous step, and solve it, but I find the same "out of memory" problem. The only thing I have not done is try to free, not only the problem, but all CPLEx memory used in each step, but I suppose that there must be a less drastic way to fix it.
Thanks in advance.
#CPLEXOptimizers#DecisionOptimization