Table 2
Partner instrument follow-up information.
| Name | Run | Tiles per trigger | Target alerts per week | Triggers imaged |
|
|
||||
| Palomar Transient Factory | Autumn | 10 | 1/3 | 1 |
| Pi of the Sky | Autumn | 1 | 1 | 1 |
| QUEST | Both | 3 | 1 | 5 |
| ROTSE III | Autumn | 1 | 1 | 5 |
| SkyMapper | Autumn | ~9 | 1 | 3 |
| TAROT | Both | 1 | 1 | 3 |
| Zadko Telescope | Autumn | 5 | 1 | 2 |
| Liverpool Telescope | Autumn | 1 | 1 | 1 |
| LOFAR | Autumn | 1 | 1 | 2 |
| Swift | Both | 5 | 1/4 | 2 |
Notes. Follow-up information for instruments involved in the search. Each instrument participated in either the autumn run, or both the winter and autumn runs. The column marked “Tiles per Trigger” shows how many different field locations the instrument attempted to observe for each accepted GW event candidate. The “Target Alerts Per Week” column shows that alerts were sent to PTF and Swift at a lower rate than the other observatories. The final column shows the number of GW event candidates for which each instrument collected data.
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.