GraceDB Server issueshttps://git.ligo.org/computing/gracedb/server/-/issues2022-08-03T19:08:02Zhttps://git.ligo.org/computing/gracedb/server/-/issues/105Add GPS time to log entries2022-08-03T19:08:02ZGeoffrey MoAdd GPS time to log entriesHaving the option to show GPS Time (in addition to the existing LHO, LLO, Virgo, UTC times) to log entries would make by-inspection latency calculations much easier. The option already exists for submission time, so probably isn't too di...Having the option to show GPS Time (in addition to the existing LHO, LLO, Virgo, UTC times) to log entries would make by-inspection latency calculations much easier. The option already exists for submission time, so probably isn't too difficult to add.https://git.ligo.org/computing/gracedb/server/-/issues/106Create notice type for retraction VOEvents2019-02-21T05:21:09ZLeo P. SingerCreate notice type for retraction VOEventsSee emfollow/userguide!21.
* Create new notice type `LVC_RETRACTION=153`.
* Remove the `Retraction` param from the `<What>` section.
* Add the retraction IVORN to the `<Citation>` section.See emfollow/userguide!21.
* Create new notice type `LVC_RETRACTION=153`.
* Remove the `Retraction` param from the `<What>` section.
* Add the retraction IVORN to the `<Citation>` section.More VOEvent changeshttps://git.ligo.org/computing/gracedb/server/-/issues/107Change IVORN prefix to LVC2019-02-21T05:19:48ZTanner PrestegardChange IVORN prefix to LVCChange the IVORN prefix from `ivo://gwnet/gcn_sender` to `ivo://gwnet/LVC`, because GCN traditionally uses the text after the `/` to indicate the name of the mission, which most closely corresponds to "LVC", short for "LIGO/Virgo Collabo...Change the IVORN prefix from `ivo://gwnet/gcn_sender` to `ivo://gwnet/LVC`, because GCN traditionally uses the text after the `/` to indicate the name of the mission, which most closely corresponds to "LVC", short for "LIGO/Virgo Collaboration".
The IVORN path used to be `LVC`, but changed to `gcn_sender` when Scott Barthelmey made the change to pass through our VOEvents without any modification.
Copied from https://git.ligo.org/emfollow/userguide/merge_requests/20More VOEvent changeshttps://git.ligo.org/computing/gracedb/server/-/issues/108IVORNs for events that are confirmed as GW2019-02-21T05:18:59ZTanner PrestegardIVORNs for events that are confirmed as GWThe `superevent_id` changes so the IVORN changes. This might not be desirable. Should I fix it to always be the S-type ID? Is there anywhere else in the contents that this should be changed? I think the filename actually changes, not...The `superevent_id` changes so the IVORN changes. This might not be desirable. Should I fix it to always be the S-type ID? Is there anywhere else in the contents that this should be changed? I think the filename actually changes, not sure if that is a problem..More VOEvent changeshttps://git.ligo.org/computing/gracedb/server/-/issues/109Remove skymap image from VOEvent2019-02-21T05:18:27ZTanner PrestegardRemove skymap image from VOEventTakes too long to generate the image so it's slowing down notices. Also sounds like there is not really a need to include it anyway.Takes too long to generate the image so it's slowing down notices. Also sounds like there is not really a need to include it anyway.More VOEvent changeshttps://git.ligo.org/computing/gracedb/server/-/issues/110Rework phone and email alerts2019-03-06T18:48:50ZTanner PrestegardRework phone and email alertsPhone and email alerts should be sent out for superevents as well as events. This is going to be complicated enough that we might as well fully rework the alert infrastructure. The first step is going to be moving the models to the `al...Phone and email alerts should be sent out for superevents as well as events. This is going to be complicated enough that we might as well fully rework the alert infrastructure. The first step is going to be moving the models to the `alerts` app from `userprofile`.Rework of phone and email alertshttps://git.ligo.org/computing/gracedb/server/-/issues/111Handling "Page not found (404)"2022-08-03T19:08:55ZStuart AndersonHandling "Page not found (404)"Currently an attempt to access a deep link, e.g., https://gracedb-playground.ligo.org/superevents/S181203f/view/, without an active login session returns 404 "Page not found" and the message "No Superevent matches the given query."
Plea...Currently an attempt to access a deep link, e.g., https://gracedb-playground.ligo.org/superevents/S181203f/view/, without an active login session returns 404 "Page not found" and the message "No Superevent matches the given query."
Please consider enhancing the 404 page to conditionally indicate (if there is no active Shibboleth session) that authorized users should first try logging in, and provide a login hyperlink to do so.
For bonus points, see if there is an easy way for users that select the login link (and successfully authenticate) to automatically have their browsers reload the originally requested page.
Note, for users with a valid Shibboleth session and still land at a URL with no valid page, please also consider changing messages like No Superevent matches the given query." to "No Superevent matches the given query or you are not authorizes to view it."Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/112Filenames can't contain commas2022-08-04T01:22:48ZTanner PrestegardFilenames can't contain commasBecause the versioning method adds `,#` to the end and we rely on splitting on a comma. So we need to check this on all models with filenames and everywhere files can be uploaded (event creation/replacement specifically). It might be a...Because the versioning method adds `,#` to the end and we rely on splitting on a comma. So we need to check this on all models with filenames and everywhere files can be uploaded (event creation/replacement specifically). It might be automatically handled in the superevents API, but I'm not sure.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/113Pkt_Ser_Num voevent param lacks description2019-03-04T19:35:07ZLeo P. SingerPkt_Ser_Num voevent param lacks descriptionThe `Pkt_Ser_Num` param in our VOEvents lacks a description. How about something to the effect of, `A number that increments by 1 each time a new alert is issued for this event`.The `Pkt_Ser_Num` param in our VOEvents lacks a description. How about something to the effect of, `A number that increments by 1 each time a new alert is issued for this event`.https://git.ligo.org/computing/gracedb/server/-/issues/114Retraction VOEvents generated by GraceDb have wrong AlertType2019-03-04T19:34:55ZLeo P. SingerRetraction VOEvents generated by GraceDb have wrong AlertTypeRetraction VOEvents generated by GraceDb have the `AlertType` param set incorrectly to `Preliminary`. See the example below from the production GraceDb instance.
```xml
<?xml version="1.0" ?>
<voe:VOEvent xmlns:xsi="http://www.w3.org/20...Retraction VOEvents generated by GraceDb have the `AlertType` param set incorrectly to `Preliminary`. See the example below from the production GraceDb instance.
```xml
<?xml version="1.0" ?>
<voe:VOEvent xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:voe="http://www.ivoa.net/xml/VOEvent/v2.0"
xsi:schemaLocation="http://www.ivoa.net/xml/VOEvent/v2.0 http://www.ivoa.net/xml/VOEvent/VOEvent-v2.0.xsd"
version="2.0" role="test" ivorn="ivo://gwnet/LVC#MS190220e-2-Retraction">
<Who>
<Date>2019-02-20T05:00:16</Date>
<Author>
<contactName>LIGO Scientific Collaboration and Virgo Collaboration</contactName>
</Author>
</Who>
<What>
<Param name="Packet_Type" dataType="int" value="164">
<Description>The Notice Type number is assigned/used within GCN, eg type=164 is an LVC_RETRACTION notice</Description>
</Param>
<Param name="internal" dataType="int" value="0">
<Description>Indicates whether this event should be distributed to LSC/Virgo members only</Description>
</Param>
<Param name="Pkt_Ser_Num" dataType="string" value="2"/>
<Param name="GraceID" dataType="string" value="MS190220e" ucd="meta.id">
<Description>Identifier in GraceDB</Description>
</Param>
<Param name="AlertType" dataType="string" value="Preliminary" ucd="meta.version">
<Description>VOEvent alert type</Description>
</Param>
<Param name="HardwareInj" dataType="int" value="0" ucd="meta.number">
<Description>Indicates that this event is a hardware injection if 1, no if 0</Description>
</Param>
<Param name="OpenAlert" dataType="int" value="1" ucd="meta.number">
<Description>Indicates that this event is an open alert if 1, no if 0</Description>
</Param>
<Param name="EventPage" dataType="string" value="https://gracedb.ligo.org/superevents/MS190220e/view/" ucd="meta.ref.url">
<Description>Web page for evolving status of this GW candidate</Description>
</Param>
</What>
<WhereWhen>
<ObsDataLocation>
<ObservatoryLocation id="LIGO Virgo"/>
<ObservationLocation>
<AstroCoordSystem id="UTC-FK5-GEO"/>
<AstroCoords coord_system_id="UTC-FK5-GEO">
<Time>
<TimeInstant>
<ISOTime>2019-02-20T04:57:20.447399</ISOTime>
</TimeInstant>
</Time>
</AstroCoords>
</ObservationLocation>
</ObsDataLocation>
</WhereWhen>
<Citations>
<EventIVORN cite="retraction">ivo://gwnet/LVC#MS190220e-1-Preliminary</EventIVORN>
<Description>Determined to not be a viable GW event candidate</Description>
</Citations>
</voe:VOEvent>
```https://git.ligo.org/computing/gracedb/server/-/issues/115Zero-valued sngl_inspiral columns are missing from JSON representations of ev...2019-04-22T14:57:38ZLeo P. SingerZero-valued sngl_inspiral columns are missing from JSON representations of eventsOriginally reported as emfollow/gwcelery#85.Originally reported as emfollow/gwcelery#85.https://git.ligo.org/computing/gracedb/server/-/issues/116Add log filtering by tag2022-08-04T01:24:41ZTanner PrestegardAdd log filtering by tagAdd a filter to the logs API where only logs with certain tags applied will be retrieved. Would need a client update as well.Add a filter to the logs API where only logs with certain tags applied will be retrieved. Would need a client update as well.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/117GWCelery issues with AWS implementation of GraceDB2019-03-08T20:53:50ZTanner PrestegardGWCelery issues with AWS implementation of GraceDBGWCelery has been seeing a few new errors since we moved the service to the AWS cloud:
* `SSLEOFError: Problem establishing secure connection: EOF occurred in violation of protocol (_ssl.c:777)`: [link](https://emfollow.ligo.caltech.edu...GWCelery has been seeing a few new errors since we moved the service to the AWS cloud:
* `SSLEOFError: Problem establishing secure connection: EOF occurred in violation of protocol (_ssl.c:777)`: [link](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/299/?query=is:unresolved)
* `SSLError [SSL: SSL_HANDSHAKE_FAILURE] ssl handshake failure (_ssl.c:2217)`: [link](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/305/)
* `ConnectionResetError [Errno 104] Connection reset by peer`: [link](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/306/)https://git.ligo.org/computing/gracedb/server/-/issues/118SSLEOFError for some clients2019-04-22T16:10:31ZTanner PrestegardSSLEOFError for some clientsGWCelery is reporting periodic `SSLEOFError`s that have occurred when trying to interact with the GraceDB API using gracedb-client. A Sentry page which is tracking these issues is [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery...GWCelery is reporting periodic `SSLEOFError`s that have occurred when trying to interact with the GraceDB API using gracedb-client. A Sentry page which is tracking these issues is [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/299/events/latest/).
The error looks like
```
SSLEOFError
EOF occurred in violation of protocol (_ssl.c:777)
```https://git.ligo.org/computing/gracedb/server/-/issues/119SSLError for some clients2019-03-27T15:03:23ZTanner PrestegardSSLError for some clientsGWCelery is reporting periodic `SSLError`s that have occurred when trying to interact with the GraceDB API using gracedb-client. A Sentry page which is tracking these issues is [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/iss...GWCelery is reporting periodic `SSLError`s that have occurred when trying to interact with the GraceDB API using gracedb-client. A Sentry page which is tracking these issues is [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/305/).
The error looks like
```
SSLError
[SSL: SSL_HANDSHAKE_FAILURE] ssl handshake failure (_ssl.c:2217)
```https://git.ligo.org/computing/gracedb/server/-/issues/120ConnectionReset error for some clients2019-03-11T17:12:42ZTanner PrestegardConnectionReset error for some clientsGWCelelry saw two `ConnectionReset` errors to gracedb-playground (see Sentry issue [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/306/)). The error looks like
```
ConnectionResetError
[Errno 104] Connection reset by pee...GWCelelry saw two `ConnectionReset` errors to gracedb-playground (see Sentry issue [here](https://emfollow.ligo.caltech.edu/sentry/gwcelery/issues/306/)). The error looks like
```
ConnectionResetError
[Errno 104] Connection reset by peer
```https://git.ligo.org/computing/gracedb/server/-/issues/121\pi value in VOEvent builder erroneously truncated2019-03-27T15:02:32ZErik Katsavounidis\pi value in VOEvent builder erroneously truncated\pi in https://git.ligo.org/lscsoft/gracedb/blob/master/gracedb/events/buildVOEvent.py is set to 3.14152 which is not right at the 5th decimal point. Needs to be fixed.\pi in https://git.ligo.org/lscsoft/gracedb/blob/master/gracedb/events/buildVOEvent.py is set to 3.14152 which is not right at the 5th decimal point. Needs to be fixed.https://git.ligo.org/computing/gracedb/server/-/issues/122Open alerts should be public in GraceDb2022-08-04T01:25:41ZLeo P. SingerOpen alerts should be public in GraceDbIt's useful to be able to download old VOEvents. We should make this possible for anonymous GraceDb users. Please add the `public` tag to any VOEvent that is created with `internal=False`.It's useful to be able to download old VOEvents. We should make this possible for anonymous GraceDb users. Please add the `public` tag to any VOEvent that is created with `internal=False`.Backloghttps://git.ligo.org/computing/gracedb/server/-/issues/123QOL Improvement - Login Warning2022-08-04T01:26:04ZRyan FisherQOL Improvement - Login WarningWould it be possible to add a warning to the search/search results page(s) if you aren't logged in? I noticed you almost did this during the presentation today, and it reminded me that it's easy for students and users to make this mista...Would it be possible to add a warning to the search/search results page(s) if you aren't logged in? I noticed you almost did this during the presentation today, and it reminded me that it's easy for students and users to make this mistake and waste time not finding their results.https://git.ligo.org/computing/gracedb/server/-/issues/124Improve LVAlert Overseer configuration2022-08-04T01:26:41ZTanner PrestegardImprove LVAlert Overseer configurationA few ideas:
* Move overseer into its own container so we don't have one instance in each gracedb container (will have to update the overseer code to allow connections from outside localhost (optionally; not by default) and secure it on...A few ideas:
* Move overseer into its own container so we don't have one instance in each gracedb container (will have to update the overseer code to allow connections from outside localhost (optionally; not by default) and secure it on AWS)
* Add some kind of monitoring to it (in AWS? via some Django URL that nagios can query?)
* Fix the client persistance with the failover to the basic LVAlert client