Modify

Opened 10 years ago

Closed 7 years ago

#20 closed defect (fixed)

Leap second bug in BNC

Reported by: k.fenaughty Owned by: mervart
Priority: major Component: BNC
Version: Keywords:
Cc:

Description

We are running v2.6 of BNC. The latency calculations produced by this software have been incorrect since the leap second of July 1 2012. The bug is in the module rtcm3torinex.c which does not feature the latest leap second.

The result is that latency messages are being logged every second instead of at the proscribed interval (perfIntr), and of course the calculations are wrong (negative latencies!).

Attachments (0)

Change History (3)

comment:1 by k.fenaughty, 10 years ago

It was pointed out to me by a colleague that you have already found the above bug and fixed the source code in late June and early July. When can we expect new executables to be available from the GNSS Data Center? This is causing a major impact with measuring quality of service for our GNSS streams in the meantime.

Thanks,
Kevin Fenaughty

comment:2 by pgentle@…, 10 years ago

This issue is also affecting our stats reporting for our service.

Are you able to inform us when you will be releasing the fix?

I could get our programmers to look at it but I don't want to waste their time if you will be releasing it in the next couple of days.

Thanks

comment:3 by stuerze, 7 years ago

Resolution: fixed
Status: newclosed

The leap seconds within the current module rtcm3torinex.c are up to date

Modify Ticket

Change Properties
Action
as closed The owner will remain mervart.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.