10.2 Blinding: Difference between revisions
More actions
No edit summary |
// via Wikitext Extension for VSCode |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Cover|10.2 Blinding}} | |||
Blind analysis has emerged as the newest addition to the scientific process to guard against scientists' own confirmation bias, especially in high-precision experiments involving complex analyses, by preventing the scientists from seeing the result of their analysis as they refine and debug the analysis procedure. We illustrate blinding techniques and their dramatic effect through a simple measurement experiment. | Blind analysis has emerged as the newest addition to the scientific process to guard against scientists' own confirmation bias, especially in high-precision experiments involving complex analyses, by preventing the scientists from seeing the result of their analysis as they refine and debug the analysis procedure. We illustrate blinding techniques and their dramatic effect through a simple measurement experiment. | ||
== The Lesson in Context == | == The Lesson in Context == | ||
| Line 22: | Line 20: | ||
{{ContextRelation|In group decision making, when factual evaluation and values evaluation are made by two different groups of people without knowledge of the other, it prevents evaluation motivated by the need to confirm a personal belief.}} | {{ContextRelation|In group decision making, when factual evaluation and values evaluation are made by two different groups of people without knowledge of the other, it prevents evaluation motivated by the need to confirm a personal belief.}} | ||
}} | }} | ||
== Takeaways == | == Takeaways == | ||
| Line 54: | Line 51: | ||
|-|Examples= | |-|Examples= | ||
{{Example | |||
|Muon <math>g</math>−2 Experiment | |||
|This experiment performed highly precise measurements of the magnetic dipole moment of muons to test the theoretical predictions of the currently accepted model of elementary particles. Blinding is done by injecting a secret code into all of the data that would undergo analysis, so that the scientists involved would not make specific choices in the analysis in a way that makes the final value agree with the theoretical prediction. The secret code was kept in a physical locker, the opening of which was highly publicized in the announcement event. Once the data was "unscrambled", the result shows that there is indeed a sizeable deviation of the measured value from the theoretical prediction. | |||
{{LinkCard | |links={{LinkCard | ||
|url=https://www.youtube.com/watch?v=HtdVH1Wp7fs | |url=https://www.youtube.com/watch?v=HtdVH1Wp7fs | ||
|title=Why is the | |title=Why is the Muon <math>g</math>−2 Experiment Shifting Time? | ||
|description=A short video about this process.}} | |description=A short video about this process.}} | ||
{{ | }} | ||
{{Example | |||
|<math>p</math>-hacking and Preregistration | |||
{{LinkCard | |One way in which <math>p</math>-hacking could occur is to choose or alter the analysis method after one has seen the results of that method to be undesirable. As an example, suppose a psychologist performs an experiment with 100 participants, sees that the results are at a statistical significance of <math>p</math> = 0.06, just shy of the <math>p</math> < 0.05 threshold for publication. They then decide to recruit another 100 participants to "improve their results", finally leading to <math>p</math> = 0.04, good enough for publication. This is a form of <math>p</math>-hacking, as <math>p</math>-values can dip below 0.05 as one slowly increases the sample size simply by random chance. To guard against this phenomenon, the sample size of a study is a required item in the preregistration process. | ||
|links={{LinkCard | |||
|url=https://rstudio-pubs-static.s3.amazonaws.com/318451_8dbb1fba8952424fb722196f98587429.html | |url=https://rstudio-pubs-static.s3.amazonaws.com/318451_8dbb1fba8952424fb722196f98587429.html | ||
|title=<math>p</math>-hacking: A Demonstration | |title=<math>p</math>-hacking: A Demonstration | ||
|description=A demonstration of this type of <math>p</math>-hacking.}} | |description=A demonstration of this type of <math>p</math>-hacking.}} | ||
}} | |||
|-|Common Misconceptions= | |||
<!-- Misconceptions must be written with the Misconception template. The first Misconception should have the "first=yes" flag at the end. --> | |||
{{Misconception|Blind analysis is just another name for a double blind experiment.|These concepts are related but distinct. A double blind experiment keeps both participants and administrators from knowing who is in the control or intervention group, primarily in treatment testing with a placebo. Blind analysis instead applies to the analysis process ''once the data has been collected'', hiding the results of interest while analysis decisions are made. Blind analysis may be employed whether or not double blinding is.|first=yes}} | |||
|-|Expanded Learning Goals= | |||
After this lesson, students should | |||
# Attitudes | |||
## One should always be looking for ways that we get things wrong (by fooling ourselves or due to bugs in our reasoning processes) so that we can invent better procedures. | |||
### This is important both for methods long in use and new ones (e.g. big data). | |||
# Concept Acquisition | |||
## '''Blind analysis:''' Making all decisions regarding data analysis before the results of interest are unveiled, such that expectations about the results do not bias the analysis. Usually co-occurs with a commitment to publicize the results however they turn out. | |||
## Examples of analysis decisions for which blind analysis could be useful: | |||
### Stopping rules for when to stop looking for flaws in your experimental design or for computer/math bugs. | |||
### Data selection decisions. | |||
### Decisions about which analysis procedures to use (e.g. grouping decisions). | |||
## Confirmation bias drives the need for blind analysis. | |||
## Confirmation bias is pervasive and doesn't necessarily indicate any fraudulent activity. | |||
## Approaches to reducing confirmation bias other than blind analysis: | |||
### '''Preregistration:''' A research group publicly commits to a specific set of methods and analyses before they conduct their research. | |||
### '''Registered replication:''' A research group (or groups) commits to a specific set of methods and procedures to verify the result of an earlier work (typically with the input of the original research team). Results are publicized regardless of outcome. | |||
### '''Adversarial collaboration:''' Scientists with opposing views agree to all the details of how data should be gathered and analyzed before any of the results are known. | |||
### '''Peer review:''' New results are evaluated by other experts in the same field to determine whether they are valid. This only reduces confirmation bias if reviewers don't share biases. | |||
## Scientists are constantly looking for bugs in scientific practices in order to fix them. Blind analysis is just the latest example of scientists recognizing a bug in their practice (e.g., a way of being fooled) and adjusting practice to account for/remove the bug. | |||
# Concept Application | |||
## Explain why blind analysis might be needed, by explaining the errors that might arise in its absence. | |||
## Recognize when blind analysis is being used and explain what function it serves. Identify situations and decisions that would call for blind analysis. | |||
## Evaluate techniques (e.g., registered replication, adversarial collaboration, peer review) | |||
### for ability to address confirmation bias, and | |||
### in comparison to blind analysis. | |||
## Propose how to use blind analysis for simple studies. | |||
## '''Stretch Goal:''' Propose new practices to solve a new (fictional) problem with current scientific practice. (This is a stretch goal for evaluation, too! Can we invent a new problem with a new scientific practice?) | |||
</tabber> | </tabber> | ||
Latest revision as of 23:41, 11 June 2026
Blind analysis has emerged as the newest addition to the scientific process to guard against scientists' own confirmation bias, especially in high-precision experiments involving complex analyses, by preventing the scientists from seeing the result of their analysis as they refine and debug the analysis procedure. We illustrate blinding techniques and their dramatic effect through a simple measurement experiment.
The Lesson in Context
This lesson offers solutions to potential pitfalls in scientific studies raised in 10.1 Confirmation Bias and 4.2 Finding Patterns in Random Noise. We use a stick measurement activity to illustrate the effects of confirmation bias and to motivate techniques to reduce its effect, especially blind analysis. These techniques are not universally employed in all fields of science today, and students pursuing a scientific career are encouraged to introduce these techniques in their own work.
Takeaways
After this lesson, students should
- Recognize what types of blinding are useful for solving what types of errors.
- Be able to explain why blind analysis might be needed, by explaining the errors that can arise in its absence.
- Recognize when blind analysis is being used and explain what function it serves. Identify situations and decisions in which blind analysis would be useful.
- Be able to evaluate techniques (e.g., registered replication, adversarial collaboration, peer review)
- for ability to address confirmation bias, and
- in comparison to blind analysis.
- Propose how to use blind analysis for simple studies.
Blind Analysis
Double Blind
| Students may confuse blind analysis with a double blind experiment. The latter is used primarily in treatment testing in conjunction with a placebo, such that the patient is prevented from knowing whether they received the real treatment or placebo, and the doctor is also prevented from knowing this fact in order not to inadvertently reveal this fact to the patient through subtle signs. The former type of blinding applies to the analysis process once the data has been collected. In the case of treatment testing, blind analysis may be employed whether or not double blinding is. |
Preregistration
Registered Replication
Registered Reports
Adversarial Collaboration
Peer Review
Muon [math]\displaystyle{ g }[/math]−2 Experiment
[math]\displaystyle{ p }[/math]-hacking and Preregistration
Blind analysis is just another name for a double blind experiment.
After this lesson, students should
- Attitudes
- One should always be looking for ways that we get things wrong (by fooling ourselves or due to bugs in our reasoning processes) so that we can invent better procedures.
- This is important both for methods long in use and new ones (e.g. big data).
- One should always be looking for ways that we get things wrong (by fooling ourselves or due to bugs in our reasoning processes) so that we can invent better procedures.
- Concept Acquisition
- Blind analysis: Making all decisions regarding data analysis before the results of interest are unveiled, such that expectations about the results do not bias the analysis. Usually co-occurs with a commitment to publicize the results however they turn out.
- Examples of analysis decisions for which blind analysis could be useful:
- Stopping rules for when to stop looking for flaws in your experimental design or for computer/math bugs.
- Data selection decisions.
- Decisions about which analysis procedures to use (e.g. grouping decisions).
- Confirmation bias drives the need for blind analysis.
- Confirmation bias is pervasive and doesn't necessarily indicate any fraudulent activity.
- Approaches to reducing confirmation bias other than blind analysis:
- Preregistration: A research group publicly commits to a specific set of methods and analyses before they conduct their research.
- Registered replication: A research group (or groups) commits to a specific set of methods and procedures to verify the result of an earlier work (typically with the input of the original research team). Results are publicized regardless of outcome.
- Adversarial collaboration: Scientists with opposing views agree to all the details of how data should be gathered and analyzed before any of the results are known.
- Peer review: New results are evaluated by other experts in the same field to determine whether they are valid. This only reduces confirmation bias if reviewers don't share biases.
- Scientists are constantly looking for bugs in scientific practices in order to fix them. Blind analysis is just the latest example of scientists recognizing a bug in their practice (e.g., a way of being fooled) and adjusting practice to account for/remove the bug.
- Concept Application
- Explain why blind analysis might be needed, by explaining the errors that might arise in its absence.
- Recognize when blind analysis is being used and explain what function it serves. Identify situations and decisions that would call for blind analysis.
- Evaluate techniques (e.g., registered replication, adversarial collaboration, peer review)
- for ability to address confirmation bias, and
- in comparison to blind analysis.
- Propose how to use blind analysis for simple studies.
- Stretch Goal: Propose new practices to solve a new (fictional) problem with current scientific practice. (This is a stretch goal for evaluation, too! Can we invent a new problem with a new scientific practice?)
Additional Content
You must be logged in to see this content.
