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

jdmin meaning in Lasair #191

Open
chrisfrohmaier opened this issue Jun 2, 2023 · 1 comment
Open

jdmin meaning in Lasair #191

chrisfrohmaier opened this issue Jun 2, 2023 · 1 comment

Comments

@chrisfrohmaier
Copy link

What does the jdmin column actually store?
Should it be the discovery date or the oldest date in a ZTF alert packet?

I've noticed this when using filters to find short lived transients. Filtering on say, jdmax-jdmin < N days, finds objects with loads of light curve history before jdmin.

We're also trying to search for more long-lived transients by doing jdmax-jdmin > N days in the filter, but noticed that for ZTF20abrbeie the jdmin is only 30 days ago, but the light curve has more than 800 days of history.

Without a true date of discovery or earliest detection it is impossible to do some types of archival searches in Lasair.

@RoyWilliams
Copy link
Contributor

jdmin is the earliest of the candidates that are included with the alert from ZTF. That alert has 30 days of lightcurve, so jdmax - jdmin cannot be more than 30 days. When we built Lasair we assumed it would be about rapid transients, not about archival searches. There has been a lot of discussion about this at Lasair meetings, and we have petitioned Rubin to include the true number -- see here

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