Rubin's real cadence: visits and fields, not a stare

Open
  • Is something wrong?
#332 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, three.js
Domain
computer-graphics

Research direction

This issue is part of #321 and describes a new model for Rubin's nightly survey schedule, including fields, slews, and the object's field. Start by reading #321 and tracing the existing demo that tracks the object all night; the issue does not name files or tests. Done means the demo models a night's survey schedule using the survey strategy or published visit lists.

Written by the indexing model from the issue text.

Description

track:spacecraft

Part of #321. Rubin surveys the sky in 30-second visits across many fields; the discovery came from the pipeline's detections across them. The demo tracks the object all night to show where it is. Model a night's schedule (fields, the slews between them, the object's field among them), from the survey strategy or the published visit lists.

🤖 Generated with Claude Code

Dominant language
JavaScript
Stars
55
Forks
4
Avg merge
10h 12m
Merged PRs (30d)
134

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.