Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Effect 1709: ML5 Risen RP:P replication p = .02, not p > .05

Abierto
  • ¿Algo no está bien?
#145 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
data

Línea de trabajo

Find the record with fred_id ManyLabs5_1g (effect 1709) in the FReD data and check its pval_type_r and pval_value_r fields against Table 4 of Ebersole et al. (2020). The proposed change is to set the type to e (=) and the value to 0.02 while keeping r = −.04. Done means the record matches the cited table, and the maintainers confirm the inequality-versus-equality coding convention first, since the thread has no reply yet.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Effect 1709 (fred_id = ManyLabs5_1g) records pval_type_r = g (>), pval_value_r = 0.05, despite a published replication p-value of .02 for this arm.

The record identifies the ML5 RP:P-protocol replication of Risen & Gilovich (2008), original Study 6: study_r = 7_RPP, n_r = 2811, replication DOI 10.1177/2515245920958687. Its recorded es_type_r = r, es_value_r = -0.04 agrees with the overview's tables.

Source evidence in Ebersole et al. (2020):

  • Table 3, p. 11: ML5 RP:P-protocol arm, N = 2,811, r = −.04, 95% CI [−.08, −.01]. The original effect is r = +.19.
  • Table 4, p. 14: Risen & Gilovich → RP:P protocol, k = 1, r = −.04 [−.08, −.01], p = .02 in the p-value column. The adjacent P_orig column also has .02 but represents a different metric.
  • The all-protocols and revised-protocol results have p = .20 and .87, respectively; neither is the endpoint for effect 1709.

Two independent source coders (Opus and a blind Codex agent) agreed on N, estimate, CI, p-value, and direction. I also checked the Table 4 image. The printed p-value is rounded to two decimal places; sidedness is inferred from the estimate and zero-excluding 95% CI rather than explicitly labelled in the table.

Please change the replication p-value to pval_type_r = e (=), pval_value_r = 0.02, retaining r = −.04. This makes significance against zero true under a two-sided p < .05 endpoint. It remains unsuccessful in reproducing the original direction, so reported_success = failed need not change.

The overview's narrative on pp. 10–11 says none of the RP:P-protocol replications were significant, which conflicts with this negative significant numerical result if read as significance against zero. The paper defines successful replication using significance in the original direction on p. 8. That may explain the narrative, but the reason for FReD's inequality coding is unconfirmed. Footnote 5 also distinguishes individual-report estimators from the overview meta-analyses; the recommendation here is specific to the cited overview and the matching N and effect estimate.

Lenguaje dominante
HTML
Estrellas
1
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forrtproject/fred-data

Todos los issues de forrtproject/fred-data

Issues similares

Más issues de Data Engineering

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.