GA features update - Having multi-objective optimization (NSGA-II )

[JunyungKim]

---

Pull Request Description

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

2069

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

---

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.

[moosebuild]

Job Mingw Test on 7b66055 : invalidated by @joshua-cogliati-inl

restarted civet

[moosebuild]

Job Mingw Test on 7b66055 : canceled by @wangcj05

take too long

[moosebuild]

Job Test mac on a255665 : invalidated by @Jimmy-INL

[moosebuild]

Job Mingw Test on 52717ae : invalidated by @joshua-cogliati-inl

failed in fetch

[moosebuild]

Job Mingw Test on 52717ae : invalidated by @joshua-cogliati-inl

failed in fetch

[moosebuild]

Job Test Ubuntu 18-2 Python 3 on 52717ae : invalidated by @joshua-cogliati-inl

failed in fetch fatal: fetch-pack: invalid index-pack output

[moosebuild]

Job Test mac on 52717ae : invalidated by @Jimmy-INL

[moosebuild]

Job Test Ubuntu 18 PIP on 5e3d977 : invalidated by @Jimmy-INL

[moosebuild]

Job Mingw Test on 5e3d977 : invalidated by @Jimmy-INL

[moosebuild]

Job Test mac on 7916f3a : invalidated by @Jimmy-INL

[moosebuild]

Job Precheck on bc9ab9f : invalidated by @joshua-cogliati-inl

failed because of hpcgitlab being down

[moosebuild]

Job Test Ubuntu 18 PIP on beaba5a : invalidated by @joshua-cogliati-inl

restarted civet

[moosebuild]

Job Test Ubuntu 18 PIP on beaba5a : invalidated by @joshua-cogliati-inl

restarted civet

[moosebuild]

Job Test Ubuntu 18 PIP on beaba5a : invalidated by @joshua-cogliati-inl

failed in fetch

[moosebuild]

Job Test Ubuntu 18 PIP on beaba5a : invalidated by @joshua-cogliati-inl

restarted civet

[moosebuild]

Job Test Ubuntu 18 PIP on 163eb87 : invalidated by @Jimmy-INL

[moosebuild]

Job Test Ubuntu 18-2 Python 3 on 163eb87 : invalidated by @Jimmy-INL

[moosebuild]

Job Test qsubs sawtooth on eadd2d4 : invalidated by @joshua-cogliati-inl

failed in set (HTTP error)

[moosebuild]

Job Test Ubuntu 18-2 Python 3 on 729187c : invalidated by @JunyungKim

[moosebuild]

Job Test Ubuntu 18-2 Python 3 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Mingw Test on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test CentOS 7 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test CentOS 8 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test CentOS 8 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Fedora 31 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Fedora 32 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Ubuntu 16 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Ubuntu 16 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Fedora 31 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test CentOS 7 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test CentOS 8 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Fedora 31 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test Ubuntu 16 on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Mingw Test on 729187c : invalidated by @Jimmy-INL

[moosebuild]

Job Test qsubs sawtooth on 729187c : invalidated by @joshua-cogliati-inl

FAILED: Timeout tests/framework/PostProcessors/TemporalDataMiningPostProcessor/DimensionalityReduction/MiniBatchSparsePCA Timeout tests/framework/PostProcessors/TemporalDataMiningPostProcessor/DimensionalityReduction/LocallyLinearEmbedding

[moosebuild]

Job Mingw Test on 729187c : invalidated by @joshua-cogliati-inl

failed in set python environment

[alfoa]

Can I suggest to address #2053 #2049 as well here? At least in terms of manual/documentation (for the constraint)?