-
Notifications
You must be signed in to change notification settings - Fork 25
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
How do we calculate the misfit that is plotted? #377
Comments
misfits is calculated with this implementation if i understand correctly in With regards to displaying the actual equation i'm not sure if i agree. I would like to think of it as an internal thing to our application and nothing a user should care about. On the other hand i guess i understand people would like to know what is the basis of the calculations..... 🤔 Do you @sondreso have any input to this? |
I think there are many reasons why one would want to analyze the misfits, particularly this one that seems to be standardised misfit (response-observed)/standard_deviation. One inference that can come from it is if the estimation of the uncertainty (standard deviation) is appropriate. For example, if the misfits are too large, that would mean that the uncertainty is probably underestimated. With too large, we take in consideration that a normal distribution encompasses 99.7% of its points within +- 3 standard_deviation. There are other things that can be analyzed, for example, is a particular time that has high misfit or all the observation in a given time series have similar values and distribution. |
Do you also then mean that we might should have different implementations of the misfit and the user should be able to choose / configure the calculation? |
Good question! |
Is your feature request related to a problem? Please describe.
The definition of the misfit calculation is important because there are many ways to do it.
I saw another vizualisation tool from the Drogon tutorial only plotting (obs-realization). It seems webvis-ert adopts another equation, and it would be nice that the user could find this information easily.
Describe the solution you'd like
I would have the equation in the x-axis as pointed in the image, I suspect the equation is simply |observation-realization|/standard_deviation.
The text was updated successfully, but these errors were encountered: