Error when two superevents within RAVEN window
From @deep.chatterjee : I noticed an external trigger in playground (https://gracedb-playground.ligo.org/events/E13064/view/) corresponding to which sentry sent an error notification. It seems like the code tried to assign it to two superevents S190323m and S190323n as can be seen from the log messages.
Now I guess, if RAVEN is looking for a long window like 600s, it is possible that it will find 2 or more superevents. The superevent windows are typically only a few seconds long, max. The code will always raise an error in those cases, so would it be useful to assign it to the superevent which is closer in time difference?
in that case, at least, the method is deterministic and the E event is simply not put into the superevent that the code finds first