Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing sort from RELAPparser.py #1024

Conversation

Jimmy-INL
Copy link
Collaborator

@Jimmy-INL Jimmy-INL commented Jul 16, 2019


The PR addresses issue #995, by removing the sort from RELAPparser.py.
In addition, a typo was corrected in the user manual, under runInfo.tex: the was defined as colon separated string instead of column separated.

Ref. #995.

Ref. #995

No change in functionality, and regression tests for the RELAP interface passed (at least on my machines).


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.

Screen Shot 2019-07-22 at 1 14 38 PM

moosebuild added 30 commits April 4, 2017 14:33
@wangcj05
Copy link
Collaborator

@Jimmy-INL The issue #995 was addressed in PR #996, you may consider to merge your PR with PR #996, please talk to @PaulTalbot-INL. In addition, there are some questions regarding the issue #995 closure checklist. Please try to resolve that issue.

@PaulTalbot-INL
Copy link
Collaborator

Since this involves changing exactly 8 characters in 1 line, I don't think combining the pull requests in some way makes much sense. I'll close the other pull request, as @Jimmy-INL will have the resources to properly address the concerns @wangcj05 has raised in the issue closure process.

@moosebuild
Copy link

Job Test Ubuntu 16 on 1a39983 : invalidated by @wangcj05

Could not read from remote repository

@wangcj05
Copy link
Collaborator

Tests failed, and I believe our devel will have similar issues:

  1. framework/ROM/SKLearn/GP: we need to increase the error tolerance (small diff for Linux systems)
  2. timeout for varma test
  3. qsub test failed for adapted sobol
    @alfoa @PaulTalbot-INL

@Jimmy-INL
Copy link
Collaborator Author

Jimmy-INL commented Jul 30, 2019 via email

@moosebuild
Copy link

Job Test CentOS 7 on db38a2b : invalidated by @alfoa

1 similar comment
@moosebuild
Copy link

Job Test CentOS 7 on db38a2b : invalidated by @alfoa

@moosebuild
Copy link

Job Test CentOS 7 on db38a2b : invalidated by @wangcj05

varma timeout

@alfoa alfoa changed the base branch from devel to alfoa/fix_for_relap5_3d_interface September 24, 2019 14:28
@alfoa
Copy link
Collaborator

alfoa commented Sep 24, 2019

Ok guys,
I changed the base of this PR from devel to a branch I just created. Unfortunately there is another problem with RELAP5 interface that has been discovered during the workshop.

I will address it there (and merge this PR in that branch)

@alfoa alfoa merged commit a344d81 into idaholab:alfoa/fix_for_relap5_3d_interface Sep 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants