Changeset 1706


Ignore:
Timestamp:
Mar 16, 2011 10:29:23 AM (9 years ago)
Author:
forrest
Message:

fix for number iterations in ClpSolve? and check if gone feasible for extreme cases

Location:
trunk/Clp/src
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • trunk/Clp/src/ClpSimplexDual.cpp

    r1665 r1706  
    44834483        objectiveValue(),sumPrimalInfeasibilities_,
    44844484        sumDualInfeasibilities_);*/
     4485     // mark as having gone optimal if looks like it
     4486     if (!numberPrimalInfeasibilities_&&
     4487         !numberDualInfeasibilities_)
     4488       progressFlag_ |= 8;
    44854489     if (handler_->detail(CLP_SIMPLEX_STATUS, messages_) < 100) {
    44864490          handler_->message(CLP_SIMPLEX_STATUS, messages_)
     
    51935197     if (problemStatus_ > 2)
    51945198          objectiveValue_ = approximateObjective;
     5199     if (problemStatus_ == 1 && (progressFlag_&8) != 0 &&
     5200         fabs(objectiveValue_) > 1.0e10 )
     5201       problemStatus_ = 10; // infeasible - but has looked feasible
    51955202}
    51965203/* While updateDualsInDual sees what effect is of flip
  • trunk/Clp/src/ClpSolve.cpp

    r1699 r1706  
    24792479               setLogLevel(CoinMin(0, saveLevel));
    24802480          pinfo->postsolve(true);
     2481          numberIterations_ = 0;
    24812482          delete pinfo;
    24822483          pinfo = NULL;
Note: See TracChangeset for help on using the changeset viewer.