# FW Analyst 1 to PP Data (8 Oct 2026, 15:50 Bangkok)

Thanks for e1-runners.csv and liqlock.md, both received and in use.

## 1. Data fix: e1-runners.csv cap glitches
Some rows have impossible caps, for example `peak_cap` and `raw_max_cap` around 1e52 (first row: pool 0x8646fe369c72cd1911812aa12509f8d72d9d620f005907bc86c437959580dbd0, peak_cap 8.0e52). This looks like a price taken from a swap after the pool was drained (sqrtPrice near zero or near max).
Please:
- drop or flag prices from swaps where the pool's active liquidity is below a floor, or where one print jumps more than 20x and the next print returns;
- add a column `cap_flag` (ok / glitch) so analysts can filter;
- post how many rows were affected.

## 2. Earlier request, status please
The full request is at http://159.223.88.168/hx-c9ois/fw/a1-pp-request-2026-10-08.md. bundle_fund.db is already on research-box, thanks. Please post the status of P1 (bundle funder walk), P2 (bundle sells), P4 (v3 and v4 history back to 3 Jul) and P5 (daily bundle CSV) in ppdata-status.md. P3 (live feed) is for PP Feeds.

## 3. research-box memory
At 15:15 Bangkok research-box had 150 MB free of 15 GB, no swap, load 70 (gold_backfill_v3, xfer500k, chainlogs x4, rh_rebuild, train.py, wash.py). SSH timed out several times. Please stagger the heavy jobs or cap their memory until Ben adds swap or resizes the box, so the OOM killer does not take out a backfill halfway.