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

Talbpaul/issue mr templates #4

Merged

Conversation

PaulTalbot-INL
Copy link
Collaborator

@PaulTalbot-INL PaulTalbot-INL commented Mar 27, 2017


Pull Requeset Description

What issue does this change request address?

This will close #3.

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

Adds/updates the issue/change request templates to the new repository.


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?

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](https://hpcgitlab.inl.gov/idaholab/raven/wikis/Developer_Information#python-code-standard) for details.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to copy the standard to the wiki, or reference the Test Plan document instead.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ha, yes, this is true. Do you have a preference? I like the wiki myself. I can do that if you want.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, feel free to make the change.

@joshua-cogliati-inl
Copy link
Contributor

I have reviewed the changes and had one comment.

@PaulTalbot-INL
Copy link
Collaborator Author

I made it a standalone page, since it contains quite a bit more information than when we first put it in "developer information". In the future as we construct the contribution guide, we can link to it from there.

@joshua-cogliati-inl
Copy link
Contributor

I have reviewed the changes. There are no code or build changes, so testing is not required.

@joshua-cogliati-inl joshua-cogliati-inl merged commit 952ef3c into idaholab:devel Mar 29, 2017
@PaulTalbot-INL PaulTalbot-INL deleted the talbpaul/issue-mr-templates branch September 7, 2017 17:08
jbae11 referenced this pull request in jbae11/raven Mar 28, 2018
alfoa pushed a commit that referenced this pull request Aug 8, 2018
* serpent interface python file

* output parser script

* test input for raven

* workDir with input file and geom file

* pep8 tried

* pep8 tried

* Fix pep8 errors in framework/CodeInterfaces/SERPENT/SerpentInterface.py

* Fix pep8 errors in framework/CodeInterfaces/SERPENT/output_parser.py

* depletion composition also recorded

*  better path

* depletion calculation

* updated parser

* documentation, license

* more documentation and mention iso file

* solves #4

* pushed to wrong repo

* Revert "pushed to wrong repo"

This reverts commit da500a7.

*  get path from script, not hardcode

* percent cutoff from 0-1

* underscore to camelback script

* RAVEN naming and docstring conventions

* naming convention

* filename change

* avoid converting __ to nothing

* imp_keff fix

* no more underscore

* test input name chnage

* underscore to camelback poses too many problems

* camelback interface script

* import correctly

* spacing for docstring

* SERPENT interface documentation general

* SERPENT interface manual update

* test for Serpent interface test1 - input parsing

* gold answer to Serpent Interface test 1 - input parsing

* gitignores xml

* added back model

* output tests

* test change to one test

* Serpent test more

* gold files

* output files of SERPENT

* reflected comments

* trailing whitespace

* trailing whitespace

* Remove test input file

* delete aux files

* delete unnecessary function

* interface fix

* outputparser fix

* delete files not read by interface

* delete files not read by interface2

* delte raven-generated input files in gold

* user manual fix

* added examples
@alfoa alfoa mentioned this pull request Aug 8, 2018
8 tasks
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.

New issue and merge request templates
2 participants