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

fmu design matrix: QC of distributions #664

Open
bkhegstad opened this issue Aug 10, 2021 · 2 comments
Open

fmu design matrix: QC of distributions #664

bkhegstad opened this issue Aug 10, 2021 · 2 comments

Comments

@bkhegstad
Copy link

As now it is difficult for the users to QC that the distributions they have chosen is as they would like them to be. I suggest to add a QC-sheet in the generated design matrix with the following content (and perhaps more)

  1. Statistical tables for each variable of what was actually sampled (min, P90, P50, mean, P10, max)
  2. Estimated correlation between each variable from what was actually sampled
  3. Plots of the histograms for each variable from what was actually sampled.
  4. The probability of each category of discrete variables from what as actually sampled

The tables should perhaps also compare with the input-values. The users are usually not aware that the probabilities they put in are not reproduced exactly - or can even be off quite a lot. This generates a lot of confusion -especially if there is a discrete variable that is important for the result. Then it can be important that the probabilities sampled are (low, medium, high) = (0.25, 0,43, 0.32) instead of (0.3, 0.4, 0.3)

@tralsos
Copy link
Contributor

tralsos commented Aug 12, 2021

As I've understood it, the long term plan is to have fmudesign as a part of ert. The QC functionallity you suggest is probably also relevant for parameters drawn by GEN_KW. But for current use, I think all these parameter statistics mentioned are covered by webviz ? Just that webviz uses parameters.txt as input instead of the generated design matrix. And of course no comparison to what was the input distribution parameters.

@bkhegstad
Copy link
Author

The process of defining and setting up a design matrix is often an iterative procedure. If you have to run ERT to be able to see how the input variables actually was sampled, that requires a lot of runs. If you could see what you actually have sampled/defined from the input distributions before you run ERT, you could save a lot of time. This is a strength with @risk. When using @risk to generate the design matrix (as I do), I can go through each variable and see what was actually sampled and what the resulting correlation actually became. If I am not happy with the results I can change input and rerun - without having to start the heavy ERT-machinery. Especially what resulting P90, mean, P10 actually is (and the probabilities) is useful

@dafeda dafeda transferred this issue from equinor/fmu-tools Nov 28, 2024
@eivindjahren eivindjahren added the christmas-review Issues and PRs for Christmas review label Dec 13, 2024
@eivindjahren eivindjahren removed the christmas-review Issues and PRs for Christmas review label Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants