You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So the form is (1/(1+a / ... )) / (1+1/(sinel +b / ...))
As (1/y)/(1/x) can be rewritten as x/y
Then the calculation above can be simplified as (sinel +b / ...) /(1+a / ... )
There can be no ambiguity as later it is used directly as follow, without further division or calculation directly as mapf :
This is the same (wrong?) implementation as RTKLib and any other commonly used RTK library I could find on github.
Am I just wrong about the understanding of the calculation, or is everyone copy-pasting the same error ?
The text was updated successfully, but these errors were encountered:
Hi,
There is a common pattern I see in all implementations of the Niell tropo across github :
The implementation is always the same :
(1+a / ... ) / (sinel +b / ...)
while I believe it should be(sinel +b / ...) / (1+a / ... )
(the opposite)For example :
rtklib-py/src/rtkcmn.py
Line 737 in 5d8968d
However, original paper ( https://safe.nrao.edu/wiki/pub/Main/RefBendDelayCalc/Niell_Global.pdf ) list "equation 4" as :
So the form is
(1/(1+a / ... )) / (1+1/(sinel +b / ...))
As
(1/y)/(1/x)
can be rewritten asx/y
Then the calculation above can be simplified as
(sinel +b / ...) /(1+a / ... )
There can be no ambiguity as later it is used directly as follow, without further division or calculation directly as mapf :
rtklib-py/src/rtkcmn.py
Line 755 in 5d8968d
This is the same (wrong?) implementation as RTKLib and any other commonly used RTK library I could find on github.
Am I just wrong about the understanding of the calculation, or is everyone copy-pasting the same error ?
The text was updated successfully, but these errors were encountered: