...
query, filter and stream are all the same in Lasair
Sherlock - cross-matches location of transient with other catalogs
Julien Q to Roy - screen annotation - what is the feedback on this? What can you say about user-based annotations?
Roy answer - We have not built the system yet. Michael will talk later about one of the classifications. We would like to share classifications from other brokers eg FINK, if acceptable.
Sara Q - stream annotation - are there plans to create a collaboration so people are not competing on the same follow-ups? Will the annotations become public on a “follow-up” list or similar?
Roy answer - Marshall refers to a group of people able to submit opinions on transients and make decisions.
Andy answer - Marshall building is beyond our scope to solve this.
Jakob - annotations are hard. We decided instead to be flexible so people can do what they want but they then have the responsibility to maintain and make useful. On 2nd slide, no arrow to/from Rubin Science platform. Have you thought about how this relates to the DB contents. How will eg. updated photometry be incorporated?
Andy answer- grimly aware need to think about this but not yet solved.
Jakob Q to Eric - how frequently can we expect updates and show seriously to take these.
Eric answered - let discuss during talk
Science experience with ZTF (Matt Nicholl)
Experiments with Lasair-ZTF
Use cases
Nuclear transient research currently migrating to Google Colab notebook
Difficulties are: filtering on colour, streams clogged with old objects, not having full light curve history (this is the biggest problem)
Intend doing citizen science with light curves. Documentation to do this was helpful
Lensed transients
Email alerts could be more human readable
A thumbnail for each object on streaming page would be helpful
Testing spectra in advance would be good.
Email alerts and web interface are what
Roy stated that the light curves are coming so the major problem identified will be solved. Like/dislike for an object is the tail of tiger and could mean Lasair in effect building marshalls. As yet do not have the facility to push data into notebooks but will let you know this ready. facility yet.
Eric Q to Matt - Regarding the boundaries with marshalls, how do keep track of candidates?
Matt answer - luckily the numbers are not big so not a problem yet. Have been using a note in Google collab. Also within research group have started tentative steps to building our own marshall.
Cosimo Q to Roy - Agree color curve would be fantastic. What about using Gaussian processes to interpolate the light curves in order to produce colours (with uncertainties)?
Roy - happy to look at Gaussian code and to include this in the Lasair pipeline.
Cosimo will forward the code to Roy.
Jakob Q to Roy - you are all using Google colab but we have encountered python limitations
Roy answer - Ken will talk about this later.
Ken - do not know how Google Colab behaves when it requires C binaries other than NumPy. Not yet installed own C code. We should explore this.
Gareth answer- aware that Nubaldo will be running on RSP next door so if Google Colab not suitable then can consider integration with the RSP.
...
(need slides)
Lasair team has introduced REST APIs using Django Rest Framework (looks to be defacto standard)
See http://lasair-iris.roe.ac.uk/api for initial notes from Roy
Effectively, these are machine-readable versions of functions provided (interactive) on webpages
/api/cone -
/api/query
…
Python wrapper “lasair” (available via PIP install) to help use API.
Plan to add support for querying Cassandra directly
Also have Jupyter Notebook examples, hosted on Google Colab
Need user account on Lasair to access
Ken provided live demo of cone-search notebook.
API throttled, based on different levels of token
Action taken in response to use who was submitting thousands of queries, and putting strain on service (now using more effiicient watch-list approach).
Anonymouse use limit to 10-per-hour, 1000 rows per query, …
1720 Tools interface (Andy Lawrence)
1730: Discussion
...