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

[TASK] Basicstatistic subdomain #1923

Closed
10 tasks done
aalfonsi opened this issue Aug 3, 2022 · 0 comments · Fixed by #2119
Closed
10 tasks done

[TASK] Basicstatistic subdomain #1923

aalfonsi opened this issue Aug 3, 2022 · 0 comments · Fixed by #2119
Assignees
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment

Comments

@aalfonsi
Copy link
Collaborator

aalfonsi commented Aug 3, 2022


Issue Description

Is your feature request related to a problem? Please describe.
It would be extremely useful to allow the basic statistics to accept a "subdomain" definition (a grid in the input space where to perform the computation of the moments and correlation, sensitivity matrices).

For example,
allowing for the definition of a grid (like in the grid sampler)

Describe the solution you'd like
Possibility to compute "sensitivity coefficients" (e.g. reactivity coefficients) based on a Grid sampling

e.g.

T (100,200,300,400,500,600)
dk/dT (200,300,400,500)

Describe alternatives you've considered
To split the dataset by hand and apply a basic statistic to each of the separate datasets


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@aalfonsi aalfonsi added priority_minor task This tag should be used for any new capability, improvement or enanchment labels Aug 3, 2022
@aalfonsi aalfonsi mentioned this issue Sep 15, 2022
9 tasks
@mandd mandd self-assigned this May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_minor task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants