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

data reporting to TNS #167

Open
djones1040 opened this issue Jun 19, 2020 · 3 comments
Open

data reporting to TNS #167

djones1040 opened this issue Jun 19, 2020 · 3 comments

Comments

@djones1040
Copy link
Collaborator

Hi Ken, the YSE executive committee met and wanted to adjust the data being sent to TNS for YSE objects, if possible. We wanted to send:

  1. any raw, unforced photometry from the first epoch that is not z band
  2. any raw, unforced photometry from the second epoch that is not z band
  3. if there are detections only in z for either epoch, then include z
  4. no data for things where a TNS entry already exists
    Would it be possible to make these changes?
@genghisken
Copy link
Owner

The changes are possible. I need to change a bit of code logic, but shouldn't be too difficult. I'll leave this open until the code is done.

@genghisken
Copy link
Owner

Note that our TNS replica will be slightly out of date, so there are possible times when (e.g.) ZTF report something before our copy is updated. Hence we won't know they've been reported by someone else until the act of reporting (when I get a message back from TNS stating that the object already exists). Shouldn't happen too many times, but these edge cases will happen occasionally.

@djones1040
Copy link
Collaborator Author

thanks Ken, that sounds good - I don't think that should be an issue for the EC.

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