Range by skydel

Hello @Grace
I just have one quick question.
I generate simulator for known coordinate station (CORS station by NGS ) since we have observation file for the same date and time from NGS. I noticed the Range based on Pseudorange generated by simulator is too different compared with Range from NGS website for the same date , time and satellite. I attached couple of screenshot to be more clear. Do you have any idea why it is too far. Is doing simulation in NONE mode effect ?

I also compared Navigation file between two , Some Keplerian elements are too off

The CORS station is p375. Date:2022 1 1

If you could please take a look and give me your suggestion , I will really appreciate
Compariosn_None.pdf (509.0 KB)

1 Like

Hi @alqurask,

We have received your question. We will check and get back to you as soon as possible.


Hey @alqurask ,

Indeed, the Pseudorange of the Rinex observation files includes the real clock errors of the satellites in the PSR calculation.

In skydel, since the simulator defines the position and motion of the satellites by extrapolating the data from the Rinex ephemeris, we should expect errors in the PSR calculation as well.

So it is normal that you have an offset when comparing the two PSRs.


1 Like

Hello @Geace,
Just one more question related to that. Beside the fact of skydel simulator relies on RINEX ephemeris , Is there any other factor cause this difference such as clock error , … etc.


Hi @Khalid,

Yes, the pseudorange calculation on the observation file is the distance from the receiver antenna to the satellite antenna, including receiver and satellite clock offsets, and other biases such as atmospheric delays.


1 Like