WIP: Add RAVEN VOEvent variant

• Add new fields to the VOEvent model here
• Add processing of these fields to the superevents API here, including validation
• Add processing and validation of these fields to the events API here
• Add new fields to the VOEvent files here
• Determine which external event needs to be included in the VOEvent
• Load in external event

marked the checklist item Add new fields to the VOEvent model here as completed

changed the description

changed target branch from master to python3

added 52 commits

• 7a5ee40b...799b051d - 51 commits from branch lscsoft:python3
• 187ebd97 - Merge branch 'python3' of https://git.ligo.org/lscsoft/gracedb into ravenvoevent

Compare with previous version

@tanner.prestegard sorry I'm late on this (on your last day :( ). Going to try to do as much today as I can. Let me know if you see anything particularly abhorrent in the code.

added 1 commit

• e71c485f - Add processing to the superevent API

Compare with previous version

added 1 commit

• 6fb2ca6c - Add processing and validation in the API

Compare with previous version

marked the checklist item Add processing and validation of these fields to the events API here as completed

marked the checklist item Add processing of these fields to the superevents API here, including validation as completed

changed the description

added 1 commit

• c39c518d - Fix bug accidently introduced

Compare with previous version

added 1 commit

• 72a4955d - Question on getting data

Compare with previous version

I'm running into the issue that you brought up earlier @tanner.prestegard and that I was worried about: how exactly do we choose which external event to grab? Well we want the first one, that with the superevent, is publishable but there's no obvious way to know which at this step. I see a few possible solutions:

1. Pass the external event ID as an argument when calling the VOEvent to be created in gwcelery
2. Create a field within a superevent that determines which external event (or events) pass coincidence threshold that is updated in gwcelery
3. Calculate which events pass coincidence threshold in gwcelery (bad because this would introduce a circular dependency on gwcelery.)

Follow-up to this: how do we get the external event here? It seems we need to give the superevent a property (say event.ext_event) with the external event dictionary prior to this, which I don't know exactly where or how to do this best.

changed this line in version 9 of the diff

changed the description

added 12 commits

• 72a4955d...9adb9cb0 - 7 commits from branch lscsoft:python3
• cf30552f - Add RAVEN VOEvent variant
• 239264fb - Add processing to the superevent API
• ffa35b74 - Add processing and validation in the API
• 75380038 - Fix bug accidently introduced
• 9bf7792d - Question on getting data

Compare with previous version

added 8 commits

• 78c93144 - Add RAVEN VOEvent variant
• e2b06cb4 - Add processing to the superevent API
• fd83907e - Add processing and validation in the API
• 2f9d5221 - Fix bug accidently introduced
• aec2feb1 - Question on getting data
• b6eb2c42 - adding raven voevent fields
• b9444798 - fixed raven_coinc
• 0fefe7af - Build xml file from RAVEN entries

Compare with previous version

added 1 commit

• 08457eca - Build xml file from RAVEN entries

Compare with previous version

marked the checklist item Add new fields to the VOEvent files here as completed

marked the checklist item Determine which external event needs to be included in the VOEvent as completed

changed the description

merged