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).
24 lines
387 B
Plaintext
24 lines
387 B
Plaintext
Date,Dividends
|
|
2014-06-27,0.067
|
|
2014-09-29,0.046
|
|
2014-12-17,0.054
|
|
2015-03-30,0.05
|
|
2015-06-29,0.072
|
|
2015-09-29,0.053
|
|
2015-12-17,0.061
|
|
2016-03-30,0.071
|
|
2016-06-29,0.055
|
|
2016-09-29,0.048
|
|
2016-12-14,0.189
|
|
2017-03-30,0.086
|
|
2017-06-29,0.055
|
|
2017-09-28,0.062
|
|
2017-11-29,0.039
|
|
2017-12-27,0.153
|
|
2018-03-28,0.041
|
|
2018-06-28,0.013
|
|
2018-09-27,0.05
|
|
2018-12-27,0.175
|
|
2019-03-28,0.072
|
|
2019-06-18,0.179
|