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

[WIP] Jimmy testing representativity based on changes in basic stat #1790

Closed

Conversation

Jimmy-INL
Copy link
Collaborator


Pull Request Description

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

Closes #1650 and #1546

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

This adds the representativity PP based on the validation gate


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.

@Jimmy-INL Jimmy-INL requested a review from wangcj05 March 17, 2022 03:40
Copy link
Collaborator

@wangcj05 wangcj05 left a comment

Choose a reason for hiding this comment

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

@Jimmy-INL I have a couple of comments for you to consider.

framework/Metrics/metrics/RepresentativityFactors.py Outdated Show resolved Hide resolved
#Internal Modules------------------------------------------------------------------------------------
from .MetricInterface import MetricInterface
# from Metrics.metrics import MetricUtilities
from utils import InputData, InputTypes
Copy link
Collaborator

Choose a reason for hiding this comment

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

use new ravenframework import strategy to import the modules

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@joshua-cogliati-inl, could you direct me to the new import strategy?

Copy link
Contributor

Choose a reason for hiding this comment

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

framework/Metrics/metrics/RepresentativityFactors.py Outdated Show resolved Hide resolved
framework/Metrics/metrics/RepresentativityFactors.py Outdated Show resolved Hide resolved
Comment on lines +107 to +112
senMeasurables = kwargs['senMeasurables']
senFOMs = kwargs['senFOMs']
covParameters = kwargs['covParameters']
r = (senFOMs.T @ covParameters @ senMeasurables)/\
np.sqrt(senFOMs.T @ covParameters @ senFOMs)/\
np.sqrt(senMeasurables.T @ covParameters @ senMeasurables)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why do you need to create a metric class to do this calculation? It seems to me this calculation is only specific to representativity. How can we use it for other applications? If not, I would suggest to move it the representativity PP.

@wangcj05
Copy link
Collaborator

I think this PR can be closed. @Jimmy-INL Please let me know if you need to reopen it.

@wangcj05 wangcj05 closed this May 19, 2022
@wangcj05 wangcj05 deleted the Jimmy-testingRepresentativity-afterJosh-BasicStat branch December 7, 2022 17:14
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.

[TASK] Adding representativity PP for validation
3 participants