Opt mode

[PaulTalbot-INL]

---

Pull Request Description

What issue does this change request address?

Closes #11

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

Implements the option to use "opt" mode instead of "sweep" in <Case><mode>.

The test is as fast as I can realistically get it without losing its purpose, but it still takes 140 seconds to run in parallel, so I marked the test as heavy for now. A few things could be done to improve this:

• Don't reset persistence on rejected potential opt points
• Speed up the startup of RAVEN (inner runs are taking 8 seconds, 4 of which are after startup)
• Don't force rerunning of previous opt points on rejection; deterministic codes don't need this, and it at least doubles the run time.

We can re-address making the test non-heavy when we can get it down around 30 seconds or less run time.

---

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.
• 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 tes.
• 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, the the analytic documentation must be updated/added.
• 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.