Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Show the nearest DSO's name on the chart screen

Aperta
  • Qualcosa non va?
#602 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
65/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
frontend

Direzione di ricerca

Start with python/PiFinder/ui/chart.py, especially UIChart._get_nearby_markers() and the chart drawing code around the existing RA/Dec row. Use python/PiFinder/nearby.py and its get_closest_objects() lookup to identify the nearest object as the chart centre changes. Done means the nearest eligible object's name is displayed while panning, remains blank beyond a sensible distance cutoff, and is suppressed at the widest zoom.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Background

Field report on the returned DSO markers: panning around the sky on the chart
and hitting the markers is a great way to observe, especially with hand-
controller zoom — but there is currently no way to tell what any marker is.
The icon gives the object type and nothing more.

Proposal

Display the name of the object nearest the chart centre at the edge of the
screen, updating as the user pans.

The lookup machinery already exists. UIChart._get_nearby_markers()
(python/PiFinder/ui/chart.py:218) builds the marker set from the active
"All Filtered" catalog via a cached BallTree, and python/PiFinder/nearby.py
already exposes get_closest_objects() (k-NN) alongside the
get_objects_within_radius() call the chart currently uses. Nearest-by-angle
needs no new indexing — the chart just needs to ask a different question of the
tree it already maintains.

Design constraints

The bottom row is already occupied. chart.py:383-402 draws the optional
RA/Dec readout at resY - base.height - 3, gated on the chart_radec config
option ("HH:MM" / "Degr" / off). The label needs to either share that row,
sit at the top instead, or define precedence when both are enabled.

Suppress at the widest zoom. The chart's FOV levels are
fov_list = [5, 10.2, 20, 30, 60] (chart.py:72). The 60° view is for moving
between constellations or jumping to a new patch of sky, where a nearest-object
label is noise rather than help. Showing it at 30° and below is the suggested
starting point; worth tuning on hardware.

Only label what is actually near. The nearest catalog object can still be a
long way from the centre in a sparse field. A distance cut-off — likely tied to
the current FOV — should leave the label blank rather than naming something off
the edge of the field.

Follow-up

Being able to jump straight to the labelled object's details screen is tracked
separately, and depends on this.

Lingua principale
Jupyter Notebook
Stelle
253
Fork
63
Merge medio
11h 55m
PR unite (30g)
8

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di brickbots/PiFinder

Tutte le issue di brickbots/PiFinder

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.