Minor issues after introducing minMaxList are fixed.

[JunyungKim]

---

Pull Request Description

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

Issue 1. After 2nd iteration, objectives and constraint values are not matching with population. It was not due to wrong calculations of objectives and constraints. It was due to the misalignment of population and objectives as a dictionary.

Issue 2. When "max" is introduced, RAVEN first multiply a corresponding objective value with negative sign (i.e., -1). The new objective value (with minus sign) gives effect to constraint calculation. For instance, if a constraint says this objective needs to be smaller than 20, and the originally calculated objective value is 25. However, due to the -1 multiplication, it becomes -25 and suddenly it complies with a constraint.

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

This PR fixed the aforementioned issues.

---

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.