Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The actual values stored in the raw data are the times in microseconds.
  • The time in seconds is used to display a hours:minutes:seconds value in a report
    • This is determined calculated when the report is generated by rounding the microseconds value divided by 1000000 (the number of microseconds in one second)
  • The sums at the bottom are calculated in the report, by summing up the relevant column.

...

As you can see, one second has gone missing, although the sum is sums are numerically correct.

Info

So where did it go?

  • This is due to a cumulative number of microseconds which is greater than half a second, being rounded off when the number of seconds is calculated for each row.

An alternative could be displaying to get the sum of the number of seconds from the sum of the microseconds (which is correct) and display the following:

StatusTime in Status in MicrosecondsTime in Status in Seconds
Status 141,570,259,03341570
Status 2162,338,287162
Status 368,047,41068
Status 4258,951,950259
Status 5314,248,890314
Status 644,026,154,43044026
SUM86,400,000,00086400

...

However, astute readers will note that 41570 + 162 + 68 + 259 + 314 + 44026 does not in fact equal 86400.

Info

So what to do?

Unfortunately, this is called the rounding paradox.

The simple fact of the matter is there is no nice way to deal with this.

  • You either live with the missing second(s) in the output
  • Or you display an incorrect value somewhere in the data, by adding the missing seconds to the individual data rows

We here at jtel have decided just to live with it - so sometimes the sums in our reports, when they involve times, may not add up as you would expect. Now, at least you know why!

...