Lower and upper bounds for boolean variables redefined

This is related to how min up/down times constraints override the default binary limits (basically forcing a unit on or off). I think when a binary variable gets created in Pyomo those limits get set. This warning should be able to be squelched. Or instead of creating a variable for this case, we could use a fixed parameter.

On Thu, Jul 25, 2013 at 7:52 AM, rschell notifications@github.com wrote:

When running minpower in debug mode I get the following warning messages:

pyomo.lp:79690: warning: lower bound of variable status_Bridger1(t648)' redefined pyomo.lp:79690: warning: upper bound of variablestatus_Bridger1(t648)' redefined pyomo.lp:79691: warning: lower bound of variable status_Bridger1(t649)' redefined pyomo.lp:79691: warning: upper bound of variablestatus_Bridger1(t649)' redefined

It complaining about statements in the LP file like: 0 <= status_Bridger1(t648) <= 1

any way to stop these statements from being created?

Ron

— Reply to this email directly or view it on GitHubhttps://github.com/adamgreenhall/minpower/issues/14 .

adamgreenhall / minpower

Lower and upper bounds for boolean variables redefined #14