Closed johnnyturpin-aow closed 1 year ago
It's a good question, for which I don't see necessarily a definitive answer.
From my memory, these times require a small iterative process to minimise a distance. And depending on where the min distance is found (after or before the provided starting time), you end up with rise, transit & set times not exactly in the "night" you want.
It thought it was better to leave to the client to verify, and apply possible corrections, rather than imposing one myself.
Thanks for the response... that is what I kinda figured.
I am a bit confused about the riseTransitSetTimes methods for CelestialBody. I am getting results for some objects calculated at a specific time where the setTime is prior to the riseTime.
Are my expectations incorrect that the times should be in the sequence of rise -> transit -> set?
Should I add 24hr to the setTime result when a setTime is prior to riseTime or should make two riseSetTransitTimes calls and merge the results so that I get a setTime value that is after the transit?
Here is a use-case where it resulted in rise -> transit -> set times in correct chronological order:
And here is a use-case where it resulted in rise -> transit -> set times where the setTime is prior to the riseTime: