Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Phase of Mars's, Uranus's and Neptune's moons: precise mean motions and epoch longitudes

Open
#139 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, three.js

Research direction

Read issue #137 and inspect its fixture epochs and Saturn-moon implementation for how orbital elements are sourced and tested. Compare the named moons’ positions with JPL Horizons at those epochs; the issue gives a target tolerance of about 1° and requires a test to pin the result.

Written by the indexing model from the issue text.

Description

track:solar-system

After #137, the orbital planes of Phobos, Deimos, Titania, Oberon, Triton and Proteus are right. But their positions along the orbit drift by tens of degrees, up to 180°, against JPL Horizons over 2000–2050.

The published satellite tables give periods to only 4–7 significant figures, and Phobos's node period is rounded to 2.3 yr. Over 50 years that is many revolutions.

Take precise mean motions and epoch longitudes from Horizons' osculating elements, as #137 did for Saturn's moons, or from the tables' source ephemerides.

Done when: these moons are within a stated tolerance (e.g. 1°) of Horizons at the #137 fixture epochs, and a test pins it.

Dominant language
JavaScript
Stars
55
Forks
4
Avg merge
9h 32m
Merged PRs (30d)
136

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from celestiary/web

All issues in celestiary/web

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.