Commit 73de4f7f authored by Leo Pound Singer's avatar Leo Pound Singer Committed by Leo Pound Singer

Rename "Procedures" to "Data Analysis"

Also reorder the subsections to better reflect the sequence of the
steps of the pipeline.

Fixes #112.
parent 75944c67
Procedures
==========
Data Analysis
=============
In this section we describe the different online searches looking for GW
signals. When multiple candidates from different pipelines are close enough
together in time, they will be considered as originating from the same physical
event and will be grouped into a single :doc:`superevent <superevents>`. See
the following pages for technical details.
signals, the selection and vetting of candidates, and parameter estimation
analysis.
When multiple candidates from different pipelines are close enough together in
time, they will be considered as originating from the same physical event and
will be grouped into a single :doc:`superevent <superevents>`. See the
following pages for technical details.
.. toctree::
:maxdepth: 1
searches
parameter_estimation
superevents
inference
vetting
parameter_estimation
inference
The timeline for distribution of alerts is described below.
......
......@@ -23,7 +23,7 @@ Poisson processes. A source-dependent weighting of matched-filter templates is
used to compute the mean values of expected counts associated with each of
these five categories. The mean values are updated weekly based on observed
matched-filter count rates. They are then used to predict the category for new
triggers uploaded by :doc:`search pipelines </procedures/searches>`.
triggers uploaded by :doc:`search pipelines </analysis/searches>`.
For details, see [#Pastro]_, especially Section II E. and Equation 18 therein.
......
......@@ -6,7 +6,7 @@ multiple search pipelines. Each superevent is intended to represent a single
astrophysical event.
A superevent consists of one or more event candidates, possibly from
:doc:`different pipelines </procedures/searches>`, that are neighbors in time.
:doc:`different pipelines </analysis/searches>`, that are neighbors in time.
At any given time, one event belonging to the superevent is identified as the
*preferred event*. The superevent inherits properties from the preferred event
such as time, significance, sky localization, and classification.
......@@ -24,7 +24,7 @@ event is decided by applying the following rules, in order:
1. An event detected in multiple interferometers is preferred over an
event from a single interferometer.
2. An event from modeled :term:`CBC` searches are preferred over an event from
unmodeled Burst searches (see :doc:`Searches </procedures/searches>` for
unmodeled Burst searches (see :doc:`Searches </analysis/searches>` for
details on search pipelines).
3. In the case of multiple CBC events, the event with the highest :term:`SNR`
is preferred. In the case of multiple Burst events, the event with the
......
......@@ -10,7 +10,11 @@ Version 9 (unreleased)
.. rubric:: Observing Capabilities
.. rubric:: Procedures
.. rubric:: Data Analysis
* Renamed this section from "Procedures" to "Data Analysis" and reordered its
subsections to better reflect the chronological order of the steps of the
analysis.
.. rubric:: Alert Contents
......
......@@ -25,11 +25,10 @@ automated data quality checks, but it may later be :ref:`retracted
this stage.
An **Initial GCN Notice** is issued after human vetting (see
:doc:`/procedures/vetting`). If the signal does not pass human vetting (e.g.,
it is a glitch), then instead of an initial alert there will be a retraction_.
The initial alert is also accompanied by a GCN Circular which should be
considered as the first formal publication of the candidate and can be cited as
such.
:doc:`/analysis/vetting`). If the signal does not pass human vetting (e.g., it
is a glitch), then instead of an initial alert there will be a retraction_. The
initial alert is also accompanied by a GCN Circular which should be considered
as the first formal publication of the candidate and can be cited as such.
An **Update GCN Notice** is issued whenever further analysis leads to improved
estimates of the sky localization, significance, or classification. There
......@@ -119,7 +118,7 @@ such as :samp:`MS181101abc`. A GraceDB ID has three parts:
* Prefix: ``S`` for normal candidates and ``MS`` or ``TS`` for mock or test
events respectively. The S stands for
:doc:`superevent </procedures/superevents>`.
:doc:`superevent </analysis/superevents>`.
* Date: The six-digit UTC date of the event consisting of a two-digit year,
month, and day of month.
......@@ -322,8 +321,8 @@ dependent to some extent: the Classification section takes into consideration
prior knowledge of astrophysical compact binary merger rates from previous
LIGO/Virgo observations, and both the Classification and Properties sections
depend on details of neutron star physics (e.g. maximum NS mass, equation of
state). See the earlier :doc:`procedures </procedures/inference>` for
implementation details.
state). See the earlier subsection of the :doc:`Data Analysis
</analysis/inference>` section for implementation details.
Circular Contents
-----------------
......
......@@ -41,7 +41,7 @@ Contents
quickstart
capabilities
procedures/index
analysis/index
content
tutorial/index
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment