For many ag applications, we want to sample in thermal time, not calendar time, see https://arxiv.org/abs/2506.12885
I've scoped the approach below but am interested to hear if (1) this is a feature that could be considered to incorp in rslearn and (2) if there are any simpler alternatives.
Thanks
Possible approach: Compute GDD stage boundaries externally, create one rslearn window per stage interval, and attach metadata (e.g., field_id, year, stage_idx) so windows can later be grouped. During training, group and sort these stage windows by a shared key (e.g., (field_id, year)) and stack them to form a single stage-aware temporal sample without modifying rslearn’s core pipeline.
For many ag applications, we want to sample in thermal time, not calendar time, see https://arxiv.org/abs/2506.12885
I've scoped the approach below but am interested to hear if (1) this is a feature that could be considered to incorp in rslearn and (2) if there are any simpler alternatives.
Thanks
Possible approach: Compute GDD stage boundaries externally, create one rslearn window per stage interval, and attach metadata (e.g., field_id, year, stage_idx) so windows can later be grouped. During training, group and sort these stage windows by a shared key (e.g., (field_id, year)) and stack them to form a single stage-aware temporal sample without modifying rslearn’s core pipeline.