# Does Lasair support space+time coverage?

**URL:** <https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073>\
**Category:** Lasair\
**Created:** [November 14, 2023, 10:11pm UTC](https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073 "2023-11-14T22:11:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrad](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jrad/32/2717_2.png) [@jrad](https://www.rubin.community/u/jrad)\
**Post date:** [November 14, 2023, 10:11pm UTC](https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073/1 "2023-11-14T22:11:24Z")

</div>

MOCPy has `STMOC` and `timeMOC` type objects, which can explore the region and times that events might happen. Is this something that Lasair can support, or only flat MOCs?

The science goal is: If I had ~10000 stars that I wanted to monitor at certain windows of time, could I do that with Lasair?

---

<div class="post-metadata">

**Author:** ![roy](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/roy/32/1254_2.png) [@roy](https://www.rubin.community/u/roy)\
**Post date:** [November 15, 2023, 12:07pm UTC](https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073/2 "2023-11-15T12:07:20Z")

</div>

Lasair’s watchmaps are 2D sky area – RA and Dec. The primary reason for watchmaps is to find counterparts of multi-messenger astronomy such as gravitational wave events; in that case the sky area is complex, but the time dimension is simple, just a start and stop, so we only need flat MOCs.

An alternative to us enhancing the real-time system might be an off-line data mining of the Lasair database. We already have a [watchlist of 5908 nearby stars](https://lasair-ztf.lsst.ac.uk/watchlists/1159/). What are you looking for in their lightcurves to do your “Earth Transit Zone” study?

---

<div class="post-metadata">

**Author:** ![roy](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/roy/32/1254_2.png) [@roy](https://www.rubin.community/u/roy)\
**Post date:** [November 15, 2023, 12:13pm UTC](https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073/3 "2023-11-15T12:13:14Z")

</div>

[Found it. Technosignatures](https://www.youtube.com/watch?v=tbq0EVyrPT4). If you have the code that can discern that from a light curve, then we can run it on ZTF.

---

<div class="post-metadata">

**Author:** ![jrad](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jrad/32/2717_2.png) [@jrad](https://www.rubin.community/u/jrad)\
**Post date:** [November 15, 2023, 4:47pm UTC](https://www.rubin.community/t/does-lasair-support-space-time-coverage/8073/4 "2023-11-15T16:47:53Z")

</div>

Yep! We have some signal types (e.g. the “SETI Ellipsoid”) that rely on coordinating when+where to look (but are relatively uninformative as to _what_ to search for). Recent overview on this I gave here at UW:

[![](https://img.youtube.com/vi/RPdUBlwJ_sw/maxresdefault.jpg "UW Astrobiology Colloquium: The SETI Ellipsoid") ](https://www.youtube.com/watch?v=RPdUBlwJ_sw&t=439)

So I envision a time-window specific watchlist to look for any alerts that come from ~100 stars in a given month long window. We can calculate that window of time for thousands of stars. If any of them have alerts of any kind, that’s a signal to rapidly follow-up to possible signals (e.g. w/ radio telescopes and spectra)
