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

Should ParameterGroup be split #138

Open
chris-little opened this issue Nov 2, 2022 · 1 comment
Open

Should ParameterGroup be split #138

chris-little opened this issue Nov 2, 2022 · 1 comment
Labels
enhancement New feature or request Priority 2 Dsesirable V1.1 Non-breaking change for Version 1.1

Comments

@chris-little
Copy link
Contributor

chris-little commented Nov 2, 2022

ParameterGroup has two main use cases:

  1. to group values that are really a single vector or tensor value, rather than scalar. such as Wind Velocity expressed as Wind Speed and Wind Direction, or Surface Wind Stress;
  2. to group a value with some derived statistical values, such as standard deviation.

ParameterGroup addresses both of these use cases effectively, but in the future, should the two above patterns be explicitly identified?

@chris-little chris-little added enhancement New feature or request V1.1 Non-breaking change for Version 1.1 labels Nov 2, 2022
@jonblower
Copy link
Contributor

There are examples of both in the current spec but they would need to be turned into proper specifications rather than illustrative examples.

Just to clarify the second use case - it's not about grouping values with statistics that are derived from them, it's about grouping scalar fields that represent the parameters of a probability distribution function, thereby enabling us to represent uncertainty or sub-grid variability. So for each element in the domain, if the PDF is Gaussian, we would have the mean and the standard deviation of the quantity at that location. Other PDFs would need a different set of parameters.

@chris-little chris-little added the Priority 2 Dsesirable label Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Priority 2 Dsesirable V1.1 Non-breaking change for Version 1.1
Projects
Status: No status
Development

No branches or pull requests

2 participants