GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2024-03-10T16:42:58Zhttps://git.ligo.org/computing/gracedb/server/-/issues/255Add additional pipelines/searches for external events2024-03-10T16:42:58ZBrandon PiotrzkowskiAdd additional pipelines/searches for external eventsThere are a couple new types of external events that could be potentially ingested by gwcelery in O4, requiring the following tasks in advance:
- [ ] Add pipeline=`KamLAND` as part of https://git.ligo.org/emfollow/gwcelery/-/issues/72 (...There are a couple new types of external events that could be potentially ingested by gwcelery in O4, requiring the following tasks in advance:
- [ ] Add pipeline=`KamLAND` as part of https://git.ligo.org/emfollow/gwcelery/-/issues/72 (should use a new field search=`PreSN` since these should be treated distinctly from `Supernova`)
- [x] Add pipeline=`CHIME` and search=`FRB` (fast radio burst) as part of https://git.ligo.org/emfollow/gwcelery/-/issues/519, needed as well by the GRB/FRB/Magnetar group
- [x] Add pipeline=`SVOM` as part of https://git.ligo.org/emfollow/gwcelery/-/issues/539, which should use the already existing `search='GRB'`
- [x] Add pipeline=`IceCube` as part of https://git.ligo.org/emfollow/gwcelery/-/issues/750 and would need to add a new field such as `search='HEN'`
At the moment I don't have templates to instruct ingest either of these alert types, so that will likely have to be solved in a separate issue (in gwcelery temporarily and GraceDB in the long-run).
**Edit, Feb 20, 2024**
@brandon.piotrzkowski @andrew.toivonen @michael-coughlin I'd like to get a little more organized in handling these issues since there are a couple of requests floating around on this one ticket. Could you please complete the table below with the information that is missing. In particular, what is the input file upload format for each of these new pipelines, are modifications to existing upload formats needed, and then provide a link to a sample file (even if it means uploading it manually to this issue).
Also, could you work amongst yourselves to determine what the priority are for these (1, 2, 3, etc). This should be based on your assessment of each of the new pipelines' technical readiness, ie, the file format is settled and gwcelery is ready to test but you're just waiting on gracedb changes.
| Is Complete? | Pipeline Name | Search(es) Name | Input File Format | Changes needed? | Link to file | Priority |
| ------ | ------ | ------ | ------ | ------ | ------ | ------ |
| :x: | `KamLAND` | `PreSN` | unknown | unknown | unknown | 3 |
| :white_check_mark: | `CHIME` | `FRB` | `VOEvent` | no | n/a | n/a |
| :white_check_mark: | `SVOM` | `GRB` | `JSON` for now (can convert to `VOEvent` in `gwcelery` until they send in that format) | Ingestion via GraceDB (`VOEvent` for now but eventually `JSON`) | [`VOEvent` available](https://git.ligo.org/emfollow/gwcelery/uploads/786f205addb0045b18c96e8843f3af6f/sb23041100_eclairs-wakeup_2.xml) but no `JSON` yet | 2 |
| :x: | `IceCube` | `HEN` | `VOEvent` | Ingestion via GraceDB | [`Bronze`](https://git.ligo.org/emfollow/gwcelery/-/blob/0bcd7e638d220629d504dc66c7d5fd43cdd34d1c/gwcelery/tests/data/icecube_bronze_neutrino.xml) [`Gold`](https://git.ligo.org/emfollow/gwcelery/-/blob/0bcd7e638d220629d504dc66c7d5fd43cdd34d1c/gwcelery/tests/data/icecube_gold_neutrino.xml) | 1 |O4bhttps://git.ligo.org/computing/gracedb/server/-/issues/307Add ability to disable alerts from (pipeline, searches) combinations2023-05-23T16:20:45ZTito Dal CantonAdd ability to disable alerts from (pipeline, searches) combinationsFollowup from the semi-regular RRT call of Tuesday May 23.
It seems we currently have the ability to disable alerts from individual pipelines, but not from (pipeline, search) combinations. I would like to request the latter ability as w...Followup from the semi-regular RRT call of Tuesday May 23.
It seems we currently have the ability to disable alerts from individual pipelines, but not from (pipeline, search) combinations. I would like to request the latter ability as well. The use case is that we could in principle have problems from e.g. PyCBC Live early-warning, but not from PyCBC Live full-bandwidth.O4