BUG FIXES: Solver Refactor for IDAES Integration

[mrmundt]

Fixes

Summary/Motivation:

Working with @andrewlee94 on adding initial support for v2 solvers in IDAES, we discovered some bugs. This PR addresses those bugs.

Changes proposed in this PR:

• Remove usage of model.nobjectives (etc.) due to them not existing on ScalarBlocks
• Allow forward compatibility of solver_options and writer_config in LegacySolverWrapper
• Yell loudly if users try to use both options and solver_options in the same command
• Add some docs (not a lot, but some) about how both types of option passing are supported

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

1. I agree my contributions are submitted under the BSD license.
2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

[blnicho]

This seems weird to include here. Is this pointing to an edge case that was missed in #110 that should be fixed directly in the Block or _BlockData class?

[mrmundt]

Absolutely, yes, it should be. It was something that Andrew ran into while trying to get this working for IDAES, since they inherit from ScalarBlock

[jsiirola]

This is really wacky - and probably not something that should be added to Block (in the new world order, there should never be a reason to attach a symbolmap to the model)

[mrmundt]

How would you like to handle this? It causes issues in IDAES if it's not present because they use ScalarBlock.

[mrmundt]

I added a commit to @andrewlee94's branch on IDAES to resolve this: andrewlee94/idaes-pse@532d23b

[Robbybp]

• Allow forward compatibility of solver_options and writer_config in LegacySolverWrapper
• Yell loudly if users try to use both options and solver_options in the same command
• Add some docs (not a lot, but some) about how both types of option passing are supported

Thanks! I too was confused by this when trying the new interface a few days ago.

[jsiirola]

This is really wacky - and probably not something that should be added to Block (in the new world order, there should never be a reason to attach a symbolmap to the model)