Cbc  2.9.9
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Groups Pages
Todo List
Class CbcCutGenerator

Add a pointer to function member which will allow a client to install their own decision algorithm to decide whether or not to call the CGL generateCuts method. Create a default decision method that looks at the builtin criteria.

It strikes me as not good that generateCuts contains code specific to individual CGL algorithms. Another set of pointer to function members, so that the client can specify the cut generation method as well as pre- and post-generation methods? Taken a bit further, should this class contain a bunch of pointer to function members, one for each of the places where the cut generator might be referenced? Initialization, root node, search tree node, discovery of solution, and termination all come to mind. Initialization and termination would also be useful for instrumenting cbc.

Class CbcFullNodeInfo
While there's no explicit statement, the code often makes the implicit assumption that an CbcFullNodeInfo structure will appear only at the root node of the search tree. Things will break if this assumption is violated.
Member CbcModel::addCuts1 (CbcNode *node, CoinWarmStartBasis *&lastws)
addCuts1() is called in contexts where it's known in advance that all that's desired is to determine a list of cuts and do the bookkeeping (adjust the reference counts). The work of installing bounds and building a basis goes to waste.
Member CbcModel::integerPresolve (bool weak=false)
It remains to work out the cleanest way of getting a solution to the original problem at the end. So this is very preliminary.
Member CbcNodeInfo::numberBranchesLeft_
There seems to be redundancy between this field and CbcBranchingObject::numberBranchesLeft_. It'd be good to sort out if both are necessary.
Class CbcStrongInfo
The notion that all branches are binary (two arms) is wired into the implementation of CbcObject, CbcBranchingObject, and CbcBranchDecision. Changing this will require a moderate amount of recoding.
Member CoinDrand48 (bool isSeed=false, unsigned int seed=1)
Anyone want to volunteer an upgrade for 64-bit architectures?
File CoinMessageHandler.hpp
This needs to be worked over for correct operation with ISO character codes.
Member CoinMpsIO::dealWithFileName (const char *filename, const char *extension, CoinFileInput *&input)
Add automatic append of .bz2 suffix when compiled with libbz.
Member CoinMpsIO::readMps ()
Provide an interface that will allow a client to associate a CoinMpsCardReader object with a CoinMpsIO object by setting the cardReader_ field.
Member CoinPackedMatrix::appendMinorFast (const int number, const CoinBigIndex *starts, const int *index, const double *element)
This method really belongs in the group of protected methods with #appendMinor; there are no safeties here even with COIN_DEBUG. Apparently this method was needed in ClpPackedMatrix and giving it proper visibility was too much trouble. Should be moved.
Class CoinWarmStartBasis

Modify this class so that the number of status entries per byte and bytes per status vector allocation unit are not hardcoded. At the least, collect this into a couple of macros.

Consider separate fields for allocated capacity and actual basis size. We could avoid some reallocation, at the price of retaining more space than we need. Perhaps more important, we could do much better sanity checks.

Class CoinWarmStartBasisDiff

This is a pretty generic structure, and vector diff is a pretty generic activity. We should be able to convert this to a template.

Using unsigned int as the data type for the diff vectors might help to contain the damage when this code is inevitably compiled for 64 bit architectures. But the notion of int as 4 bytes is hardwired into CoinWarmStartBasis, so changes are definitely required.

Class drop_empty_cols_action
Confirm correct behaviour with solution in presolve.
Class drop_empty_rows_action
Confirm behaviour when a solution is present in presolve.
Class dropped_zero
Why isn't this a nested class in drop_zero_coefficients_action? That would match the structure of other presolve classes.
Group Functions to work with variable status
Why are we futzing around with three bit status? A holdover from the packed arrays of CoinWarmStartBasis? Big swaths of the presolve code manipulates colstat_ and rowstat_ as unsigned char arrays using simple assignment to set values.
Group Methods for problem input and output
Allow for file pointers and positioning
Member OsiSolverInterface::getIntegerTolerance () const
This method should be replaced; it's architecturally wrong. This should be an honest dblParam with a keyword. Underlying solvers that do not support integer variables should return false for set and get on this parameter. Underlying solvers that support integrality should add this to the parameters they support, using whatever tolerance is appropriate. -lh, 091021-