Open maxnoe opened 4 years ago
agreed. Generally this should never happen unless the user is doing something unexpected. So raising an Exception (perhaps RangeError) is the right way to go, since it is an exceptional case.
I think adding a line explaining allowed range to the docstring or in the high-level user docs would also be useful. Something like "The CameraFrame/TelescopeFrame are intended to represent coordinates within the FOV of the telescope; coordinates far outside that range may not transform correctly to general Earth or sky coordinates. "
agreed. Generally this should never happen unless the user is doing something unexpected.
It could happen quite regularly for badly reconstructed events. A very small percentage of events will be that bad but there will be lots of events....
Ah, yes, i was thinking the reconstructed events are always in the TelescopeFrame or HorizonFrame, but one might want to plot them in the CameraFrame. In any case, it should still complain.
Currently it is possible to transform crazy values of camera coordinates to skycoordinates without a warning.
Then there is a certain point, where it completely breaks down (at pi/2 times the focal length) and the transformation to telescope frame:
We should probably warn or error if something is further of than something like 15 degrees or so.