-
Notifications
You must be signed in to change notification settings - Fork 0
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
push new transients to YSE_PZ after they're promoted to "good" or "possible" #155
Comments
This looks very similar to what we already do for TNS. (Anything promoted to the good list automatically gets sent immediately to the TNS.) Shouldn't be too difficult. I just need to know the API details. |
thanks Ken, I'll write a short module for this and paste here once it's finished. Can do it later this week. |
Hi Ken, took 20 days apparently but I finally wrote a code to do this - see the very bottom for my test example, that's the only info your code will need to include to send things directly to YSE_PZ once they're promoted. syntax is a bit annoying but this should work! If you don't have YSE_PZ credentials for variables _dblogin and _dbpassword, I can send you mine in a private message. and I was hoping the "name" variable would either be the TNS name for things that have just been promoted, or the 10DYSEaaa-type name for "possible" candidates. Any questions about the code or things I could improve?
|
OK... Interesting... About time we incorporated the dustmap code! So... What I'll do is wrap this in some daemon code. The daemon can sit and listen to port N (to be defined) and fire off this request to yze_pz. All it needs is the object ID - I can pass that to the daemon from the webserver code, then collect all the other pertinent info from the database. I have a horrible mixture of python 2 and 3 code running everywhere. All the web stuff is still in python 2. (I'm in the long process of doing conversions, but I can't roll the code out until it's all converted.) The daemon allows me to run whatever python environment I want on a separate server and all it needs to do is listen for an object ID. Apologies for very slow progress on many fronts - too many things going on (ATLAS fixes, LSST, reviews, substantial machine migrations), and I was also sick last week, so also playing catchup... |
thanks Ken, nice that I can submit some code for once instead of just asking for stuff and not providing any help! |
should add that there's almost certainly a better way to do the forced photometry once this code is on the server side, but if pinging the URL works for you then it's fine with me |
If it's possible to write a module that sends transients to YSE-PZ via our API once they are promoted to "good" or "possible" it would remove a 1-2 hour lag in our ability to collect metadata/ZTF observations and request followup observations through YSE-PZ. This could also make it easier for the sniffing team to comment on new/interesting things and streamline our vetting/triage process. I'm happy to write a module for this with a little guidance on how the formatting would work.
The text was updated successfully, but these errors were encountered: