Some dump files carry a trailing 'ctime' column: an older pipeline appended a FULL re-download of the symbol per download (up to ~28 vintages per date, 2019-2022). The consumer keeps the last row per date, so it silently used stale (~2021) vintages where Yahoo later revised values. scripts/clean_multivintage.py keeps, per date, the rows from the newest ctime (event files keep distinct same-day amounts; history/split keep the single newest row), drops the ctime column, sorts by date. Applied to the data root and overrides/frozen (which carried the same artifact): 1,065 files, 2,202,712 stale rows dropped. Also: stripped 3 UTF-8 BOMs (teg/lo/krft), refreshed the event backup with the cleaned files, and re-ran the double-listing scan: category C (83 symbols, 18,636 repeated within-file rows) is fully explained by the multi-vintage artifact and is now gone; A (6,589 pairs, corrected) and B (12,366 pairs, open review list) are unchanged. Whole-set structural QC after cleaning: 0 duplicate dates, 3 syms/15 rows of OHLC invariant violations, 15 syms/2,897 rows of non-positive prices (mostly long-delisted tickers), 8 unsorted files (reader sorts).
35 lines
675 B
Plaintext
35 lines
675 B
Plaintext
Date,Dividends
|
|
2014-02-26,0.110000
|
|
2014-05-28,0.110000
|
|
2014-08-27,0.125000
|
|
2014-11-24,0.125000
|
|
2015-02-26,0.125000
|
|
2015-05-27,0.125000
|
|
2015-08-26,0.125000
|
|
2015-11-24,0.125000
|
|
2016-02-25,0.125000
|
|
2016-05-25,0.135000
|
|
2016-08-26,0.135000
|
|
2016-11-16,0.135000
|
|
2017-02-24,0.135000
|
|
2017-05-26,0.135000
|
|
2017-08-28,0.135000
|
|
2017-11-29,0.135000
|
|
2018-02-27,0.135000
|
|
2018-05-30,0.135000
|
|
2018-08-29,0.135000
|
|
2018-11-29,0.135000
|
|
2019-02-27,0.135000
|
|
2019-05-30,0.135000
|
|
2019-08-29,0.135000
|
|
2019-11-25,0.135000
|
|
2020-02-27,0.135000
|
|
2020-05-28,0.135000
|
|
2020-08-28,0.135000
|
|
2020-11-27,0.135000
|
|
2021-02-25,0.135000
|
|
2021-05-27,0.135000
|
|
2021-08-30,0.135000
|
|
2021-11-29,0.075000
|
|
2022-02-25,0.075000
|