`propcov`: The classes supporting the `DSPIPCustomSensor` appear to require that the clock angles be in the range 0deg to 360 deg. Change behaviour to accept clock angles in any range.

[vinay0000]

Polygon::util::cartesianToSpherical function is used by the classes in the polygon folder and it forces the clock angle to be in the range 0 deg to 360 deg. Errors ensue if this forcing is removed.

It would be better to find where in the code there is actual requirement of the clock angles to be in the range 0 deg to 360 deg and perhaps add the forcing there.

[vinay0000]

Reply from Ryan:

In the preprocessing step, I add a 'false vertex' at 360 degrees in order to preserve the binary search space when the cycle is unwound into an array (described in the paper). This could easily be done on -180-180 bounds instead, but the way I implemented it assumes 0-360 boundaries. This can be found in the SliceArray class.