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

Relative-to-eye placement of far things, and the view as the instrument sees it (option 3)

Abierto
  • ¿Algo no está bien?
#340 0 comentarios 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, three.js
Área
computer-graphics

Línea de trabajo

Start with HDR.md sections “A telescope’s field” and “The instrument,” then inspect the far-point and star rendering paths the issue says already apply the instrument response. The issue gives no file or test names for the relative-to-eye renderer or resolved-disc pass, so first trace those entry points and the dependencies on #337 and #338. Done means far bodies and their paths render at the stated precision, and the instrument view can be toggled and compared at its resolution.

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

Descripción

Part of #334, option 3: the general fix, as an override once options 1 and 2 are in (the maintainer's comment), and the ground for comparing an instrument's view with a spacecraft's photograph (Rubin on Saturn against Cassini's; #333 for Rubin's own imagery).

The precision. Everything placed at 7e12 m from the camera is held to float32's 5e5 m: the far body's mesh, the apparent path's points and its ring, the orbit line's vertices, and the body's depth, which reads as empty sky. Relative-to-eye rendering keeps each far thing's centre in float64 on the CPU and uploads, each frame, its offset from the camera and its geometry about its own centre, so the GPU never sees a large number. Three's scene graph is float32 at the matrix level, so this is per object: a far body's mesh at the camera's origin with a per-frame offset, the path's and orbit line's points as offsets from a float64 anchor near the camera's line of sight, and the depth of a far body written as a near-plane proxy so lines in front of it occlude.

The view as seen. The maintainer's wider ask: carry the render to the eye as the instrument would see it, and be able to toggle between that and the scene as drawn, so a telescope on a body we have spacecraft photographs of (Saturn, Jupiter) can be compared with them at the instrument's resolution. That is the instrument's PSF and pixel grid applied to the frame (HDR.md, "A telescope's field", "The instrument"), which the far point and the stars already do point by point; a resolved disc needs it as a pass.

Scope this after #337 and #338 land, and before or with #333.

Lenguaje dominante
JavaScript
Estrellas
55
Forks
4
Merge medio
9 h 32 min
PR fusionados (30 d)
136

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.