Add individual computation methods for (Field) TrackingCoordinates in TopocentricFrame
The recent addition of (Field)TrackingCoordinates
avoids redundant computations when several quantities are needed e.g. elevation and azimuth. However when only one is needed, some performance is lost if all quantities are computed anyway in the process, as is now the case in TopocentricFrame
. With Field
in particular, this is detrimental as atan2
is a bit slow.
So here is what I propose:
- put back methods
getElevation
,getAzimuth
, etc., bypassinggetTrackingCoordinates
- in order to avoid code duplication, introduce a private, intermediate method doing computations until the
transformPosition
basically. Also one for the azimuth rephasing.
Edited by Romain Serra