update LOGOS submodule ID

[wangcj05]

---

Pull Request Description

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

see #1114

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.

[wangcj05]

@dylanjm Here is the PR for LOGOS dependencies update (remove the pined version for pyomo)

[dylanjm]

Changes look good to me

[moosebuild]

Job Mingw Test on 5fad4bb : invalidated by @dylanjm

Timeout

[joshua-cogliati-inl]

Change to a new version of LOGOS on branch devel.

[moosebuild]

Job Mingw Test on 5fad4bb : invalidated by @joshua-cogliati-inl

Timeout tests/framework/pca_adaptive_sgc/test_adaptive_sgc_poly_pca_analytic

[wangcj05]

@joshua-cogliati-inl @dylanjm I guess we do not need to wait the regression tests to be finished. Since it is submodule updates, and the only update is to remove the pined version for pyomo. Let me know what do you think.

[dylanjm]

@wangcj05 Yeah, I say we go for it.

[moosebuild]

Job Mingw Test on 5fad4bb : canceled by @wangcj05

library update only, will be tested in HERON submodule ID update.