SMART Data Updates & Better Dataset Awareness
Pre-release
Pre-release
🧠 Smarter Updates, Continued
This release continues the SMART approach introduced earlier and focuses on making updates more thoughtful and efficient.
SILAM Pollen now better understands what data is actually available and updates forecasts accordingly — avoiding unnecessary requests and keeping everything fast and predictable.
SILAM Pollen v0.3.3-beta.1 Release Notes
🚀 What’s New
-
🗂️ Shared runs catalog manager
- Introduced a shared runs catalog manager used by all coordinators.
- Centralizes parsing and caching of
runs/catalog.xml. - Avoids duplicate catalog requests when multiple locations or datasets are used.
- Runs catalog data is cached for 45 minutes.
-
📅 Coverage-aware catalog handling
- Catalog time coverage is now treated as the actual available forecast range:
start→ earliest available forecast start.end→ latest available forecast end.
- This defines clear limits for forecast updates.
- Catalog time coverage is now treated as the actual available forecast range:
-
✂️ Smarter tail updates
- Incremental updates now skip tail requests when no further data exists.
- Prevents unnecessary NCSS requests.
- Update behavior is now fully aware of dataset limits.
-
🏷️ Dataset source tracking
- Forecast data is now internally tagged with the dataset it was sourced from.
- Lays the groundwork for future multi-dataset logic and diagnostics.
🔄 Changes
- Moved all runs catalog logic into a shared manager.
- Removed per-coordinator catalog parsing.
- Improved incremental update logic with clear separation between:
- cache-only rebuilds,
- cache + real network updates.
- Added dataset source markers to internal forecast data.
- Improved internal diagnostics.
🐞 Fixes / Stability
- Fixed cases where cache-only updates were reported incorrectly.
- Reduced unnecessary network traffic.
- Improved debug logs around catalog usage and update decisions.
Full Changelog:
v0.3.2...v0.3.3-beta.1