userguide merge requestshttps://git.ligo.org/emfollow/userguide/-/merge_requests2024-03-29T00:13:50Zhttps://git.ligo.org/emfollow/userguide/-/merge_requests/261Add additional RAVEN citation; fixes #3472024-03-29T00:13:50ZBrandon PiotrzkowskiAdd additional RAVEN citation; fixes #347GWCelery v2.4.1 Releasehttps://git.ligo.org/emfollow/userguide/-/merge_requests/260Probability of a BNS merger in O4b2024-03-29T07:25:11ZOm Sharan SalafiaProbability of a BNS merger in O4bOm Sharan SalafiaOm Sharan Salafiahttps://git.ligo.org/emfollow/userguide/-/merge_requests/256Resolve "Adding mly-pipeline in the userguide"2024-03-27T14:10:14ZVASILEIOS SKLIRISResolve "Adding mly-pipeline in the userguide"Closes #353Closes #353VASILEIOS SKLIRISVASILEIOS SKLIRIShttps://git.ligo.org/emfollow/userguide/-/merge_requests/253include rapidpe patsro in second preliminary and initial notice2024-03-29T00:03:30ZVINAYA VALSANinclude rapidpe patsro in second preliminary and initial noticehttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/1330 modifies the alert workflows to include RapidPE-RIFT pastro numbers in the second preliminary and initial notice.
This MR ins userguide is to explain these changes in gwcelery.https://git.ligo.org/emfollow/gwcelery/-/merge_requests/1330 modifies the alert workflows to include RapidPE-RIFT pastro numbers in the second preliminary and initial notice.
This MR ins userguide is to explain these changes in gwcelery.Cody MessickCody Messickhttps://git.ligo.org/emfollow/userguide/-/merge_requests/247Main2023-11-01T13:38:47ZWeizmann KIENDREBEOGOMainThe purpose of this Merge Requests is to incorporate the observing scenarios results of the **HL** configuration, focused exclusively on the use of LIGO detectors and applicable exclusively to the O4 run.
This enables us to adopt a mo...The purpose of this Merge Requests is to incorporate the observing scenarios results of the **HL** configuration, focused exclusively on the use of LIGO detectors and applicable exclusively to the O4 run.
This enables us to adopt a more comprehensive perspective, offering estimates depending on either the duty of two LIGO (HL) detectors or the complete set of the four detectors (HLVK), as originally envisioned in the initial scenarios.Leo P. SingerMichael William CoughlinLeo P. Singerhttps://git.ligo.org/emfollow/userguide/-/merge_requests/242Information for SSM public alerts2024-03-22T13:36:28ZDivya SinghInformation for SSM public alertsThis MR is a work in progress. It adds information about the low-latency SSM searches by GstLAL and MBTA in O4 along with information about alert contents for events from these searches. All comments welcome.This MR is a work in progress. It adds information about the low-latency SSM searches by GstLAL and MBTA in O4 along with information about alert contents for events from these searches. All comments welcome.Ryan MageeDivya SinghViola SordiniRyan Mageehttps://git.ligo.org/emfollow/userguide/-/merge_requests/234Rewriting FAR section to clarify trial factor usage2024-03-27T15:03:32ZRoberto DePietriRewriting FAR section to clarify trial factor usageThe external community shows some misunderstanding of the trial factor. This rewriting tries to clarify the concept to astronomers, reversing the order of the discussion.
It also updates the trial factors to the O4b run.
Partially solv...The external community shows some misunderstanding of the trial factor. This rewriting tries to clarify the concept to astronomers, reversing the order of the discussion.
It also updates the trial factors to the O4b run.
Partially solve: https://git.ligo.org/emfollow/userguide/-/issues/355https://git.ligo.org/emfollow/userguide/-/merge_requests/233Draft: Add note about the origin of public skymaps2023-07-04T14:41:10ZJacopo TissinoDraft: Add note about the origin of public skymapsSpecifically, writing about the number of skymaps per event
and their meaning - two coming from the preliminary notices, why they might be different,
and the later one.
What I wrote comes from the answer to my question on the EMFollow c...Specifically, writing about the number of skymaps per event
and their meaning - two coming from the preliminary notices, why they might be different,
and the later one.
What I wrote comes from the answer to my question on the EMFollow channel by @peter-shawhan,
@geoffrey.mo, @deep.chatterjee.
I believe this is not fully spelled out anywhere else, but even if it could be pieced
together the page to which I added the note is the one where, as a user, I would expect to find
this information.
The pipelines for the userguide are currently failing - for one, "skymaps" is not an English word apparently,
and indeed I don't see it being used elsewhere in the user guide. Is it jargon? Should it not be used?
Some more errors are also appearing but I think they're not my fault - looking at the PDF
output the links and formatting in the note I added seem to be working.https://git.ligo.org/emfollow/userguide/-/merge_requests/62Add distance fields to VOEvents2022-08-18T21:12:01ZLeo P. SingerAdd distance fields to VOEvents