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).
36 lines
590 B
Plaintext
36 lines
590 B
Plaintext
Date,Dividends
|
|
2010-06-22,0.077
|
|
2010-12-21,0.043
|
|
2011-06-21,0.645
|
|
2011-12-21,0.157
|
|
2012-06-21,0.183
|
|
2012-09-21,0.11
|
|
2012-12-21,0.052
|
|
2013-03-21,0.077
|
|
2013-06-21,0.169
|
|
2013-09-20,0.111
|
|
2013-12-18,0.098
|
|
2014-03-25,0.064
|
|
2014-06-24,0.101
|
|
2014-09-23,0.143
|
|
2014-12-23,0.14
|
|
2015-03-25,0.018
|
|
2015-06-24,0.047
|
|
2015-09-23,0.131
|
|
2015-12-23,0.12
|
|
2016-06-22,0.024
|
|
2016-09-21,0.149
|
|
2016-12-21,0.119
|
|
2017-03-23,0.012
|
|
2017-06-22,0.062
|
|
2017-09-21,0.156
|
|
2017-12-21,0.066
|
|
2018-03-22,0.055
|
|
2018-06-21,0.099
|
|
2018-09-14,0.125
|
|
2018-12-18,0.203
|
|
2019-03-21,0.114
|
|
2019-06-14,0.002
|
|
2019-09-25,0.084
|
|
2019-12-13,0.152
|