Superevents

Adding superevents to GraceDB, including the necessary models, utility functions, and API resources. This has also resulted in changes to the overall configuration and some parts of the events model.

Many models in the events app, like Labels, Tags, EventLogs, etc. were needed in a similar form for superevents. We were able to completely reuse the existing Label and Tag models for superevents. In other cases, we had to abstract the main functionality of the class into an abstract base class and then implement separate models for events and superevents, due to foreign key requirements. This should leave the current functionality of the events models unchanged.

Some portions of the events API have been modified because of one of the following reasons:

• It didn't make sense and was unnecessarily difficult to duplicate for superevents
• It was inefficient or bad

These changes are documented here: https://bugs.ligo.org/redmine/issues/6133

gracedb/templates/superevents/detail.html

@@ -136,14 +136,16 @@
 <table class="superevent">
     <tr>
         <th>Superevent ID</th>
+        <th>Superevent category</th>
         <th>Labels</th>
-        <th>Preferred Event</th>
+        <th>Preferred event</th>
         <th>GW events</th>
         <th>External events</th>
         <th>Links</th>
     </tr>
     <tr>
         <td>{{ superevent.superevent_id }}</td>
+        <td>{{ superevent.get_category_display }}</td>
         <td>{% for labelling in superevent.labelling_set.all %}
             <div onmouseover="tooltip.show(tooltiptext('{{labelling.label.name}}', '{{labelling.creator.username}}', '{{labelling.created|utc}}', '{{labelling.label.description}}'));" onmouseout="tooltip.hide();"  style="color: {{labelling.label.defaultColor}}"><b>{{ labelling.label.name }}</b></div>
             {% endfor %}