Title Factory class for operator counting constraints
Priority feature Status chatting
Superseder Nosy List florian, malte
Assigned To florian Keywords
Optional summary

Created on 2015-11-09.17:32:43 by florian, last changed by malte.

msg4760 (view) Author: malte Date: 2015-11-10.13:11:03
Taking into account that my perspective is somewhat uninformed (I don't know the
code very well), "ConstraintFactory" and "Constraint" sound nicest.
msg4737 (view) Author: florian Date: 2015-11-09.17:32:43
Operator counting constraints currently get their task in the method
initialize_constraints, which should just create constraints in the LP. We want
to change this by introducing factory classes for constraint generators and
passing them as options to the operator counting heuristic instead of passing
constraint generators. The heuristic then creates operator counting constraints
for its task in its initialization/constructor.

Since "ConstraintGeneratorFactory" sounds like "ConstraintFactoryFactory", I
suggest to also rename the generated object to "OperatorCountingConstraint" or
just "Constraint" (its in the namespace OperatorCounting anyway). The factory
could then be named "ConstraintFactory" or "ConstraintGenerator". What names do
you prefer?
Date User Action Args
2015-11-10 13:11:03maltesetstatus: unread -> chatting
messages: + msg4760
2015-11-09 17:32:43floriancreate