Review v2
-
main page is a bit austere, do you think it is good to have a nice MM picture ? or pictures from the three interferometers ? -
if it is for the public maybe use : LHO, LLO, Virgo --> LIGO-Hanford LIGO-Livingston
Getting starting
-
Getting Started Checklist (for me it looks not very clear but I am not native english) --> or prerequisite or Before started -
Subscribe to GCN Circulars --> Subscribe to Gamma-ray Coordinates Network (GCN) circulars -
to share important announcements and solicit input --> to share important announcements, telecons and exchange with the astronomical community ?
Observing Capabilities
-
During both Engineering Runs, the detector configuration and analysis software will be changing frequently. Consequently, [during the Engineering Runs] --> remove -
Table --> can we center those numbers ? -
We expect 1–50 BNS events --> 0 - 10 BNS I think ... -
Also we need to add the BBH rate, "BH rate will dominate, possibly by more than an order of magnitude, up to few per week to one per month" -
Also NSBH range, probability to have one event at least
Procedures
-
I like the flowchart for sure but should be bigger because the font is too small. Do you want to make bigger letters ?
Online pipelines
-
We need to check with GSTLAL, CWB, MBTA, OLIB experts the text -
Still need RAVEN -
some words about single events ?
Localization and Parameter Estimation
-
LALinference, I suggest to add that I takes few hours to have the results to make a distinction with Bayestar
Superevents
- It seems there is a wish not to mention the OPA threshold : 90 % purity for CBC and 1/yr for burst
Candidate vetting
-
by a rapid response team composed by commissioning, computing, and calibration experts from each of the detector sites, pipeline experts, detector characterization experts, and electromagnetic follow-up advocates.
**Content
-
I personally think a luminosity distance should be explicitly mentionned in the notices -
"If the estimated FAR is less than (100yr)−1, then the Circular will simply describe the event as “highly significant.”" --> we need to remove this
Edited by Leo P. Singer