Custom Query (104 matches)
Results (1 - 3 of 104)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #176 | fixed | Ephemeris state not check based on current time in real-time processing | ||
| Description |
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. |
|||
| #175 | worksforme | Windows MSI v2.13.0 is identified as Trojan by Windows defender | ||
| Description |
It's identified as "Trojan:Win32/Bearfoos.A!ml" and removed. |
|||
| #174 | fixed | DVS status and SISA not considered for Galileo Satellites | ||
| Description |
According to the Galileo ICD, health status of the Galileo satellites is defined by the combination of HS, DVS and SISA send by navigation message. The current software only considers the HS, which causes satellites like E14 or E18 (which should not be used by the user) to be considered in the PPP. |
|||
