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

Add systematic errors in the error columns of the SED specifications #181

Open
cosimoNigro opened this issue Sep 17, 2021 · 2 comments
Open

Comments

@cosimoNigro
Copy link
Contributor

cosimoNigro commented Sep 17, 2021

I was playing along with SED flux points and radiative models.
Having the systematic error specified for the flux points, beside improving the fit, takes properly into account the inter-calibration effects in MWL SEDs.

What do you think of adding systematic errors in flux among the SED error columns?
It can be a new column like {NORM_REP}_sys or {NORM_REP}_syserr.
The experiment producing flux points and statistical errors might thus add its own estimate of systematic errors.
Or one might extend an already existing SED file adding a column following what an experiment claims (e.g. 15% in flux).

Of course one could also take into account the systematic errors in energy (i.e. along the x-axis) but I think this is more complex and for the time being the ones in flux are a good start.

@micheledoro
Copy link

It's always good to add information, but then it must be clear. Combining systematics errors without knowing their statistical distribution is maybe a risk. Unless we assume (or impose) that they are normal too and somehow indipendent. For example, if you put atmospheric transmission as a systematics without considering that it bias also the energy you can get into trouble.

@cosimoNigro
Copy link
Contributor Author

cosimoNigro commented Sep 17, 2021

Hi @micheledoro, I thought the experiments could (optionally) provide a global estimate of the systematic uncertainties on flux points. How the different effects are combined into this estimate I think it is outside the scope of the specs.

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

2 participants