You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spice::computeSolarLon by default always computes solar lon and appends it the cube label from Spice kernels. This should use the tables if present. This is an issue when creating tables from ISDs instead of going through the spiceinit process.
How to reproduce
Run Campt on a cube that doesn't have the solor lon key present and you'll get a tiny negative number in place of real solor lon.
Possible Solution
The code already exists in Spice::computeSolarLon it just needs the if statement changed to include if (m_usingAle || !m_usingNaif). This will create a subtle difference in SolorLon value so tests will need to be updated.
Additional context
The text was updated successfully, but these errors were encountered:
I am a bot that cleans up old issues that do not have activity.
This issue has not received feedback in the last six months. I am going to add the inactive label to
this issue. If this is still a pertinent issue, please add a comment or add an emoji to an existing comment.
I will post again in five months with another reminder and will close this issue on it's birthday unless it has
some activity.
ISIS version(s) affected: 4.X.X
Description
Spice::computeSolarLon by default always computes solar lon and appends it the cube label from Spice kernels. This should use the tables if present. This is an issue when creating tables from ISDs instead of going through the spiceinit process.
How to reproduce
Run Campt on a cube that doesn't have the solor lon key present and you'll get a tiny negative number in place of real solor lon.
Possible Solution
The code already exists in Spice::computeSolarLon it just needs the if statement changed to include
if (m_usingAle || !m_usingNaif)
. This will create a subtle difference in SolorLon value so tests will need to be updated.Additional context
The text was updated successfully, but these errors were encountered: