GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2022-08-03T19:04:41Zhttps://git.ligo.org/computing/gracedb/server/-/issues/97Rolling deletion of Test events and superevents2022-08-03T19:04:41ZTanner PrestegardRolling deletion of Test events and supereventsTest events currently make up 46% of the events in the database and take up 25% of the storage. We should not be preserving Test events indefinitely (on principle) and it could help speed things up a bit. I would like to establish a ni...Test events currently make up 46% of the events in the database and take up 25% of the storage. We should not be preserving Test events indefinitely (on principle) and it could help speed things up a bit. I would like to establish a nightly cron job that deletes events and superevents older than 3 months or so.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/63Fix the way instruments are stored for events2022-08-03T18:49:25ZTanner PrestegardFix the way instruments are stored for eventsCreated August 16, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5694)
Instruments are currently associated with events by a string like "H1,L1" or "H1,L1,V1". This is an ineffective way of doing it and prevents effici...Created August 16, 2017. Copied from redmine (https://bugs.ligo.org/redmine/issues/5694)
Instruments are currently associated with events by a string like "H1,L1" or "H1,L1,V1". This is an ineffective way of doing it and prevents efficient instrument-based queries.
We should create an instruments model and just have a many-to-many relationship with events (may need to create a go-between like "labelling").
I think there is also an 'ifos' variable: we should resolve the redundancy issue if that's the case.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/16Refurbish events API2022-08-03T18:04:27ZTanner PrestegardRefurbish events APIThe events API needs to be redone for a few reasons:
1. Incomplete validation and error handling
2. Difficult to implement permissions - redoing this would make #15 much easier
3. Many redundancies and inefficiencies
4. Doesn't make...The events API needs to be redone for a few reasons:
1. Incomplete validation and error handling
2. Difficult to implement permissions - redoing this would make #15 much easier
3. Many redundancies and inefficiencies
4. Doesn't make use of the builtin features in django-rest-framework
One possible difficulty is that some changes might require corresponding client changes, so we might run into yet another case where we have another server-client incompatibility.Backlog