Dear all,
I’ve got a question. In the angular ionospheric correction (for AzEl), the azimuth is not just corrected with a small delta, it’s completely overridden by a new ad hoc value. From what I see in the code, the latter does not take into account the station position error. That’s not right is it?
Maybe @luc @baubin can confirm?
Cheers,
Romain.
So you’re correct that the version 13 of the code does not take into account station position error, because it called the getBaseFrame() function of the underlying ground point to calculate the ground station position. However, one of the things I did in the MRs we’ve been pushing to update the measurement classes was add a function getPVCoordinatesProvider() which actually does account for the position error. That is the function that is getting called to calculate the ionospheric delay in the MR I have up now to allow the ionospheric models to perform space-space calculations, so hopefully in v14 that will no longer be an issue.
Gotcha!
Other question in the same category : for range related stuff, the javadoc says that sometimes the clock bias cancels itself, like for two way. But it’s not really true, at least not with a linear drift. Shouldn’t we add this as well to be rigorous?
Cheers
Actually, that gets into a more complicated question that I had wanted to ask you guys about calculating clock drift for some of these measurements, but it’s complex and I don’t have the time to focus well enough to ask the quesiton correctly. I’ll get back to this by Tuesday and we can have the discussion.