Open DavidT3 opened 6 months ago
It seems to happen when the 'seconds' component of the start or end time that ends up as NaT is '60' - so really it should tick over to the next minute. This must be a problem with the was eROSITA writes times in its event lists.
One of them I think is because an errant character got added on to the end of the time string, but the others don't seem to be because of this - e.g. '260177' has a NaT value for start.