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).
25 lines
407 B
Plaintext
25 lines
407 B
Plaintext
Date,Dividends
|
|
2015-07-16,0.003
|
|
2015-10-15,0.018
|
|
2015-12-23,0.083
|
|
2016-04-13,0.06
|
|
2016-07-21,0.018
|
|
2016-10-13,0.026
|
|
2016-12-22,0.041
|
|
2017-04-12,0.049
|
|
2017-07-20,0.049
|
|
2017-10-12,0.038
|
|
2017-12-21,0.059
|
|
2018-04-11,0.061
|
|
2018-07-19,0.071
|
|
2018-08-21,0.3822
|
|
2018-10-11,0.065
|
|
2018-12-28,0.066
|
|
2019-04-10,0.053
|
|
2019-07-18,0.048
|
|
2019-10-10,0.044
|
|
2019-12-30,0.2231
|
|
2020-04-08,0.022
|
|
2020-07-16,0.035
|
|
2020-12-30,0.053
|