Faster TimeSelector and SpacecraftHistory

[israelmcmc]

TimeSelector:

• Faster, using only 64bit precision
• Add unit tests
• Be consistent about tstart inclusive, stop exclusive.

I'll work on a similar trick (64bit precision) for SpacecraftHistory (I'll abandon histpy.TimeAxis in favor of a regular Axis since COSI doesn't need <1us precision).

[codecov]

Codecov Report

❌ Patch coverage is 88.88889% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 72.80%. Comparing base (6ef0230) to head (c73702e).
⚠️ Report is 91 commits behind head on develop.

Files with missing lines	Patch %	Lines
cosipy/spacecraftfile/spacecraft_file.py	73.33%	8 Missing ⚠️

Files with missing lines	Coverage Δ
cosipy/event_selection/time_selection.py	100.00% <100.00%> (+100.00%)	⬆️
cosipy/spacecraftfile/spacecraft_file.py	90.00% <73.33%> (+5.76%)	⬆️

... and 7 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jdbuhler]

I don't have a good sense of how expensive the conversions between Time and Julian date are, but I assume they are way less painful than the TimeAxis operations. I'll have to benchmark the SpacecraftHistory after the changes to see what the overhead of select_interval() is.

I see that intervals_duration() now returns a value in days. Are there other places where we were used to using seconds as the typical time unit of orientation history but are now going to have to change?

[israelmcmc]

@jdbuhler Thanks for checking. I used Julian days because that's what the underlying Time objects use. It just needs to sum jd1+jd2. Hopefully this sum is not much of an overhead, and it will allows us to still use Time for the inputs/outputs.

I see that intervals_duration() now returns a value in days. Are there other places where we were used to using seconds as the typical time unit of orientation history but are now going to have to change?

No code should assume units of intervals_duration(). The function only "promises" to return Quantity. If we find such instance using .value, we should change them to to_value(u.s) (if really needed in seconds). I also used days here to avoid the extra conversion from the underlaying jd

[jdbuhler]

OK, approving review

[israelmcmc]

Thanks @jdbuhler !