Qi Chen
Qi Chen
I asked Nick about it. I can verify that BARON doesn't take command line options, and it doesn't seem to be on the planning horizon: > BARON does not accept...
Do we still want to keep this issue around? I don't have any need to use Baron through Pyro at this point.
Yeah, I'm not a huge fan of having a bunch of unused temporary sets floating around, if only because it pollutes `display()`. I'm tempted to discourage reuse of implicit sets...
This is a known issue. I can't recall why the `*.nl` writer behaves in such a way, but if you want to get around the problem, try `TransformationFactory('contrib.deactivate_trivial_constraints').apply_to(model)`. Before solving.
The slight issue with only treating vars as active if they are in an active block is that it then becomes possible to write a constraint in an active block...
What are the competing views on ctype handling that currently exist?
I'll add that flattening also obscures the structure that the solvers I am involved with rely upon.
How large does `N` need to be?
@blnicho Yes, I still do rely on MC++. The resources were never put in to support Windows.