Skip to content

Date checking is still awry #32

@JimCircadian

Description

@JimCircadian

Dates are still being dropped due to the wrong extension dates being checked:

[30-05-25 10:58:50 :INFO    ] - Processing 84 dates for train category: 1981-01-31 - 1988-12-31
[30-05-25 10:58:50 :INFO    ] - Including lag of 2 months
[30-05-25 10:58:50 :WARNING ] - 1981-01-31 will be dropped due to missing data 1980-12-31
[30-05-25 10:58:50 :WARNING ] - 1981-01-31 will be dropped due to missing data 1980-11-30
[30-05-25 10:58:50 :WARNING ] - 1981-02-28 will be dropped due to missing data 1980-12-28

Missing data for monthly frequency should always be at month end. There is a bug in the get_extension_dates method and a fix that I didn't test properly.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions