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

Measurements with missing errors #125

Open
Gregstrq opened this issue Sep 18, 2022 · 4 comments
Open

Measurements with missing errors #125

Gregstrq opened this issue Sep 18, 2022 · 4 comments

Comments

@Gregstrq
Copy link

Is it hard to make measurements support data with non-missing value, but missing uncertainty? Data with missing uncertainty is quite different from the data with zero uncertainty, so it is good to fistinguish these two cases.

Looks like linear propagation of errors should be easy in this case: you just propagate missing.

I've stumbled upon an actual example, where such option is required, while parsing the file with the data of half-lifes of different nuclear isotopes. I have noticed that normally half life has an uncertainty provided. However, for some of the isotopes, the uncertainty is simply missing.

@giordano
Copy link
Member

Duplicate of #59?

@Eben60
Copy link
Contributor

Eben60 commented Sep 18, 2022

Yes, it is duplicate of #59 and of #62 , and it was decided that measurement(1, missing) should throw error with argumentation as following:

#62 (comment)

This case doesn't seem as clear-cut to me. My reasoning is that just because the uncertainty has gone missing somewhere, doesn't mean the actual value is not known and should be missing. A missing uncertainty might even be interpreted to mean zero uncertainty by some. I think it is better to throw an error here, than just make assumptions for the user.

But why should it be a problem if missing uncertainties just propagate?

x = 1.0 ± 2.0
y = 1.0 ± missing
x + y
>  2.0 ± missing

We do not make any assumptions for the user, they can always decide how to treat the Missings in the final result.

@giordano
Copy link
Member

But why should it be a problem if missing uncertainties just propagate?

That'd require changing the layout of the datastructure, with a likely significant impact on performance.

@Gregstrq
Copy link
Author

It looks like the missing uncertainty can be emulated by some non-physical value, like NaN.

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

No branches or pull requests

3 participants