SPB Git

spb/wp29_uqo

Public
5.4 KB · 68 lines markdown
1# F4-conf-01: Treatment effects and their uncertainty taken from two published results tables23## Question4The task is to copy specified point estimates, uncertainty measures and counts exactly as printed from two arXiv extracts, and to give each one a locator:5- **DCR study** (arxiv-2609.27732v1): staggered DiD on Swiss drug consumption room openings, Tables 6 and 7.6- **RESEA study** (arxiv-2606.14621v1): randomised trial in Rhode Island, Table 2.78Two quantities that the sources do not print are derived, with the convention stated:9- a 95% CI for the Table 6 5 km ATT, computed from its SE;10- an SE for the RESEA wage ATE, computed from its CI.1112The task also asks us to identify which requested quantity is not reported at all. Nothing is re-estimated.1314## Data and exclusions15We read `data/README.md` (10 lines), `arxiv-2609.27732v1.txt` (134 lines) and `arxiv-2606.14621v1.txt` (58 lines). Only these extracts were used. Table A19 (DCR) and Table 3 (RESEA) were read for consistency checks only, because every key names Table 6, 7 or 2.1617## Method18`out/analysis.py` finds the table rows by their labels and the columns by their headers, then parses the printed numbers and prints each line it matched.19- **Stars** are stripped from estimates and recorded separately.20- **DCR standard errors** come from the parenthesised line under each coefficient row.21- **RESEA ATE cells** are split into the estimate, the p-value and the CI bounds.22- **Formatting of printed numbers.** Thousands separators are dropped (17,250 → 17250; $2,141 → 2141). JSON cannot store trailing zeros, so printed `0.210` appears as `0.21` and `-0.340` as `-0.34`. The numeric values are identical to the printed ones.2324## Results25| key | value | source |26|---|---|---|27| dcr_att_5km / se | -0.431** / (0.210) | Table 6, ATT, 5 km |28| dcr_att_3km / se | -0.283 / (0.279) | Table 6, ATT, 3 km |29| dcr_obs_5km | 17,250 | Table 6, Observations, 5 km |30| dcr_narcotics_att_3km / se | 0.549*** / (0.187) | Table 7, Narcotics, 3 km |31| dcr_fatal_att_1km / se | -1.207*** / (0.137) | Table 7, Drug-related (fatal), 1 km |32| dcr_hiv_att_5km / se | -0.340 / (0.294) | Table 7, HIV, 5 km |33| dcr_hiv_att_5km_p_value | **null**: not reported (stars only) | Table 7 |34| dcr_hiv_att_5km_significant_10pct | false (no star) | Table 7 |35| dcr_att_5km CI (derived) | [-0.8426, -0.0194] | from Table 6 |36| ri_wage_ate | $1,153; 95% CI [166, 2,141] | Table 2, Wage, ATE |37| ri_wage_ate_se_reported | false | Table 2 |38| ri_wage_ate_se_derived | 503.83 | from Table 2 CI |39| ri_control_mean_wage | $33,043 | Table 2, Wage, Control |40| ri_reemployment_ate_pp | 1.47 pp | Table 2, Reemployment, ATE |41| ri_weeks_ui_ate | -1.99 weeks; 95% CI [-2.24, -1.75] | Table 2, Weeks on UI, ATE |4243The full locator strings are in `results.json` under `locators`.4445## Uncertainty46- **DCR study (Tables 6 and 7).** The uncertainty is printed as **standard errors** (clustered at the MedStat region level, in parentheses) plus significance stars. No exact p-values or CIs are printed.47- **RESEA study (Table 2).** The uncertainty is printed as **95% confidence intervals** and two-sided p-values. No standard errors are printed.4849How the derived quantities were computed:50- **DCR 95% CI.** -0.431 ± 1.96 × 0.210 = [-0.8426, -0.0194].51  - This uses a normal approximation with critical value 1.96.52  - The extract does not say which critical value the paper uses (it could be a bootstrap or t critical value). Using 2.0 instead would give [-0.851, -0.011].53  - The interval excludes zero, which matches the ** (p<0.05) star.54- **RESEA wage SE.** (2141 − 166) / (2 × 1.96) = 503.83.55  - This assumes the printed interval is a symmetric Wald interval with a normal critical value of 1.96.56  - The assumption is supported in two ways. The half-widths are 987 and 988. The implied z of 2.288 gives a normal two-sided p of 0.0221, against a printed p of 0.022.57  - Using 2.0 instead would give an SE of about 493.75.5859## Limitations and open issues60- **Two conflicting SEs for the 5 km ATT.** Table A19 prints an SE of (0.218) for the same CS-DR 5 km ATT of -0.431, whereas Table 6 prints (0.210). We used Table 6, as the key names it.61- **Control-region count does not match the observation count.** Tables 6 and 7 say there are 608 never-treated control regions; the A19 note says 640. The printed Observations (16,175 / 16,875 / 17,250) equal (treated + 640) × 25 exactly. With 608 controls the counts would be 15,375 / 16,075 / 16,450. The observation counts are reported as printed.62- **Narrative text does not match the tables in places:**63  - The abstract says fatal hospitalisations fall by 35%. Table 7's -0.354 at 5 km implies a fall of 29.8%, and Section 6.1 says about 30%.64  - The text calls the HIV estimates "close to zero", but the 5 km point estimate is -0.340. It is insignificant, not near zero.65- **Weeks-on-UI CI sign.** The RESEA prose gives this CI as magnitudes ([1.75, 2.24] weeks). We used the signed Table 2 bounds [-2.24, -1.75].66- **Rendering and layout.** The RESEA extract has a rendering defect ("p ¡ 0.001"). Its Tables 2 and 3 were re-set by the extract editor, so we rely on the editor's statement that the values are verbatim. We could not check them against the original PDF.67- **Missing p-value.** The exact p-value for the HIV 5 km ATT is not printed, so it is reported as null. A normal-approximation p could be computed from the estimate and SE, but that would be a derived value, not a printed one.68
Files · 6df43c338e49477c769c36e7f7d249af2563db7f
Menu

Theme