Skip to content

Add support for hourly data #50

Description

@SarahAlidoost

Currently our implementation (encoder_decoder, dataset class and utils) support daily data. To support hourly input data:

  • The encoder_decoder and all model components remain unchanged. The architecture is completely agnostic to whether T=31 or T=744 (24*31). it just sees a temporal dimension to patch. The only model instantiation change is adjusting patch_size (e.g., patch_size=(24, 4, 4) for hourly) and max_days (e.g., max_days=744).
  • The dataset class need changes.
  • The util function add_month_day_dims doesnot work for hourly data. We need another function for hourly data.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions