Optimization Path Plotter

[PaulTalbot-INL]

---

Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

Closes #1506

What are the significant changes in functionality due to this change request?

Adds a OutStreams.Plot subType for plotting optimization results.

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• 1. Review all computer code.
• 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
• 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
• 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in XML block, the node <internalParallel> to True.
• 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• 8. If an analytic test is changed/added is the the analytic documentation updated/added?
• 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

[alfoa]

This is not in the manual. @Jimmy-INL

[PaulTalbot-INL]

Can this be removed from the test change, or should we put off the GA demonstration for another PR? @Jimmy-INL

[Jimmy-INL]

on it

[Jimmy-INL]

can you please convert it back to <objective>-1</objective>? If the test is long reduce the <limit>

[Jimmy-INL]

This shouldn't affect the plotter at all. Sorry, I thought it is hanging because other tests are failing not because of this. My bad, I think I am losing my memory

[PaulTalbot-INL]

I fixed the generation script and added the updated docs. It looks like quite a few options were hiding in the InputSpecs that hadn't made it into the docs.

This is one more big sign that we should try to automate all the docs, I suppose.

[PaulTalbot-INL]

@Jimmy-INL this is passing tests still; I merged in devel to resolve some conflicts. Where are we at with this PR?

[moosebuild]

Job Test OpenSUSE Leap 15 on 7851b4f : invalidated by @Jimmy-INL

concerns have been resolved

[Jimmy-INL]

The openSuSE Leap 15 machine is currently down. I am merging this after discussion with @PaulTalbot-INL