gwcelery merge requestshttps://git.ligo.org/emfollow/gwcelery/-/merge_requests2024-02-15T00:29:30Zhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/1389Draft: Use latest GW sky map info in joint alerts; fixes #7512024-02-15T00:29:30ZBrandon PiotrzkowskiDraft: Use latest GW sky map info in joint alerts; fixes #751O4bhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/495WIP: Move DQV label check into public alert criterion2023-06-28T18:32:57ZLeo P. SingerWIP: Move DQV label check into public alert criterionPreviously, the data quality check was re-run by the Orchestrator
whenever an event was added to a superevent. Depending on the
result, the superevent would have been updated. This feedback
between the Orchestrator and the Superevent Man...Previously, the data quality check was re-run by the Orchestrator
whenever an event was added to a superevent. Depending on the
result, the superevent would have been updated. This feedback
between the Orchestrator and the Superevent Manager was race-prone.
Now, the Superevent Manager is responsible for running data quality
checks whenever an event is ingested, and the data quality status
is included in both the public alert condition and the preferred
event sorting key.
Note: merge !502 first.Deep Chatterjeedeep.chatterjee@ligo.orgDeep Chatterjeedeep.chatterjee@ligo.orghttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/669Draft: Produce internal-only GCN Notices for subthreshold events2023-06-28T12:57:44ZLeo P. SingerDraft: Produce internal-only GCN Notices for subthreshold eventsDeep Chatterjeedeep.chatterjee@ligo.orgDeep Chatterjeedeep.chatterjee@ligo.orghttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/885Generate flat-resolution FITS files asynchronously2022-07-26T21:40:18ZLeo P. SingerGenerate flat-resolution FITS files asynchronouslyReport the URL of multi-resolution FITS files in GCN Notices.Report the URL of multi-resolution FITS files in GCN Notices.Review Readiness PresentationLeo P. SingerLeo P. Singerhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/683add gracedb logs for frozen, ready and first gcn2019-12-04T14:58:58ZDeep Chatterjeedeep.chatterjee@ligo.orgadd gracedb logs for frozen, ready and first gcnAdding gracedb log messages before clean upAdding gracedb log messages before clean upLeo P. SingerLeo P. Singerhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/665Remove race-prone subthreshold alert timeout2019-11-15T16:26:53ZLeo P. SingerRemove race-prone subthreshold alert timeout* `is_complete()` is no longer part of the `should_publish()`
criteria, so that advocates are called up via an `ADVREQ`
notification as early as possible.
* The countdown to a preliminary alert has been restored, and
starts as ...* `is_complete()` is no longer part of the `should_publish()`
criteria, so that advocates are called up via an `ADVREQ`
notification as early as possible.
* The countdown to a preliminary alert has been restored, and
starts as soon as an event meets the `is_complete()` criteria.O3bhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/673Remove race-prone subthreshold alert timeout (option 2)2019-11-15T16:26:09ZLeo P. SingerRemove race-prone subthreshold alert timeout (option 2)Slight variation on !665.Slight variation on !665.O3bDeep Chatterjeedeep.chatterjee@ligo.orgDeep Chatterjeedeep.chatterjee@ligo.orghttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/609WIP: Incorporate update circular; Fixes #2222019-09-18T16:38:03ZBrandon PiotrzkowskiWIP: Incorporate update circular; Fixes #222Incorporate the new update type circular so that the emfollowup advocate can create whatever type of update circular they want when sending out a new update GCN notices
To do:
* [x] Add update circular to circulars.py
* [x] Incorp...Incorporate the new update type circular so that the emfollowup advocate can create whatever type of update circular they want when sending out a new update GCN notices
To do:
* [x] Add update circular to circulars.py
* [x] Incorporate in orchestrator.py
* [ ] Incorporate into flask app
* [ ] Fix/build unittests
Flask App Design Goal:
Have check boxes when choosing which files to update in order to choose what the update circular will contain (out of: update skymap, p_asto, EM-bright classification)O3bhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/605WIP: Incorporate update circular; Fixes #2242019-09-17T00:47:12ZBrandon PiotrzkowskiWIP: Incorporate update circular; Fixes #224To do:
* [ ] Add update circular to circulars.py
* [ ] Incorporate in orchestrator.py
* [ ] Incorporate into flask app
* [ ] Fix/build unittestsTo do:
* [ ] Add update circular to circulars.py
* [ ] Incorporate in orchestrator.py
* [ ] Incorporate into flask app
* [ ] Fix/build unittestshttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/592Retry GraceDB errors when applying public tag to sky maps2019-08-29T01:30:47ZLeo P. SingerRetry GraceDB errors when applying public tag to sky mapsRetry any GraceDB API calls that fail when sending an initial or update
alert. This fixes a regression that was introduced in version 0.8.2 that
added several GraceDB API calls that would not have been retried.
As a side effect, the ``p...Retry any GraceDB API calls that fail when sending an initial or update
alert. This fixes a regression that was introduced in version 0.8.2 that
added several GraceDB API calls that would not have been retried.
As a side effect, the ``p_astro.json`` and ``em_bright.json`` files
are not made public. (They have never been one of our documented
data products anyway.)
This will make it easier to fix #211.Release version 0.8.6Deep Chatterjeedeep.chatterjee@ligo.orgDeep Chatterjeedeep.chatterjee@ligo.orghttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/559WIP: Set task priorities proportional to log false alarm rate2019-07-15T18:56:35ZLeo P. SingerWIP: Set task priorities proportional to log false alarm rateSet Celery task priorities proportional to the log of the false
alarm rate for resource-intensive CBC tasks. This should decrease
the latency of the preliminary alert in cases where a large number
of events are uploaded to the superev...Set Celery task priorities proportional to the log of the false
alarm rate for resource-intensive CBC tasks. This should decrease
the latency of the preliminary alert in cases where a large number
of events are uploaded to the superevent.Leo P. SingerLeo P. Singerhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/546Publishability triggers preliminary alert2019-06-14T20:38:23ZLeo P. SingerPublishability triggers preliminary alertTrigger a preliminary alert for a superevent upon the first time
that the preferred event is set to an event that meets the public
alert criterion. Remove the preliminary alert timeout because it
is no longer necessary to wait until t...Trigger a preliminary alert for a superevent upon the first time
that the preferred event is set to an event that meets the public
alert criterion. Remove the preliminary alert timeout because it
is no longer necessary to wait until the preferred event
stabilizes.
This fixes a longstanding issue that has prevented automated
preliminary alerts from being sent so far. The preferred event
*at the instant that the timeout ended* did not meet the public
alert criterion, but a preferred event that was selected some tens
of seconds later did.
Note: merge !495 first.
![preliminary_alert_diagram](/uploads/f3351dcdfe8ad410bd44c1aa14b59870/preliminary_alert_diagram.png)Release version 0.6.3https://git.ligo.org/emfollow/gwcelery/-/merge_requests/473Use consistent criteria for public alerts and preferred events2019-05-01T14:35:55ZLeo P. SingerUse consistent criteria for public alerts and preferred eventsWe define a total ordering over events in order to select the
preferred event. The ordering is defined through a key function
that returns a tuple, the first element of which is the boolean
value indicating whether a public alert would b...We define a total ordering over events in order to select the
preferred event. The ordering is defined through a key function
that returns a tuple, the first element of which is the boolean
value indicating whether a public alert would be sent.
This fixes a whole class of bugs where the choice of the preferred
event could inhibit sending a public alert. Such bugs are now
impossible, by construction.
Fixes !471.https://git.ligo.org/emfollow/gwcelery/-/merge_requests/379add logic to disable preliminary notices for single IFO superevents2019-04-03T14:58:03ZDeep Chatterjeedeep.chatterjee@ligo.orgadd logic to disable preliminary notices for single IFO supereventsPreliminary notices will be disabled for single interferometer triggers. This is configured by mentioning pipeline names for which we want to disable in `disable_single_ifo_alert`
CC @erik\-katsavounidisPreliminary notices will be disabled for single interferometer triggers. This is configured by mentioning pipeline names for which we want to disable in `disable_single_ifo_alert`
CC @erik\-katsavounidisO3 StartLeo P. SingerLeo P. Singerhttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/326added a wallclock time to livetime conversion factor for far2019-02-08T17:36:06ZDeep Chatterjeedeep.chatterjee@ligo.orgadded a wallclock time to livetime conversion factor for far- pipeline specific wall_2_livetime_factor config variable added
- this factor is multiplied to the event FAR for uniformity across
pipelines.
CC @leo\-singer- pipeline specific wall_2_livetime_factor config variable added
- this factor is multiplied to the event FAR for uniformity across
pipelines.
CC @leo\-singerErik KatsavounidisErik Katsavounidishttps://git.ligo.org/emfollow/gwcelery/-/merge_requests/309fixing KeyError mention in #622018-12-16T10:19:43ZDeep Chatterjeedeep.chatterjee@ligo.orgfixing KeyError mention in #62- event information not available in superevent packet
- getting information of event added from recent event logs
See sentry [message](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/178/) for the details
CC @leo\-singer- event information not available in superevent packet
- getting information of event added from recent event logs
See sentry [message](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/178/) for the details
CC @leo\-singerPatrick BradyPatrick Brady