Name: wfc3_photometry
Owner: Space Telescope Science Institute
Description: null
Created: 2017-11-17 19:37:19.0
Updated: 2018-05-14 18:45:24.0
Pushed: 2018-05-14 18:45:23.0
Homepage:
null
Size: 26
Language: Python
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Email | Most Recent Commit | # Commits |
|---|
README
wfc3_photometry
Welcome to the WFC3 Photometric tools repository. This repository will be used as the home base for all the tools we develop to unify/optimize our photometry data analysis. For now, the goal of this project is to create a unified pipeline that encompasses the work done by several team members, to minimize the amount of repeated efforts/errors in processes. Specifically we want to develop a comprehensive pipeline for analyzing the photometric standard star images, but the tools in this repository will probably work for other data.
The pipeline will be run via the use of config files. The config files will be stored with the outputs,
Rough skeleton of pipeline:
- [x] Query MAST Database for all observations of target(s)
- [ ] Check calibration version?
- [ ] Download all observations not in data directories (~~Via Astroquery or QL?~~ Via MAST API)
- [ ] Filter bad datasets
- [x] Visit level drizzle all images (code exists already)
- [ ] Detect source in each drizzled image?
- [ ] Use WCS tools to transform coordinates to find them in FLT/FLC frame
- [ ] Validate detections?
- [ ] Run LACosmic on relevant exposures, save output images in a parallel tree.
- [ ] Run the photometry, use several different apertures, bg methods etc.
- [x] Implement sigma-clipped median/mode bg measurement for photutils
- [x] Implement full error computation (DAOPHOT style errors)
- [ ] Save results to csv's? hdf5? Some format that will be easy for anyone to access
- [ ] Make some preliminary plots from these results.
Ideas:
- Base the flow of the software on the contam pipeline?
- Write as little new code as possible, use packages that are well developed and maintained
- Document the pipelines well so others can work on the project without a huge learning curve
Other To-do's:
- [ ] Make modules out of components of pipeline
- [ ] Write a top-level wrapper (pipeline) that runs with plaintext/json? config file
