rpotter6298 0814e7c965 Fix: Use issued_at instead of target_at for zero-hour resolved truth timestamps ...

The zero-hour forecasts (observations) were being saved with resolved_at = target_at,
which could be in the future. This caused them to be filtered out by the time-based
query in load_display_dataset(). Now using issued_at (when the observation was made)
ensures the timestamps fall within the valid display range.

2026-04-25 21:00:34 +02:00

deploy/systemd

first_commit

2026-04-25 20:35:25 +02:00

docs

first_commit

2026-04-25 20:35:25 +02:00

gibil

Fix: Use issued_at instead of target_at for zero-hour resolved truth timestamps

2026-04-25 21:00:34 +02:00

.gitignore

first_commit

2026-04-25 20:35:25 +02:00

aux | grep db_daemon

Fix: Use issued_at instead of target_at for zero-hour resolved truth timestamps

2026-04-25 21:00:34 +02:00

debug_weather.py

Fix: Use issued_at instead of target_at for zero-hour resolved truth timestamps

2026-04-25 21:00:34 +02:00

main.py

first_commit

2026-04-25 20:35:25 +02:00

requirements.txt

first_commit

2026-04-25 20:35:25 +02:00

ubprocess; result = subprocess.run(['journalctl', '-u', 'astrape-web.service', '-n', '30', '--no-pager'], capture_output=True, text=True); print(result.stdout)"

Fix: Use issued_at instead of target_at for zero-hour resolved truth timestamps

2026-04-25 21:00:34 +02:00

S

Description

No description provided

112 KiB

Languages

Python 100%