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).
367 B
367 B
| 1 | Date | Dividends |
|---|---|---|
| 2 | 2014-04-11 | 0.3 |
| 3 | 2014-07-11 | 0.3 |
| 4 | 2014-09-26 | 0.3 |
| 5 | 2015-02-25 | 0.66 |
| 6 | 2015-03-27 | 0.3 |
| 7 | 2015-06-26 | 0.3 |
| 8 | 2015-09-28 | 0.3 |
| 9 | 2016-02-25 | 1.24 |
| 10 | 2016-03-29 | 0.3 |
| 11 | 2016-06-28 | 0.3 |
| 12 | 2016-09-28 | 0.3 |
| 13 | 2017-02-24 | 0.59 |
| 14 | 2017-03-29 | 0.3 |
| 15 | 2017-06-28 | 0.3 |
| 16 | 2017-09-28 | 0.3 |
| 17 | 2018-03-28 | 0.3 |
| 18 | 2018-06-28 | 0.3 |
| 19 | 2018-09-27 | 0.3 |
| 20 | 2019-03-28 | 0.15 |
| 21 | 2019-06-27 | 0.15 |
| 22 | 2019-09-13 | 1.51 |
| 23 | 2019-12-05 | 0.57 |
| 24 | 2020-03-18 | 6.0 |