Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Simulated telescope mode and a limiting-magnitude filter for Gaia-scale catalogues

Abierto
  • ¿Algo no está bien?
#155 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, three.js
Área
data-visualization, frontend, performance

Línea de trabajo

Start by reading the work in PR #153, especially limitingMagnitude(), ThreeUi.setLimitingMagnitude, the existing bloom law, and the probe it introduced; inspect the settings and permalink handling for the proposed lm= parameter. The issue proposes magnitude filtering for Gaia-scale catalogues and telescope controls for aperture and exposure, but does not name the relevant files or tests. Done means the acceptance probe shows counts matching the limit at each setting while day and twilight remain unchanged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

PR #153 made the star field's calibration one parameter: LIMITING_MAGNITUDE (6.5, the dark-adapted naked eye at the metered dark gain), with the limit at any exposure given by limitingMagnitude(gain, starGain), and a user gain (ThreeUi.setLimitingMagnitude, stepped with [ / ] as in Celestia). Three things build on it.

1. Telescope mode. Aperture D and exposure t raise the light gathered by (D / 7 mm)² · (t / 0.1 s), so the limit by 2.5 · log10 of that: a 100 mm aperture is +5.8 magnitudes, which reaches this Celestia catalogue's faintest stars (~9.5) and, with Gaia, 12+. Model it as a star gain with those two knobs, a narrower field (the FOV already drives the patch per pixel), and the bloom law already in place for the bright end. The sky's own light and the planets' discs follow from the same exposure (a telescope on the day sky still shows Venus, not Vega).

2. Gaia (#98) needs the limit as a filter. A 1M-star buffer can't draw everything every frame: sort stars by magnitude (or tile by magnitude bands) and draw only those brighter than limitingMagnitude() plus a margin, so the naked-eye default draws ~10k and telescope mode pages in the fainter bands. The same cut is what the galaxy plan (#116) wants for its density.

3. The user's limit in Settings and the permalink. A numeric setting, the first (the s= letters are switches), e.g. lm=7.5.

Acceptance: the probe from #153 (project every star, read its pixel per magnitude bin) shows the counts per bin matching the limit at each knob setting; day and twilight unchanged.

From the maintainer: "Celestia had an variable mag threshold and if we get to Gaia, we'll probably want one just to filter out stars that aren't visible to the naked eye. it'd be good to then vary the exposure to pick up fainter stars in a kind of simulated telescope mode to then allow seeing all that were originally captured in the catalog".

Generated by Claude Code

Lenguaje dominante
JavaScript
Estrellas
55
Forks
4
Merge medio
10 h 12 min
PR fusionados (30 d)
134

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de celestiary/web

Todos los issues de celestiary/web

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.