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).
17 lines
266 B
Plaintext
17 lines
266 B
Plaintext
Date,Dividends
|
|
2011-12-29,0.067
|
|
2012-12-28,0.067
|
|
2013-12-30,0.036
|
|
2014-03-31,0.0
|
|
2014-12-30,0.683
|
|
2015-12-30,0.57
|
|
2016-12-29,0.386
|
|
2017-12-28,0.063
|
|
2018-12-28,0.473
|
|
2019-01-31,0.033
|
|
2019-02-28,0.03
|
|
2019-03-29,0.032
|
|
2019-04-30,0.032
|
|
2019-12-30,0.329
|
|
2020-12-30,0.199
|