Ody Driver Fixes

[amystamile-usgs]

No description provided.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 99 lines in your changes are missing coverage. Please review.

Project coverage is 14.67%. Comparing base (58a8ee4) to head (283e82a).

Files	Patch %	Lines
ale/drivers/ody_drivers.py	0.00%	94 Missing ⚠️
ale/base/type_distortion.py	0.00%	4 Missing ⚠️
ale/drivers/__init__.py	0.00%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #582      +/-   ##
==========================================
- Coverage   14.84%   14.67%   -0.17%     
==========================================
  Files          59       59              
  Lines        6697     6772      +75     
==========================================
  Hits          994      994              
- Misses       5703     5778      +75     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[amystamile-usgs]

Seeing an issue with Themis VIR where:

with sclkCode: -53 and clockValue: 1023406812.230

I am seeing two different results:

CSpice scs2e_c is returning 392211096.4307215.

SpiceyPy spice.scs2e is returning 392211095.6221291.

@acpaquette have you ever run into this before?

[acpaquette]

Seeing an issue with Themis VIR where:

with sclkCode: -53 and clockValue: 1023406812.230

I am seeing two different results:

CSpice scs2e_c is returning 392211096.4307215.

SpiceyPy spice.scs2e is returning 392211095.6221291.

@acpaquette have you ever run into this before?

I have not seen this, I would make sure your times are the same to the 16th sig fig and that the codes are the same

[amystamile-usgs]

Seeing an issue with Themis VIR where:
with sclkCode: -53 and clockValue: 1023406812.230
I am seeing two different results:
CSpice scs2e_c is returning 392211096.4307215.
SpiceyPy spice.scs2e is returning 392211095.6221291.
@acpaquette have you ever run into this before?

I have not seen this, I would make sure your times are the same to the 16th sig fig and that the codes are the same

Figured out that python's str() function was dropping the zero and causing it to convert the time for 1023406812.023 instead of 1023406812.230.

[AustinSanders]

Should be good to go after a changelog entry!