Description
The internal SE calendar bundled with AlertTools contains an invalid start date for epidemiological week 201815.
Current stored value:
- SE 201815
- Inicio:
2018-04-04
- Termino:
2018-04-14
Expected:
- Inicio:
2018-04-08
- Termino:
2018-04-14
The full calendar was audited from 2010 through 2026 (887 epiweeks), and 201815 was the only mismatch.
The expected value was independently confirmed by:
AlertTools::episem()- PostgreSQL
epi_week()
- Python
epiweeks
The stored row also creates an 11-day epidemiological week and overlaps SE 201814 from 2018-04-04 through 2018-04-07.
Both packaged calendar files contain the same incorrect value:
data/SE.rdaR/sysdata.rda
Expected
- correct the start date of SE
201815 to 2018-04-08;
- keep
2018-04-14 as the end date;
- update both packaged calendar objects consistently;
- add regression tests around SE
201814–201816;
- add a full-calendar consistency test against
episem() to prevent similar drift.
Description
The internal
SEcalendar bundled with AlertTools contains an invalid start date for epidemiological week201815.Current stored value:
2018-04-042018-04-14Expected:
2018-04-082018-04-14The full calendar was audited from 2010 through 2026 (887 epiweeks), and
201815was the only mismatch.The expected value was independently confirmed by:
AlertTools::episem()epi_week()epiweeksThe stored row also creates an 11-day epidemiological week and overlaps SE
201814from2018-04-04through2018-04-07.Both packaged calendar files contain the same incorrect value:
data/SE.rdaR/sysdata.rdaExpected
201815to2018-04-08;2018-04-14as the end date;201814–201816;episem()to prevent similar drift.