Opened 5 months ago

Closed 5 months ago

#176 closed defect (fixed)

Ephemeris state not check based on current time in real-time processing

Reported by: lucia Owned by: stuerze
Priority: normal Component: BNC
Version: Keywords:


In PPP processing, the satellite position is obtained from the applicable navigation message. There is a check on whether this message can be used or whether it should be discarded because it is unhealthy, outdated or bad-formed. However, from the current implementation, it seems that in real-time processing this status is only defined at the time the message arrives for the first time. Therefore, if a navigation message is not updated, exceeding the validity time, but the satellite is still in view, the outdated navigation message may be used.

I think that in real-time inside the PPP processing, when the getCrd function is called, it is necessary to relaunch the checkEphemeris to ensure the ephemeris saved in the database is still valid and not outdated.

Attachments (0)

Change History (1)

comment:1 by stuerze, 5 months ago

Resolution: fixed
Status: newclosed

Dear Lucia,

Thanks for this hint. Such a test was implemented already but activated for ephemerides stream generation only. Now I have added this test in PPP and combination mode as well, to check if stored ephemerides were outdated and/or not updated in between. This wll be part of the next BNC update after some successful monitoring days.

Best regrads, Andrea

Modify Ticket

Change Properties
as closed The owner will remain stuerze.
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.