-
Notifications
You must be signed in to change notification settings - Fork 10
/
broker_task_force_work_plan.html
158 lines (119 loc) · 9.58 KB
/
broker_task_force_work_plan.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
<!DOCTYPE HTML>
<html>
<head>
<title>LSST-TVS</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<!--[if lte IE 8]><script src="assets/js/ie/html5shiv.js"></script><![endif]-->
<link rel="stylesheet" href="assets/css/main.css" />
<!--[if lte IE 8]><link rel="stylesheet" href="assets/css/ie8.css" /><![endif]-->
<!--[if lte IE 9]><link rel="stylesheet" href="assets/css/ie9.css" /><![endif]-->
</head>
<body>
<!-- Header -->
<div id="header">
<div class="top">
<!-- Logo -->
<div id="logo">
<span class="image avatar48"><img src="images/MEDLogoBLK.jpg"subg alt="" /></span>
<h1 id="title"> Transients and Variable Stars </h1>
<p>LSST Science Collaboration</p>
</div>
<!-- Nav -->
<nav id="nav">
<!--
Prologue's nav expects links in one of two formats:
1. Hash link (scrolls to a different section within the page)
<li><a href="#foobar" id="foobar-link" class="icon fa-whatever-icon-you-want skel-layers-ignoreHref"><span class="label">Foobar</span></a></li>
2. Standard link (sends the user to another page/site)
<li><a href="http://foobar.tld" id="foobar-link" class="icon fa-whatever-icon-you-want"><span class="label">Foobar</span></a></li>
-->
<ul>
<li><a href="https://lsst-tvssc.github.io/index.html#top" id="top-link" class="skel-layers-ignoreHref"><span class="icon fa-home">Intro</span></a></li>
<li><a href="https://lsst-tvssc.github.io/index.html#subgroups" id="portfolio-link" class="skel-layers-ignoreHref"><span class="icon fa-th">Subgroups</span></a></li>
<li><a href="https://lsst-tvssc.github.io/index.html#members" id="members-link" class="skel-layers-ignoreHref"><span class="icon fa-user">Members and roles</span></a></li>
<li><a href="https://lsst-tvssc.github.io/index.html#taskForces" id="portfolio-link" class="skel-layers-ignoreHref"><span class="icon fa-th">Task Forces</span></a></li>
<li><a href="https://lsst-tvssc.github.io/index.html#events" id="members-link" class="skel-layers-ignoreHref"><span class="icon fa-calendar">Events</span></a></li>
<li><a href="https://tvs.science.lsst.org/apply" id="application-link" class="skel-layers-ignoreHref"><span class="icon fa-edit">Become a member</span></a></li>
<li><a href="https://lsst-tvssc.github.io/index.html#contact" id="contact-link" class="skel-layers-ignoreHref"><span class="icon fa-envelope">Contact us</span></a></li>
</ul>
</nav>
</div>
<div class="bottom">
<!-- Social Icons -->
<ul class="icons">
<li><a href="#" class="icon fa-twitter"><span class="label">Twitter</span></a></li>
<li><a href="https://github.com/LSST-TVSSC" class="icon fa-github"><span class="label">Github</span></a></li>
<li><a href="#contact" class="icon fa-envelope"><span class="label">Email</span></a></li>
</ul>
</div>
</div>
<!-- Main -->
<div id="main">
<!-- Intro -->
<section id="top" class="one dark cover">
<div class="container">
<header>
<h2 class="alt">these webpages are a work in progres... .</h2>
<p>In the meantime you can find out about us on the <a href="https://tvs.science.lsst.org/">LSST TVS wiki</a>
</header>
</div>
</section>
<section id="about" class="">
<div style="margin-left:45px">
<h2 style="color:#4682b4">TVS Task Force </h2>
<h3 style="font-weight: bold">Characterize the functionality needed from a community-broker interface</h3>
<h3>Work Plan</h3>
<table><tr>
<td><h3><a href="https://github.com/LSST-TVSSC/broker-requirements-survey/blob/master/tvs_broker_requirements_report.pdf">2018 Survey Results</a></h3></td>
<td><h3><a href="https://lsst-tvssc.github.io/how_fast_do_you_need_alerts.html">How fast do you <i>really</i> need alerts?</a></h3></td>
</tr></table>
<h4 style="color:#4682b4" align="left"> Members:</h4>
<table width=100px border=1px>
<tr><td align="left">Francisco Förster Buron, CMM-UChile / MAS</td><td align="left"></td></tr>
<tr><td align="left">Suvi Gezari, University of Maryland </td><td align="left"></td></tr>
<tr><td align="left">Melissa Graham, University of Washington/LSST </td><td align="left"></td></tr>
<tr><td align="left">Ashish Mahabal, Caltech </td><td></td></tr>
<tr><td align="left">Gautham Narayan, STScI</td><td align="left">Questionnaire team</td></tr>
<tr><td align="left"><a href="mailto:markus.rabus@gmail.com">Markus Rabus, PUC, Chile</a></td><td align="left">Spokesperson</td></tr>
<tr><td align="left">Keivan Stassun, Vanderbilt University</td><td align="left">Questionnaire team</td></tr>
<tr><td align="left">Paula Szkody, University of Washington</td><td align="left">Questionnaire team</td></tr>
<tr><td align="left">Rachel Street, Las Cumbres Observatory</td><td align="left"> Chair, Questionnaire team</td></tr>
<tr><td align="left">Stephen Smartt, Queen’s University Belfast</td><td></td></tr>
<tr><td align="left">Ken Smith, Queen’s University Belfast</td><td align="left"></td></tr>
</table>
<h2 style="color:#4682b4">Context</h2>
<p>The LSST Data Management (DM) software will deliver an alert package for every object in each image which exhibits some photometric or positional change. The scale of the survey leads us to anticipate millions of alerts per night and hence a computational challenge for astronomers to identify targets of specific interest for their science. In this context, we refer to a ‘broker’ as software which receives alert information, associates it with other data, performs classification functions according to numerous algorithms and criteria, and stores the information in a database. Brokers may issue secondary alerts, and may provide interfaces to enable users to sort targets and alters according to their own preferences. These users may be individual scientists, teams, or additional brokers working at a level of finer detail. They may also be accessed by many instances of Target/Observation Manager software, which are designed to prioritizing targets for a specific science goal, request follow-up observations, tracking progress and analyze the results. </p>
<p>While some astronomers are accustomed to responding to alerts and conducting ‘reactive’ follow-up observations in real-time, for many scientists this mode of operation is unfamiliar, making it difficult for them to envision how they will exploit LSST. </p>
<p>Meanwhile, substantial development of broker facilities is ongoing, including ANTARES (NOAO), Lasair (LSST:UK), ALeRCE (Chile). To maximize the science return from LSST as a whole, the user interfaces to these brokers need to be carefully designed to address the needs of the community. </p>
<h2 style="color:#4682b4">Task Force (TF) Goals</h2>
<div style="display: inline-block; text-align: left;">
<ul margin-left: 1em;>
<li>Stimulate scientists from all fields in astronomy to think through how they will extract targets of interest from LSST, what information and data products they will require at each stage, timescales of delivery and modes of interaction with brokers. </li>
<li>Derive and document Scientific and Functional & Performance requirements</li>
</ul>
</div>
<h2 style="color:#4682b4">Work Plan and Deliverables</h2>
<div style="display: inline-block; text-align: left;">
<a href="broker_task_force_gantt_chart_v1.0.pdf">Broker Task Force Gantt Chart</a><br>
<a href="images/BrokerTFGantt.png"><img width=100% src="images/BrokerTFGantt.png"></a>
<li>Develop short introductory document to describe and publicize how the ‘broker ecosystem’ is envisioned to work.
Develop questionnaire to be circulated to all LSST-SC members designed to stimulate scientists of all fields to think in detail about how they will conduct their science and hence what they will need from a broker.</li>
<li>Conduct the survey and collate the results</li>
<li>Develop Science Requirements document based on the results of the survey.</li>
</div>
<br><br>
<table padding=15px>
<tr><th style="color:#4682b4" align="right">Deadline</th><th align="left" style="color:#4682b4">Milestone</th>
<tr><td align="right">March 9, 2018</td><td align="left">Deliver completed broker ecosystem document</td></tr>
<tr><td align="right">March 9, 2018</td><td align="left">Deliver completed survey questionnaire</td></tr>
<tr><td align="right">April 20, 2018</td><td align="left">Completed summary of survey responses and statistics</td></tr>
<tr><td align="right">May 18, 2018</td><td align="left">Complete v1.0 of Science Requirements document</td></tr>
<tr><td align="right">June 4-8, 2018</td><td align="left">Review v1.0 Science Requirements with broker developers, discussion session at TVS workshop</td></tr>
<tr><td align="right">July 6, 2018</td><td align="left">Complete v2.0 Science Requirements document</td></tr>
</table>
</div>
</section>
</div>
</body>
</html>