G2 Science K223, K224 and K225 test interpretation becomes more precise when learners separate the target condition from the signal used to detect it. A positive observation can occur for the wrong reason; a negative observation can occur even when the target is present but below detection. School Science questions often reward exactly this distinction through controls, qualitative tests, apparatus checks and experimental evaluation.
This eighty-third Learner’s Guide develops diagnostic-test evidence: reason about positive signals, negative signals, false positives, false negatives, detection limits and controls without importing specialised statistical formulas the syllabus does not require. It extends Vol 0079 Negative Evidence and Vol 0075 Data Ownership.
The diagnostic chain
- What target condition is being tested?
- What observation counts as a positive signal?
- Can anything else create the same signal?
- Can the target be present without producing a detectable signal?
- What control or second test would distinguish these possibilities?
1. Expected positive
Evidence pattern: the target is present and the test gives its expected signal.
Interpretation: this supports the intended inference when procedure and controls are valid.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
2. Expected negative
Evidence pattern: the target is absent and the test stays negative.
Interpretation: this supports test specificity under the tested condition.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
3. False positive
Evidence pattern: the signal appears even though the target condition is absent.
Interpretation: look for contamination, cross-reaction, background process or non-specific indicator.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
4. False negative
Evidence pattern: the target condition is present but the expected signal does not appear.
Interpretation: look for low concentration, weak sensitivity, wrong timing, degraded reagent or procedure failure.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
5. Positive control succeeds
Evidence pattern: a known-positive sample gives the expected signal.
Interpretation: this supports that the test procedure can detect the target under those conditions.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
6. Positive control fails
Evidence pattern: a known-positive sample gives no signal.
Interpretation: experimental negative results become difficult to trust.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
7. Negative control stays negative
Evidence pattern: a known-negative sample gives no signal.
Interpretation: this supports low background signal and improves interpretation of positives.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
8. Negative control becomes positive
Evidence pattern: a known-negative sample produces the signal.
Interpretation: suspect contamination or poor specificity.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
9. Blank stays negative
Evidence pattern: reagent without sample shows no signal.
Interpretation: this supports that reagent alone is not generating the observation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
10. Blank becomes positive
Evidence pattern: reagent-only condition shows the signal.
Interpretation: treatment positives may be artefacts.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
11. Food-test positive
Evidence pattern: the correct colour change occurs after valid procedure.
Interpretation: support detection of the tested nutrient within the test’s capability.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
12. Food-test negative
Evidence pattern: no characteristic change occurs.
Interpretation: state that the nutrient was not detected rather than making an unlimited absence claim.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
13. Gas-test positive
Evidence pattern: a collected gas gives the characteristic response.
Interpretation: support the gas identity while checking that the test is distinctive and correctly performed.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
14. Gas-test negative
Evidence pattern: the characteristic response is absent.
Interpretation: weaken the proposed identity but inspect gas collection and procedure.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
15. Precipitate positive
Evidence pattern: the expected precipitate forms.
Interpretation: support the relevant ion or reaction inference, considering colour and reagent.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
16. Precipitate absent
Evidence pattern: no precipitate forms.
Interpretation: weaken the target-ion hypothesis only after checking reagent and concentration.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
17. Flame colour clear
Evidence pattern: a characteristic flame colour appears.
Interpretation: support the relevant ion identity with contamination caution.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
18. Flame colour mixed
Evidence pattern: the colour is weak or mixed.
Interpretation: treat identity as uncertain and seek complementary evidence.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
19. Indicator changes
Evidence pattern: the indicator moves into the expected colour range.
Interpretation: support the corresponding pH condition within indicator resolution.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
20. Indicator unchanged
Evidence pattern: no colour shift is seen.
Interpretation: conclude no detected crossing of the indicator range, not necessarily no pH change.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
21. Current detected
Evidence pattern: a correctly connected circuit gives current.
Interpretation: support electrical conduction under those conditions.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
22. No current
Evidence pattern: meter reads zero.
Interpretation: check circuit, range and contacts before concluding non-conduction.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
23. Lamp lights
Evidence pattern: the lamp visibly glows.
Interpretation: support sufficient current for visible operation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
24. Lamp dark
Evidence pattern: no visible light.
Interpretation: do not equate automatically with exactly zero current.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
25. Temperature rise detected
Evidence pattern: sensor records a rise beyond resolution.
Interpretation: support heating in the measured system.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
26. No temperature rise
Evidence pattern: sensor reading stays unchanged.
Interpretation: state no detectable change; small changes may lie below resolution.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
27. Oxygen signal rises
Evidence pattern: a suitable photosynthesis setup shows increased oxygen.
Interpretation: support net oxygen production under those conditions.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
28. No oxygen rise
Evidence pattern: no detectable increase appears.
Interpretation: weaken a strong net-production claim while considering respiration and sensitivity.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
29. Carbon dioxide signal rises
Evidence pattern: a respiration setup shows increased carbon dioxide.
Interpretation: support production when controls are appropriate.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
30. No carbon dioxide rise
Evidence pattern: no detected increase.
Interpretation: keep conclusion bounded by duration, system closure and sensitivity.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
31. Enzyme product detected
Evidence pattern: assay shows expected product.
Interpretation: support enzyme activity under tested conditions.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
32. No enzyme product
Evidence pattern: assay stays negative.
Interpretation: check enzyme, substrate, pH, temperature, time and assay function before strong absence claims.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
33. Seed germinates
Evidence pattern: germination occurs.
Interpretation: show that required conditions were sufficiently met for that seed.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
34. Seed does not germinate
Evidence pattern: no germination occurs.
Interpretation: do not identify one missing factor without further evidence.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
35. Treatment response positive
Evidence pattern: treatment group differs from a comparable control.
Interpretation: support an association with treatment and assess causal design.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
36. Treatment response absent
Evidence pattern: treatment and control are similar.
Interpretation: weaken a large-effect claim while considering sample size and measurement noise.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
37. Behavioural response positive
Evidence pattern: organism changes behaviour after stimulus.
Interpretation: support responsiveness without inferring human-like motive.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
38. Behavioural response absent
Evidence pattern: no visible change.
Interpretation: consider threshold, delay and observation sensitivity.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
39. Magnetic response positive
Evidence pattern: test object is attracted.
Interpretation: support magnetic interaction under the setup.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
40. No magnetic response
Evidence pattern: no attraction is observed.
Interpretation: consider field strength and distance before absolute claims.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
41. Image on screen
Evidence pattern: a clear image forms at predicted position.
Interpretation: support the real-image model for the setup.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
42. No image on screen
Evidence pattern: no clear image forms.
Interpretation: check alignment, object distance, screen position and model assumptions.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
43. Sound detected
Evidence pattern: sound is heard or measured.
Interpretation: support signal reaching the detector.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
44. No sound detected
Evidence pattern: no signal is heard or measured.
Interpretation: bound the conclusion by detector sensitivity and frequency range.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
45. Force detected
Evidence pattern: sensor records force.
Interpretation: support interaction on the measured axis.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
46. Zero force reading
Evidence pattern: sensor shows zero.
Interpretation: state no detectable force on that sensor axis and check calibration/orientation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
47. Control unexpectedly positive
Evidence pattern: control shows the treatment-like signal.
Interpretation: suspect background effect, contamination or non-specific test.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
48. Control appropriately negative
Evidence pattern: control lacks signal while treatment has it.
Interpretation: strengthen attribution to treatment if other conditions are comparable.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
49. Repeated positives
Evidence pattern: independent repeats show the same positive result.
Interpretation: increase confidence in repeatability but not automatically validity.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
50. Repeated negatives
Evidence pattern: sensitive repeats remain negative.
Interpretation: strengthen evidence against a detectable effect in that tested range.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
51. Mixed repeats
Evidence pattern: some repeats positive and some negative.
Interpretation: investigate threshold, method consistency and real variability.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
52. Threshold behaviour
Evidence pattern: signal appears only above a certain input.
Interpretation: support a threshold-like response.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
53. Saturation behaviour
Evidence pattern: signal stops increasing beyond a level.
Interpretation: support plateau or saturation rather than absence of the target.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
54. Dose response
Evidence pattern: larger input gives larger measured response.
Interpretation: strengthen a graded relationship claim within range.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
55. No dose response
Evidence pattern: different doses give similar output.
Interpretation: consider ceiling, floor, saturation or insensitive measurement.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
56. Correct time window
Evidence pattern: signal appears when the mechanism predicts it.
Interpretation: timing strengthens interpretation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
57. Too-early negative
Evidence pattern: measurement occurs before expected response.
Interpretation: negative evidence is weak.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
58. Adequate-time negative
Evidence pattern: signal still absent after sufficient time.
Interpretation: negative evidence becomes stronger if manipulation and detection are valid.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
59. Direct measure positive
Evidence pattern: a direct measurement detects the target quantity.
Interpretation: usually stronger for that quantity than a vague proxy.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
60. Proxy positive
Evidence pattern: an indirect indicator changes.
Interpretation: interpret through the relationship between proxy and target.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
61. Direct-proxy conflict
Evidence pattern: direct measure and proxy disagree.
Interpretation: compare validity, calibration and what each actually measures.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
62. Two independent positives
Evidence pattern: different tests support the same target through different mechanisms.
Interpretation: confidence increases when errors are genuinely independent.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
63. Two independent negatives
Evidence pattern: different sensitive tests both fail to detect target.
Interpretation: negative evidence strengthens within both detection limits.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
64. Tests disagree
Evidence pattern: one test is positive and another negative.
Interpretation: compare sensitivity, specificity, timing and target definition rather than averaging.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
65. Sensitive test
Evidence pattern: method can detect small amounts or effects.
Interpretation: a negative result is more informative about absence above its threshold.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
66. Specific test
Evidence pattern: signal is strongly tied to target.
Interpretation: a positive result is more informative.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
67. Sensitive but non-specific
Evidence pattern: test catches targets but also other conditions.
Interpretation: negative can be useful; positive needs confirmation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
68. Specific but insensitive
Evidence pattern: positive is convincing but small targets may be missed.
Interpretation: negative is weaker.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
69. Detection limit
Evidence pattern: effects below a size cannot be reliably seen.
Interpretation: write not detected rather than zero.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
70. Resolution limit
Evidence pattern: instrument steps are coarse.
Interpretation: small differences can appear identical.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
71. Observer limit
Evidence pattern: human sight or hearing is the detector.
Interpretation: weak signals may be missed.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
72. Contamination
Evidence pattern: target-like material enters sample unintentionally.
Interpretation: positive may be false.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
73. Cross-reaction
Evidence pattern: another substance produces same signal.
Interpretation: specificity falls.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
74. Degraded reagent
Evidence pattern: test chemistry no longer works properly.
Interpretation: negative may be false.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
75. Calibration succeeds
Evidence pattern: instrument matches a known reference.
Interpretation: support accuracy near that calibration range.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
76. Calibration fails
Evidence pattern: reference reading is wrong.
Interpretation: all dependent measurements need caution.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
77. Sample mix-up
Evidence pattern: labels are swapped.
Interpretation: diagnosis attaches to wrong condition until data ownership is repaired.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
78. Wrong timing
Evidence pattern: sample is tested outside valid response window.
Interpretation: positive or negative classification may misrepresent process.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
79. Wrong temperature
Evidence pattern: test system is outside suitable temperature.
Interpretation: signal may weaken or disappear.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
80. Wrong pH
Evidence pattern: test system is outside functional pH.
Interpretation: enzyme or indicator may fail.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
81. Insufficient sample
Evidence pattern: too little material is tested.
Interpretation: signal may fall below detection.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
82. Excess sample
Evidence pattern: signal saturates or obscures differences.
Interpretation: positive result loses quantitative meaning.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
83. Background noise
Evidence pattern: unrelated variation is large.
Interpretation: small signals may be indistinguishable.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
84. Signal-to-noise
Evidence pattern: true effect is small relative to variation.
Interpretation: single classifications are weak.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
85. Binary threshold
Evidence pattern: continuous measurement is turned into yes/no at a cut-off.
Interpretation: near-boundary cases can flip labels.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
86. One positive overclaim
Evidence pattern: one signal is treated as proof.
Interpretation: ask what else can generate the signal.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
87. One negative overclaim
Evidence pattern: one negative is treated as proof of absence.
Interpretation: ask what could hide a true signal.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
88. Diagnostic chain
Evidence pattern: sample leads to test, signal and inference.
Interpretation: verify every arrow rather than jumping from reagent to conclusion.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
89. MCQ positive distractor
Evidence pattern: option makes a positive test overly specific.
Interpretation: reject if another cause can produce the signal.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
90. MCQ negative distractor
Evidence pattern: option says absent because no signal.
Interpretation: reject if sensitivity or procedure does not justify absolute absence.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
91. Structured response
Evidence pattern: question asks what result shows.
Interpretation: state observation, inference and relevant limitation in that order.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
92. Evaluation
Evidence pattern: test classifications are inconsistent.
Interpretation: diagnose calibration, threshold, contamination or observer variation.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
93. Combining evidence
Evidence pattern: two different observations support one conclusion.
Interpretation: show what each contributes independently.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
94. Conflicting evidence
Evidence pattern: one observation supports and one weakens hypothesis.
Interpretation: weight by validity and diagnostic strength.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
95. Scope
Evidence pattern: test is valid only in a defined range or condition.
Interpretation: keep conclusion inside that range.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
96. Final rule
Evidence pattern: ask what can create a positive and what can hide a true target.
Interpretation: this is the practical core of sensitivity and specificity reasoning.
For practice, draw target → test → signal → inference and identify which arrow could fail. Then design one control, repeat or complementary observation that would reduce the ambiguity. The goal is to reason about test quality, not merely memorise a positive/negative label.
Positive and negative controls
A positive control asks whether the procedure can produce the expected signal when the target is known to be present. A negative control asks whether the procedure stays quiet when the target is absent. When these controls fail, the experimental result becomes harder to interpret. Controls therefore diagnose the diagnostic method itself.
Links
Use the Science Hub, Vol 0061 Claim–Evidence Mapping, Vol 0072 Verification Asymmetry, the Examination Craft hub and the PSLE Learner’s Guide.
Official-source discipline
For current K223–K225 assessment objectives and paper structure, use the official SEAB 2027 G2 syllabus directory and linked Science syllabus. If SEAB updates the syllabus, the current official document takes priority.
Final rule
A test result is not the target itself. Ask what else can create a positive signal and what can hide a true target from detection. Strong Science answers reason through sample, procedure, signal and inference before deciding what the evidence actually establishes.
