Lab
Detection Floors and Invisible Presence
Every measurement system has a lower boundary — below that threshold, the thing being measured still exists, but the system calls it zero because looking harder costs too much.
Then check the pattern
A test reports 'none detected'. What does that actually mean?
Nothing exists in the sample Nothing exists above the level where the system stopped looking The test equipment malfunctioned The thing is there but changed form
Answer: Nothing exists above the level where the system stopped looking. A 'none detected' result means the system looked down to a certain level and found nothing above it — not that nothing exists below. Hearing 'none' makes people think absolute zero, but every system stops at a chosen cut-off, and things below that line stay invisible.
Why don't measurement systems just push their lower boundaries as far down as physically possible?
Regulations forbid measuring below certain levels Most things being measured don't exist in tiny amounts Looking harder costs more time, equipment, or expertise than the benefit justifies for most cases Lower boundaries make false positives more common
Answer: Looking harder costs more time, equipment, or expertise than the benefit justifies for most cases. Boundaries sit where they do because pushing lower requires something — longer processing, pricier tools, specialists to read weak signals. For most samples, the standard level works fine. Focusing on noise rather than the cost-benefit trade-off misses what actually determines where systems stop.
A test measures concentration of a substance in a sample. The lower boundary is set fairly high. What happens to samples with small amounts of the substance?
They get flagged for retesting They get reported as 'none detected' even though some is there The test automatically switches to a more sensitive method Results come back as 'inconclusive'
Answer: They get reported as 'none detected' even though some is there. If the substance sits below the boundary, the system reports 'none detected' — not because nothing's there, but because the cut-off was set above where those samples land. The substance exists; the system stopped looking before reaching it. Most systems don't flag borderline cases for extra work unless someone specifically requests it.
You're designing a measurement system. How do you decide where to set the lower boundary?
At the lowest level the equipment can possibly detect Where the cost of looking harder stops being worth it for most samples Where false positives and false negatives balance out mathematically At whatever level professional standards require
Answer: Where the cost of looking harder stops being worth it for most samples. The boundary goes where the trade-off tips: how much does pushing lower cost versus how many samples does it help? For most samples, a higher boundary works fine. For the few below it, that trade-off means being called 'zero'. Mathematical symmetry sounds precise but dodges the real constraint — economics and utility drive the choice.
The lower boundary for an existing test is pushed down using better equipment. What changes for samples previously called 'none detected'?
All samples now get more accurate results Some samples that were called 'none detected' now show a measurable amount The test takes less time to run Samples with high concentrations show even higher numbers
Answer: Some samples that were called 'none detected' now show a measurable amount. Lowering the boundary means seeing things that were always there but below the old cut-off. Samples that got 'none detected' under the old system might now show a number — not because the sample changed, but because the system started looking harder. Results improve only for samples near the old boundary; for everyone else, nothing changes.
← All labs