I will change FLOPC++, not to include obviously empty constraint blocks in the generated problem. However, in any case I think you should still include a small preprocessing step for yor solver to remove empty rows (and possibly more)
For example I do not plan to check for empty rows coming from constraints like
somedata <= someotherdata
or similar
Issue created by migration from Trac.
Original creator: thh
Original creation time: 2005-11-30 14:22:31
Assignee: somebody
Version:
I will change FLOPC++, not to include obviously empty constraint blocks in the generated problem. However, in any case I think you should still include a small preprocessing step for yor solver to remove empty rows (and possibly more) For example I do not plan to check for empty rows coming from constraints like somedata <= someotherdata or similar