Add per-effect focal-effect flag (is_focal / focal_role) for original–replication pairs - #131
Open
LukasWallrich wants to merge 1 commit into
Open
Add per-effect focal-effect flag (is_focal / focal_role) for original–replication pairs#131LukasWallrich wants to merge 1 commit into
LukasWallrich wants to merge 1 commit into
Conversation
Flags, for each of the 2164 FReD effects, whether it is the focal effect of its replication pair (the single effect the replication targeted). Focal effects resolved per pair by a tiered rule (single_effect -> abstract match -> outcome_quote match -> replication-report reading; LLM tiers use gemini-flash-lite-latest two-pass semantic matching, report tier is human-directed agent reading with cited evidence). Pairs with no single identifiable focal claim are classified as constituent_set, target_absent, focal_in_sibling (FReD-fragment pairs whose focal effect lives in a sibling fred_id), or not_applicable (association-matrix bundles); no pair remains needs_review. Effects outside the coded universe are uncoded. Exactly one is_focal=TRUE per resolved pair (957). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TL;DR
I wanted a version to select focal effects - i.e. pick one row per original-replication pair in a principled way - a few times now. I would suggest we add this to the store - but @LukasRoeseler let's discuss whether we add this to the database directly, or just provide it as an extra resource. Maybe keeping it separate is better as it is not double-coded and thus not up to FReD quality standards.
What this adds
Two files under
cache/:focal_effect_flags.csv— one row per FReD effect (2164 rows, keyed tooutput/FReD.xlsxbyeffect_id), flagging whether each effect is the focal effect of its replication pair: the single effect the replication study actually targeted as its primary replication object.focal_effect_flags.md— documentation of the columns, the derivation rule, and the caveats.Why
FReD's row unit is the effect (
effect_id), but the scientific unit of a replication is the original↔replication pair (fred_id), which can carry many correlated within-study effects. Any per-pair analysis (replication-rate summaries, z-curves, one-observation-per-claim comparisons) needs to reduce each pair to the one effect the replication was actually about. This flag provides that, chosen on principle.How the focal effect was determined
Per pair, cheapest evidence first (
focal_sourcerecords which tier resolved each pair):gemini-flash-lite-latest, two-pass, spot-checked).When no single focal claim could be identified, the focal effect was **left empty ** — and the pair was routed to an explicit non-focal class.
Coverage
987 coded pairs → 957 resolved to a single focal effect. The rest are classified, not dropped:
focal_role = constituent)fred_ids; the targeted effect lives in a siblingfred_idSoto/LOOPR) — focal concept doesn't applyNo pair remains
needs_review. Effect-level coverage:is_focal = TRUEon exactly 957 rows (one per resolved pair);resolved1781 /constituent_set169 /target_absent13 /focal_in_sibling7 /not_applicable60 /uncoded134 effects.Method notes
validation == "validated - chosen"rows are authoritative.coalesce(DOI, URL)on both the original and replication sides, with preprint↔version-of-record equivalences (cache/confirmed_preprint_duplicates.csv) and RPP umbrella-vs-component DOIs, not on raw DOI alone.FReD data-quality findings surfaced by this work
fred_idfragmentation — one original↔replication pair is sometimes split across a basefred_idand_1-style siblings sharing identicaldoi_o+doi_r. Documented (focal_in_sibling); analyses must dedup ondoi_o+doi_r, notfred_id.additional_studies94claim_text mis-paste (fixed in source) — effects 323/324 carried the Study-1 manipulation-check text although their statistics are the focal reliance DV; corrected in the validation sheet on 2026-07-23 (seefocal_effect_flags.md).curatescience15depletion DV and threeresciencex_01teacher-credential effects — effects the replications targeted that FReD did not hold.Provenance / reproducibility
Derived from the "Validating FReD replication success" abstract-coding sheet and the FReD effect table; full method, per-tier counts, spot-checks, and the complete list of non-focal pairs are in the accompanying validation report (available on request).