gracedb issueshttps://git.ligo.org/lscsoft/gracedb/-/issues2018-11-26T01:13:32Zhttps://git.ligo.org/lscsoft/gracedb/-/issues/88Fully implement public &quot;switch&quot;2018-11-26T01:13:32ZTanner PrestegardFully implement public "switch"Fully implement the settings variable which will allow or not allow unauthenticated access. Should also have unit tests which test this capability.Fully implement the settings variable which will allow or not allow unauthenticated access. Should also have unit tests which test this capability.2018-11-30publicTanner PrestegardTanner Prestegardhttps://git.ligo.org/lscsoft/gracedb/-/issues/75Moving old detections to superevents and making them public2019-04-23T13:40:58ZTanner PrestegardMoving old detections to superevents and making them publicWe want to make old events like GW170817 into superevents and available publicly.
The steps will be:
1. Aggregate the events into superevents
2. Copy over relevant content (logs, files, etc.)
* Metadata: do we need log submitters, timestamps, etc. to match that of the original event? Patrick: No
3. Add new information like samples files which are included for these events on GWOSC.
4. Internal vetting and approval.
5. Public release
Steps 1 and 2 will likely be handled by superevent_manager/gwcelery.
Questions are:
* What kind of timescale are we working on?
* Catalog paper and engineering run are expected near the end of November. Can we get this done on a similar timescale?
* Maybe - need to talk to Tom about AWS/public implementation planWe want to make old events like GW170817 into superevents and available publicly.
The steps will be:
1. Aggregate the events into superevents
2. Copy over relevant content (logs, files, etc.)
* Metadata: do we need log submitters, timestamps, etc. to match that of the original event? Patrick: No
3. Add new information like samples files which are included for these events on GWOSC.
4. Internal vetting and approval.
5. Public release
Steps 1 and 2 will likely be handled by superevent_manager/gwcelery.
Questions are:
* What kind of timescale are we working on?
* Catalog paper and engineering run are expected near the end of November. Can we get this done on a similar timescale?
* Maybe - need to talk to Tom about AWS/public implementation planpublicsupereventsTanner PrestegardTanner Prestegard