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

Auto follow-up: cancel if already classified or has spectra #244

Merged
merged 2 commits into from
Sep 27, 2023

Conversation

Theodlz
Copy link
Collaborator

@Theodlz Theodlz commented Sep 27, 2023

This goes in pair with a SkyPortal PR, where we make it possible to cancel triggering a follow-up request if a source is already classified, or already has spectra

@Theodlz Theodlz requested a review from mcoughlin September 27, 2023 15:26
Copy link
Collaborator

@mcoughlin mcoughlin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess you test that functionality differently now. Just noting the delete.

kowalski/tests/test_alert_broker_ztf.py Show resolved Hide resolved
@Theodlz
Copy link
Collaborator Author

Theodlz commented Sep 27, 2023

I guess you test that functionality differently now. Just noting the delete.

So it's the same test, plus I post a classification and run the filter again to verify that it does not trigger which is what we want. Just a way to test the skyportal + kowalski interaction at least locally, as we don't have SP running in the GA. We could make it point to preview, but not essential.

@Theodlz Theodlz merged commit e406925 into skyportal:main Sep 27, 2023
2 checks passed
Theodlz added a commit that referenced this pull request Sep 28, 2023
* BTS model v1 + extra ML features (#243)

* update the BTS model
* extra ML features

* Auto follow-up: cancel if already classified or has spectra (#244)

* dont trigger followup requests if there is already classification or spectra for a source

* fix duplicate comments, test no followup when classified

* Temporary: use all candidates (not just prv_candidates) to generate lightcurve  (#249)

While we are retrieving data in prod for the prv_candidates, make sure to post all the candidates for an object as detections.
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

Successfully merging this pull request may close these issues.

2 participants