Is there documentation or papers that go into some depth of how these constraints work, how you would represent them symbolically, etc.?
Thanks,
Corey.
\
To unsubscribe from this group and stop receiving emails from it, send an email to gamsworld+unsubscribe@googlegroups.com.
To post to this group, send email to gamsworld@googlegroups.com.
Visit this group at http://groups.google.com/group/gamsworld.
For more options, visit https://groups.google.com/d/optout.
Corey,
There is some mention of this in the PATH documentation: you can find it at
http://www.gams.com/help/topic/gams.doc/solvers/path/index.html
and search for “=N=” from there. You won’t find too much specifically about =N= rows there because the type of constraint used doesn’t change the model that you are solving. If you have a formulation that GAMS accepts (say, some =N= rows matched with lower-bounded variables), then changing the sense of the constraint will either have no effect (say, changing to =G= rows) or will make the model unacceptable/inconsistent (say, switching to =L= rows).
IMHO, it’s more useful to start from the MCP definition as given in the PATH docs mentioned above. Once that is well understood it’s easier to understand what GAMS is doing to cast the constraints of your model into the functions of the MCP.
HTH,
-Steve
On Mon, Nov 30, 2015 at 9:08 PM, Corey wrote:
Is there documentation or papers that go into some depth of how these constraints work, how you would represent them symbolically, etc.?
Thanks,
Corey.
\
Steven Dirkse, Ph.D.
GAMS Development Corp., Washington DC
Voice: (202)342-0180 Fax: (202)342-0181
sdirkse@gams.com
http://www.gams.com