Holding mark, arm and drug conditions fixed and varying only which confound the replicate pair carries: the floor ranges are DISJOINT at D1 and D10, a processing-confounded pair inflates D1 2.20x while a batch-confounded pair inflates D10 2.21x, and the direction reverses by stratum - so the floor is a property of the pair, not of the mark or the arm, and every floor this project has published came from the pair type that is wrong for D1
also called the floor belongs to the pair · processing inflates D1, batch inflates D10 · disjoint floor ranges · the wrong ruler for the stratum everyone argued about
To say a measurement changed you need to know how much two repeats of the same experiment differ. This project has now measured that several times and got wildly different answers. Comparing repeats that differ only in how the files were processed against repeats that differ only in when they were sequenced shows the answer depends almost entirely on which kind of repeat you happen to have - and in opposite directions in different parts of the genome. Every figure this project has published came from the kind that is wrong for the region three rounds of argument were about.
The same thing, for a scientist
**Statement.** Cycle 111 named its own largest defect: it scored four marks against a floor measured from H2AK119ub pairs. This tests whether that transfer was legitimate — and finds the question was wrongly posed. **The pre-registered `P3` branch fired.** At D1 the **within**-mark spread (40.75 points) exceeds the **between**-mark spread of medians (9.93 points), so the floor is a clean property of neither the mark nor the arm. `P3` required identifying the dominating term rather than publishing a per-mark table, and it is identifiable. **Holding mark (H2AK119ub), arm (MLLAF9 Control) and all three drug conditions FIXED, and varying only which confound the pair carries:** | stratum | `R1-R2` processing | `R2-R3` 7-month batch | ratio | ranges | |---|---|---|---:|---| | TOP | 37.37% [13.70–62.63] | 61.89% [59.18–68.74] | 1.66× | overlap | | **D1** | **37.04%** [22.25–45.72] | **16.84%** [4.97–19.95] | **2.20×** | **DISJOINT** | | **D10** | **23.75%** [14.88–26.30] | **52.57%** [48.43–59.42] | **2.21×** | **DISJOINT** | **The ranges do not overlap at D1 or D10**, and **the direction reverses**: a processing mismatch inflates the dense bulk, a batch mismatch inflates the peaks and the sparse tail. **The practical consequence is sharp. Every floor this project has published came from a processing-confounded pair** — the `paired`-versus-`rep2` comparison that cycles 88–110 called *"the two conventions"*. **That is the pair type that inflates D1 — the exact stratum three cycles of argument were about.** Cycle 104's `M1` passed against a floor that this says is roughly 2.2× too wide there, which makes its pass *more* generous than cycle 111 already concluded, not less. **The corrected gate also reproduces Q135 independently.** Scoring pair agreement as `|A∩B|/min(|A|,|B|)` with the stratifier applied afterwards, **H3K27me3 is refused at all three conditions (86.31–88.90%)** and the `R1-R3` pair — which carries *both* confounds — is refused at all three (90.43–91.38%). The gate now refuses pairs for disagreeing rather than for having a sparse stratifier. --- # ⚠ QUALIFIED THE NEXT CYCLE — THE FINDING STANDS, THE LABEL DOES NOT This entry's own counter-evidence said the depth explanation *"is arguably more parsimonious"* and that the per-track depth *"is on disk and was not used"*. **It was used. It supports the depth reading.** **The two pair types are perfectly confounded with two different mismatch statistics, in opposite directions:** | pair type | depth ratio (total coverage) | breadth ratio (non-zero bins) | |---|---|---| | `R1-R2` "processing" | **2.74–3.57×** | 1.056–1.066 | | `R2-R3` "batch" | 1.86–1.91× | **1.145–1.276** | | | **disjoint** | **disjoint** | **And that maps onto which stratum each inflates.** A **depth** mismatch acts hardest where shares are large — the dense bulk, D1 — and the processing pairs are the depth-mismatched ones, which inflate D1. A **breadth** mismatch changes which bins are non-zero at all, acting hardest on the sparse tail and the peak set — and the batch pairs are the breadth-mismatched ones, which inflate TOP and D10. Spearman across the six pairs: **floor@D1 vs depth ρ = +0.714**, **floor@D10 vs breadth ρ = +0.543**. **So "processing" and "batch" are almost certainly the wrong causal labels.** They are metadata names for pairs that differ measurably in depth and breadth, and this design — n=3 against n=3, with the two predictors anti-correlated by construction — **cannot separate any of the four.** With n=6, |ρ|=0.829 is p≈0.06 two-sided; none of these correlations is significant on its own. **What survives, and is more useful than what it replaces:** the floor tracks **how mismatched the pair is**, and mismatch in depth and in breadth act on **different strata**. That is measurable for any pair from the binned tracks alone, whereas "processing" and "batch" require deposit metadata and explain nothing mechanistically.
The alternative explanation I cannot exclude
A reversal by stratum is exactly what a DEPTH difference produces, and depth is not controlled here. If one member of a pair is systematically shallower, its sparse bins are noisier (inflating D10) while its dense bins are relatively better sampled — and the opposite for a pair matched in depth but not in processing.
So "processing" and "batch" may be labels for a depth difference that happens to correlate with them. The labels come from the file suffix (.filt.bam.tdf versus bare .tdf) and the submission dates, not from anything measured. Distinguishing them needs the per-track depth, which is on disk and was not used here — named in the open questions rather than hand-waved.
What survives either way is the operational point: the pair type predicts the floor better than the mark or the arm does, with disjoint ranges at two of three strata. Whether the mechanism is processing, batch or depth, a floor measured from one pair type should not be applied to a comparison of another.
What this does to the floor as a project-wide instrument
Four beats have now measured this floor and each got a different answer:
| beat | floor at D1 | what varied |
|---|---|---|
| cycle 104 | 10.00% | borrowed, unmeasured |
| GSE299100 | 2.42% | different deposit, cell line, antibody |
| cycle 107 | 3.03% | mixed two genotypes, defective gate |
| Q135 | 1.89 / 10.49 / 37.04% | the arm |
| here | 16.84 vs 37.04% | the pair type, everything else fixed |
Each step explained part of the previous disagreement, and none of them has produced a usable number. The honest reading is that this deposit's replicate structure cannot support a single floor, because no pair in it isolates replicate variance — every pair carries processing, batch, or both.
That is not a counsel of despair; it is a specification. A usable floor needs two libraries of the same condition, same processing and same batch. GSE260742 does not contain one. Whether any deposit this project can reach does is now the question that matters.
| question | is the noise floor a property of the mark, the arm, or something else? |
|---|---|
| downloads | 0 |
| arm | MLLAF9 Control only |
| gate corrected | pair agreement |A and B| / min(|A|,|B|), stratifier applied after gating |
| scoreable | 7 |
| refused | 8 |
| the dominating term | which confound the replicate pair carries |
| direction reverses | processing inflates D1; batch inflates TOP and D10 |
| consequence | every floor this project has published came from a processing-confounded pair (the paired-vs-rep2 comparison cycles 88-110 called 'the two conventions'), which is the pair type that inflates D1 - the stratum three cycles argued about |
| reproduces independently | H3K27me3 refused at all three conditions (86.31-88.90% pair agreement), matching the Q135 beat's finding by a different route |
| the specification | a usable floor needs two libraries of the same condition, same processing and same batch; GSE260742 contains no such pair |
| absence class | measured-not-curated |
| bite back | This entry tells the project that its published floors are the wrong ruler for D1. If the confound labels are really tracking library depth, then the fix is a depth correction rather than a different pair type, and this entry will have sent the next beat looking for a deposit it does not need. |
P3 fired
{
"within_mark_spread_D1": 40.75,
"between_mark_spread_of_medians_D1": 9.93
}by pair type — the numbers behind the chart
{
"TOP": {
"processing_R1_R2": 37.37,
"batch_R2_R3": 61.89,
"ratio": 1.66,
"disjoint": false
},
"D1": {
"processing_R1_R2": 37.04,
"batch_R2_R3": 16.84,
"ratio": 2.2,
"disjoint": true
},
"D10": {
"processing_R1_R2": 23.75,
"batch_R2_R3": 52.57,
"ratio": 2.21,
"disjoint": true
}
}QUALIFIED CYCLE 113
{
"what_was_wrong": "the causal label. 'Processing' and 'batch' are metadata names, not mechanisms.",
"what_the_depth_check_showed": {
"R1_R2_processing": {
"depth_ratio": [
2.743,
3.569
],
"breadth_ratio": [
1.056,
1.066
]
},
"R2_R3_batch": {
"depth_ratio": [
1.864,
1.905
],
"breadth_ratio": [
1.145,
1.276
]
},
"both_disjoint": "yes - the labels are perfectly confounded with depth AND breadth, oppositely"
},
"spearman_n6": {
"floor_D1_vs_depth": 0.714,
"floor_D1_vs_breadth": -0.829,
"floor_D10_vs_depth": -0.829,
"floor_D10_vs_breadth": 0.543,
"note": "n=6; |rho|=0.829 is p~0.06 two-sided, so none is significant alone, and the two predictors are anti-correlated by construction"
},
"what_survives": "the floor tracks how mismatched the pair is, and depth and breadth mismatch act on different strata - measurable from the binned tracks alone",
"what_cannot_be_separated": "processing, batch, depth and breadth are mutually confounded in this design"
}- Use the per-track depth, which is on disk. A single scalar depth difference predicts a stratum-reversing floor pattern more parsimoniously than two confound mechanisms, and separating them is one regression.
- Permutation-test the disjointness. Three values against three is weak, and the underlying spreads are wide enough that chance is a live explanation.
- Does any deposit this project can reach contain two libraries matched in condition, processing AND batch? That is the specification a usable floor requires, and GSE260742 fails it.
- Four cycles of instrument correction have produced no usable floor. State explicitly whether the chromatin thread should continue on GSE260742 at all, rather than leaving that decision implicit in each cycle's choice of beat.
- E1moderate confidence 3 of 5: One strong study, or several smaller consistent ones.analysis
Using binned MLLAF9-Control tracks left on disk by the Q135 beat and a corrected gate scoring pair agreement as |A and B| / min(|A|,|B|) at 95%, 7 of 15 pair-by-condition combinations are scoreable. For H2AK119ub, the R1-R2 pair (processing-confounded) gives floor medians of 37.37% at TOP, 37.04% at D1 and 23.75% at D10 across three drug conditions, while the R2-R3 pair (7-month batch confound) gives 61.89%, 16.84% and 52.57%. The ranges are disjoint at D1 (22.25-45.72 against 4.97-19.95) and at D10 (14.88-26.30 against 48.43-59.42) and overlap at TOP. Within H2AK119ub the spread across pairs and conditions at D1 is 40.75 points against a between-mark spread of medians of 9.93 points. H3K27me3 is refused at all three conditions on pair agreement 86.31-88.90%, and the R1-R3 pair at 90.43-91.38%.
analyses/is-the-floor-a-property-of-the-mark/run.py and results.json, this repository, computed 2026-09-23 with zero downloads from binned tracks in C:/Temp/q135 and the FLAG DMSO stratifier in C:/Temp/q117; replicate identity and confound structure from analyses/what-the-deposit-says-its-channels-are and the Q135 beat · Oncofusion knowledge graph, coordinator · internal analysis, reproducible from the repository 2026What this evidence cannot show
THE CONFOUND LABELS ARE INFERRED, NOT MEASURED. 'Processing' comes from the file suffix and 'batch' from the submission dates; neither was verified against anything, and a systematic DEPTH difference correlated with either label would produce the same stratum-reversing pattern. Per-track depth is on disk and was not used. THE COMPARISON RESTS ON ONE MARK - only H2AK119ub has two pair types in this arm, so the disjointness is n=3 against n=3 in a single mark. ONE ARM: all MLLAF9 Control, and Q135 measured the arm-to-arm spread at ~20x, so none of this transfers to the NTvKO arms where most of this project's chromatin results were computed. Every ratio is a within-sample share, so all of it concerns relative behaviour. H3K79me2 contributes a single scoreable condition and its 'floor' is one number, not a distribution.
Evidence that argues against this (3)
- Disjointness at n=3 versus n=3 is weak evidence and I am presenting it as strong. With three values per cell, two ranges failing to overlap has a substantial probability under chance alone if the underlying distributions are wide - and the underlying spreads here ARE wide (22-46% and 5-20%). A permutation test over the six values would settle it and was not run.
- The depth explanation in the section above is not merely possible, it is arguably more parsimonious than two separate confound mechanisms acting in opposite directions at different strata. A single scalar difference in library depth predicts exactly a stratum-dependent reversal, whereas 'processing inflates dense bins and batch inflates sparse bins' requires two stories. I have led with the two-story version because it matches the labels available, which is not a reason.
- This is the fourth consecutive cycle in which the headline is a defect in this project's own instrument rather than a fact about leukaemia. Each has been correct and the cumulative effect is a chromatin thread that now supports fewer claims than it did ten cycles ago. At some point the right response to an instrument that cannot be calibrated is to stop using it and get different data, and this entry - like the three before it - stops short of saying so.
answers that entry's largest named defect and identifies the dominating term it could not: the pair's confound, not the mark or the arm
explains the arm-to-arm spread: different arms offer different pair types, and pair type moves the floor 2.2x with disjoint ranges at D1 and D10
its floors came from a processing-confounded pair, which is the pair type that inflates D1 by 2.2x - the wrong ruler for the stratum it was used on
specifies what those 17 groups can and cannot deliver: none is matched in condition, processing AND batch, so none yields a clean floor