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
Description
Objects with eccentricity greater than 0.9 (e > 0.9) are not correctly positioned when created using createObject. While debugging, I found that the anomaly calculation and position update mechanism do not correctly compute the trajectory, leading to incorrect visualization. The issue seems to be related to the handling of parabolic and near-parabolic orbits in the KeplerParticles.update(jd) function.
Steps to Reproduce
Create an object with createObject using the following parameters:
Observe that the object's position is incorrect when compared to expected orbital mechanics calculations.
Expected Behavior
The object should follow the correct Keplerian trajectory based on its orbital parameters.
Objects with e > 0.9 should still be properly plotted according to their mean anomaly and true anomaly computations.
Actual Behavior
The object remains static or is plotted in an incorrect position.
The update(jd) function correctly prints debug logs showing updated values for mean anomaly (M), but the position is not visually updated in the WebGL scene.
Potential Cause
The calculation of a0 for objects with e > 0.9 may be incorrect or not properly fed into the shader update.
The handling of mean anomaly (M) and a0 might be inconsistent with how Spacekit expects to compute the position in highly eccentric cases.
Suggested Fix
Review how KeplerParticles.update(jd) updates M and a0.
Ensure that M is properly propagated for high-eccentricity objects.
Check if the position update logic in the fragment shader or vertex shader is correctly using these updated values.
The text was updated successfully, but these errors were encountered:
Description
Objects with eccentricity greater than 0.9 (e > 0.9) are not correctly positioned when created using createObject. While debugging, I found that the anomaly calculation and position update mechanism do not correctly compute the trajectory, leading to incorrect visualization. The issue seems to be related to the handling of parabolic and near-parabolic orbits in the KeplerParticles.update(jd) function.
Steps to Reproduce
Expected Behavior
Actual Behavior
Potential Cause
Suggested Fix
The text was updated successfully, but these errors were encountered: