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

Bandpasses for LSST need an update #335

Open
2 tasks
rbiswas4 opened this issue Dec 20, 2021 · 0 comments
Open
2 tasks

Bandpasses for LSST need an update #335

rbiswas4 opened this issue Dec 20, 2021 · 0 comments
Labels
help-wanted No one is working on this issue yet (that we know of!)

Comments

@rbiswas4
Copy link
Member

LSST bandpasses provided by the Rubin Observatory have been updated on 5/7/21, while the sncosmo builtins have been last updated in 2016. Such updates are always in the throughputs repository: https://github.com/lsst/throughputs

The complete updates are found in https://github.com/lsst/throughputs/tree/main/baseline (version 1.7 seems the current one)

In sncosmo, we usually use truncated bandpasses which remove the bandpass values that are below a certain threshold 10**(-250), in order to save time in magnitude calculations. This is done by the script https://github.com/lsst/throughputs/blob/main/approximate_baseline/approximateBandpasses.py
and stored in the approximate_baseline directory of the repository e.g : https://github.com/lsst/throughputs/blob/main/approximate_baseline/total_g.dat

The total indicates that it uses the atmosphere as 1.2 X throughout.

  • In previous versions, this made a lot of sense, as the threshold only removed values that were recorded in the csv files as zero. We should manually check if these approximate throughputs still make sense (does not lead to patchy bandpasses)
  • The sncosmo builtins for lsst bandpasses should be updated to these throughputs.
@benjaminrose benjaminrose added the help-wanted No one is working on this issue yet (that we know of!) label Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help-wanted No one is working on this issue yet (that we know of!)
Projects
None yet
Development

No branches or pull requests

2 participants