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).
23 lines
369 B
Plaintext
23 lines
369 B
Plaintext
Date,Dividends
|
|
2012-12-13,0.026
|
|
2013-12-12,0.863
|
|
2014-07-02,0.019
|
|
2014-10-01,0.078
|
|
2014-12-11,0.169
|
|
2015-04-09,0.04
|
|
2015-07-01,0.054
|
|
2015-10-07,0.067
|
|
2015-12-11,0.019
|
|
2016-04-06,0.057
|
|
2016-07-06,0.089
|
|
2016-10-05,0.041
|
|
2016-12-14,0.037
|
|
2017-04-05,0.002
|
|
2017-07-05,0.026
|
|
2017-12-13,0.089
|
|
2018-07-05,0.003
|
|
2018-12-20,9.051
|
|
2019-03-06,0.3
|
|
2019-10-02,0.001
|
|
2019-12-13,0.001
|