-
Notifications
You must be signed in to change notification settings - Fork 0
/
snewsmo_template.tex
146 lines (113 loc) · 6.1 KB
/
snewsmo_template.tex
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
\documentclass{article}
\begin{document}
\title{SNEWS Operational Mode Template Description}
\author{SNEWS Collaboration}
\date{\today}
\maketitle
\section{Introduction}
The purpose of this document is to specify a template for operational
mode documents of the SuperNova Early Warning System (SNEWS).
It is the conviction of the participants that SNEWS should operate
under conditions that are:
\begin{itemize}
\item Documented and available at all times to the participants.
\item Approved by the participants.
\item Consistent with the ``Prompt'', ``Positive'' and ``Private''
objectives of SNEWS.
\end{itemize}
It is also implicit that SNEWS will develop in a series of managed
transitions between operational modes. For instance, new experiments
or new coincidence servers will be added or removed. Each operational
mode will be identified by a number and the date when it came into
effect, and will specify in detail the participants, the coincidence
conditions, the alert classifications, and the procedures for action
in case of different alarm conditions. Major changes ($e.g.$ addition
of an experiment) will increment the first version number, and minor changes
($e.g.$ change in some monitoring responsibility) will increment the
second number of the operation mode version. This document outlines a
template for an operational mode document.
% Approval
One caveat is that any details that would assist individuals in locating
and gaining access to the SNEWS servers, and information that could be
used to simulate SNEWS alerts, will be confined to an appendix which
will not be widely distributed but is nonetheless available to SNEWS
subgroup members.
\section{Operational Mode Template}
\subsection*{Section 1: Participating Experiments}
This section will list all experiments that may send alerts to the
coincidence server(s). It is understood that a temporary lack of
participation of one or more of these listed experiments for hours,
days, or weeks does not constitute a change of operational mode. Any
other change in this list does constitute a change of operational
mode. However the SNEWS collaboration should be notified of long
lasting downtime periods ($\delta t>$1 day), previously scheduled for
maintenance, calibration or other items. The information will be
posted into the downtime web page, available to experiment collaboration
members.
\subsection*{Section 2: Privacy Agreement}
This section will contain a pointer to the current SNEWS privacy
agreement, which defines guidelines for communication
of SNEWS-related information.
\subsection*{Section 3: Client Computer Management}
Client computer management at each local site is the responsibility of
each participant experiment. No specific requirements are formally
imposed on the collaboration members, other than those described in
the privacy agreement. Basic recommendations will however suggested
in this section, to improve the security of the whole system, since the
information passed via socket connection to the SNEWS server(s) is
present on the local machines.
\subsection*{Section 4: Server Computer Management}
The SNEWS server are managed according to memoranda
of understanding with national laboratory or similar sites;
this section will list the currently active coincidence
servers and provide pointers to the currently active memoranda
of understanding. A significant MOU change, or permanent addition
or removal of a coincidence server from the network,
constitutes a change of operational mode.
\subsection*{Section 5: Client-Server Communications}
This section will define individual experiment alarm categories
($e.g.$ TEST, DUBIOUS, GOOD) and packet flags, and will describe the
communications protocol between client and server (encryption
protocol, access check requirements, etc).
\subsection*{Section 6: SNEWS Shift Work}
The SNEWS subgroup members will share SNEWS shift work on a regular
basis. Each SNEWS member will be equipped with communications
equipment, and is responsible 24/7 for response to SNEWS coincidences
(silver or gold), as well as some regular maintenance and monitoring
jobs. This section will outline the shifting mode and designate the
shiftmeister, and will list specific responsibilities of the SNEWS
shifter. This information will be provided in a short and simple
manual, including daily duties, alert procedures and actions, e-mail
and phone numbers of all subgroup members, SNEWS coordinator, and
server sysadmin(s).
\subsection*{Section 7: Coincidence Definition}
This section will define the coincidence conditions for different
SNEWS alert categories ($e.g.$ TEST, SILVER, GOLD).
\subsection*{Section 8: Alert Procedure}
This section will describe in detail the procedure to be followed by
SNEWS members and individual experiments for the case of each type of
coincidence alert. It will specify what information is to be sent as
part of an alert, and to whom. After receipt of this information, if
the information is used either for any scientific purpose or for any
alert communication, the SNEWS origin of the information should be
always clearly cited.
For each alert type, each experimental collaboration
provides a list of e-mails, names and phone numbers, and fixes
the specific notification order and procedure. For instance, an email may
be sent to a particular list, and furthermore a certain set of
people may be notified in a given order by the SNEWS shifter.
This detailed contact information will be included in the appendix.
\subsection*{Section 9: Communication to the Scientific Community}
This section will describe the means of communication
of the alert information to the astronomical community, including
examples of the alert emails to be sent.
This section will also include a description of the alert list management
and details of PGP verification of the emails.
\subsection*{Section 10: Changelog}
This section will summarize the main changes since the previous document
version.
\subsection{Appendix}
The appendix will contain any information which needs to be defined
for the operating mode, but which should be available only
to the SNEWS subgroup, such as the SNEWS datagram packet definition.
\end{document}