Navigation » Orbiter-Forum > Projects > ORBITER 2010-P1 > Bug » oapiGetPlanetCurrentRotation

oapiGetPlanetCurrentRotation Issue Tools
issueid=122 07-23-2009 01:56 PM
Beta Tester
oapiGetPlanetCurrentRotation
return value of oapiGetPlanetCurrentRotation is incorrect
It seems that return value of oapiGetPlanetCurrentRotation() is incorrect.

It looks like the return value is an angle from the node of precession axis and planet rotation axis to prime meridian, when it supposed to be an angle from the node of ecliptic and planet rotation axis to prime meridian.

Functions oapiGetPlanetObliquity() and oapiGetPlanetTheta() seems to be ok.
Issue Details
Issue Type Bug
Project ORBITER 2010-P1
Category Unknown
Status Fixed
Priority 1 - Highest
Affected Version 090722
Fixed Version (none)
Users able to reproduce bug 0
Users unable to reproduce bug 0
Attachments 0
Assigned Users (none)
Tags Physics

06-16-2010 12:33 PM
Beta Tester
  
Let's bring this issue on a top.
Reply
06-16-2010 04:44 PM
Beta Tester
  
Looks like my memory is starting to return slowly....

If a planet orientation is computed using a function set oapiGetPlanetObliquity(), oapiGetPlanetTheta(), oapiGetPlanetCurrentRotation() then the calculations will fail in the Orbiter 2010 when in the Orbiter 2006 this did produce a valid result.

In the Orbiter 2010 correct result is archived when oapiGetPlanetObliquityMatrix() is used to acquire the obliquity matrix and it is then rotaded by the amount received from the oapiGetPlanetCurrentRotation().

If we want that both approaches are valid then both functions oapiGetPlanetCurrentRotation() and oapiGetPlanetObliquityMatrix() should be altered.

The other possibility is to make oapiGetPlanetTheta() obsolete and issue a warning when used due to potential probability of invalid use.
Reply
07-28-2010 08:12 PM
Beta Tester
  
This issue is fixed.
Reply
Reply

Issue Tools
Subscribe to this issue