The new outlier detection code no longer auto-rejects any read, but it's still a good idea to keep doing this for a double read (i.e. two reads within a very short timeframe at the same reader). The time frame should not be as long as 30 seconds (which it was before), 10 seconds should suffice to reject double reads (as long as it's 10 seconds since the last read, even if that last read was rejected, so no laps are counted if there is a problem and a team's baton is near the same antennas for a long time).
The new outlier detection code no longer auto-rejects any read, but it's still a good idea to keep doing this for a double read (i.e. two reads within a very short timeframe at the same reader). The time frame should not be as long as 30 seconds (which it was before), 10 seconds should suffice to reject double reads (as long as it's 10 seconds since the last read, even if that last read was rejected, so no laps are counted if there is a problem and a team's baton is near the same antennas for a long time).
Also adjust the graphing code in the UI, https://github.com/ULYSSIS-KUL/ipp/blob/master/UI/src/main/java/org/ulyssis/ipp/ui/widgets/TeamPanel.java#L302-L304, to this