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 ZTF Forced Photometry Service #1057

Open
1 of 5 tasks
Tracked by #832
jchate6 opened this issue Oct 1, 2024 · 0 comments
Open
1 of 5 tasks
Tracked by #832

Add ZTF Forced Photometry Service #1057

jchate6 opened this issue Oct 1, 2024 · 0 comments
Labels
Data Services Data Services enhancement New feature or request User Issue Raised by a user

Comments

@jchate6
Copy link
Contributor

jchate6 commented Oct 1, 2024

As a tom user, I would like a module to define and query forced photometry servers to pull in photometric and spectroscopic data for my targets. Rachel's intern Ezequiel has a tom toolkit project branch with code for accessing atlas, ztf, and and panstarrs forced photometry. They all access in different ways, but I think it would be best to design an interface to handle all of these methods of requesting forced photometry into a tom module, like tom brokers or tom_observations. It seems like you might want to request them from a specific targets detail page, or from its own interface. The forced photometry servers can work synchronously, asynchronously (task queue), and asynchronously with the end result emailed to you, which then requires you to upload data files from that email into your tom.

Modes of operation to support:

  • ztf - email you data files that then need to be uploaded
  • panstarrs - synchronous gets images from position
  • atlas - asynchronous task queue until data is ready

This story is to copy and refactor the code for ztf implementation of forced photometry service

https://github.com/econtrerasmartinez09/myTOM

Tasks:

  • Add ztf implementation of tom forced_photometry server
  • Create ZTF data processor implementation
@github-project-automation github-project-automation bot moved this to Triage in TOM Toolkit Oct 1, 2024
@jchate6 jchate6 added Data Services Data Services enhancement New feature or request labels Oct 1, 2024
@jchate6 jchate6 added this to the TOMToolkit version 3.0 milestone Oct 11, 2024
@jchate6 jchate6 moved this from Triage to Backlog in TOM Toolkit Oct 17, 2024
@jchate6 jchate6 moved this from Backlog to Triage in TOM Toolkit Nov 14, 2024
@jchate6 jchate6 added the User Issue Raised by a user label Nov 14, 2024
@jchate6 jchate6 moved this from Triage to Backlog in TOM Toolkit Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Services Data Services enhancement New feature or request User Issue Raised by a user
Projects
Status: Backlog
Development

No branches or pull requests

1 participant