X-Pipeline or just
X has been floating around in GraceDB since way before I've been on this project, but has never uploaded an event. I was attempting to clean up event logic back in mid 2020, and so I added
Omega pipelines to a list of pipelines that were being phased out, and returned a warning message if a user attempted to upload an event to that pipeline. Not that it would have worked anyway, because the logic to ingest X-pipeline event files had never actually been implemented and likely would have returned an error.
I received a request over mattermost to revive the pipeline.
Before proceeding with this, I need from @amber-stuver:
- An example event upload. I don't know the output file format (xml? json?) or what fields that are in the file should be stored in the database. I can look it over as a first step to compare to other event types that are in GraceDB, but I need the file first and foremost. It can be attached to this ticket.
- What kind of search type is it? Right now, GraceDB ingests events from
Multiburstsearches, etc. If
Xfits into one of those categories, storing event data and constructing the view and
RESTresponse is simpler. But this will make more sense when I get the example upload.
- Who is going to be uploading and populating the pipeline? If it's individual users, I need just your
@LIGO.orgemail address. Or, if there is a robot account that is uploading, please apply for a cert from https://robots.ligo.org/ and then I'll add it as an uploader.
Once I get the example upload and the other information that I need, the steps I need to do are:
Xfrom the depreciated pipelines list.
- Add logic to
view_logic.pyto read in
- Determine views for
Xevents, add it to settings.
- Add uploader permissions for the pipeline
- Test event uploads, ingestion into the database, and webpage views.
- Make appropriate LVAlert topics for
Then I'll have to push a server code change and deploy it.
Drop any questions or sample files you have here and I'll get back to you.