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).
38 lines
555 B
Plaintext
38 lines
555 B
Plaintext
Date,Dividends
|
|
2012-02-01,0.0
|
|
2012-03-01,0.0
|
|
2012-04-02,0.0
|
|
2012-05-01,0.0
|
|
2012-06-01,0.0
|
|
2012-07-02,0.0
|
|
2012-08-01,0.0
|
|
2012-09-04,0.0
|
|
2012-10-01,0.0
|
|
2012-11-01,0.0
|
|
2012-12-03,0.0
|
|
2013-01-02,0.0
|
|
2013-02-01,0.0
|
|
2013-03-01,0.0
|
|
2013-04-01,0.0
|
|
2013-05-01,0.0
|
|
2013-06-03,0.0
|
|
2013-07-01,0.0
|
|
2013-09-03,0.0
|
|
2013-10-01,0.0
|
|
2013-11-01,0.0
|
|
2013-12-02,0.0
|
|
2014-01-02,0.0
|
|
2014-02-03,0.0
|
|
2014-03-03,0.0
|
|
2014-04-01,0.0
|
|
2014-05-01,0.0
|
|
2014-06-02,0.0
|
|
2014-07-01,0.0
|
|
2014-08-01,0.0
|
|
2014-09-02,0.0
|
|
2014-10-01,0.0
|
|
2014-11-03,0.0
|
|
2015-01-02,0.0
|
|
2016-11-01,0.0
|
|
2016-12-01,0.0
|