Add new required attributes for events
Created on June 26, 2018. Copied from redmine (https://bugs.ligo.org/redmine/issues/6169)
From the emfollow design document, section 4.1.3:
Each trigger generated by a search should be submitted to GraceDb. In addition to event information specific to each search, such searches will specify
the tag/version of code used by the search,
the version of calibrated h(t) processed,
which low-latency DQ flags were applied,
whether the alert corresponds to a hardware injection or not,
whether the alert was generated online or offline,
the instruments from which h(t) was actually used to estimate the trigger’s significance
an estimate of the False Alarm Rate normalized to the livetime for the set of instruments specified (i.e.: joint livetime for a LHO-LLO search). If searches do not provide all this information at event-creation time, GraceDb should reject the new event and should not create a new entry in the database. Some of these already exist (offline flag, hardware injection (should be specified by applying INJ label), instruments, FAR), but we may need to enforce that they are set (and set with something reasonable). At first glance, we will have to add the following fields to the Event model:
code_version: CharField
hoft_verion: CharField
dq_flags: CharField (comma-separated string?) Depends on how these will be uploaded, I don't think we want to add a whole table of DQ flags to GraceDB