SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2005.07882 · 2020

Curating a COVID-19 data repository and forecasting county-level death counts in the United States

arXiv · PDF · Open in the Atlas

Code that ran

1 of 1 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2005.07882.json · badge: /api/ran/2005.07882.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
Yu-Group/covid19-severity-prediction canonical (classifier label)
classifier basis: classifier_2025
1 ran · 0 no recorded run
FunctionStatusWhere it lives
clean_ahrf_health Ran
ran; our contract draft was wrong, not the code
Yu-Group/covid19-severity-prediction/data/county_level/processed/ahrf_health/clean.py
code served (permissive licence) · get_code("5ca09d72e2333390")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1) and returned DataFrame. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import os
import tempfile
import pandas as pd
from os.path import join as oj

# Create a temporary directory for testing
temp_dir = tempfile.mkdtemp()
data_dir = temp_dir
out_dir = temp_dir

# Create a mock raw CSV file that load_ahrf_health would expect
raw_csv_path = oj(data_dir, 'ahrf_health.csv')

# Create sample data with all the columns that will be dropped or renamed
sample_data = {
    'Blank': [1, 2],
    'EntityofFile': ['A', 'B'],
    'SecondaryEntityOfFile': ['X', 'Y'],
    'DateofFile': ['2018-01-01', '2018-01-02'],
    'DateofCreation': ['2018-01-01', '2018-01-02'],
    'FileLength': [100, 200],
    'CountyNamew/StateAbbrev': ['County1, ST', 'County2, ST'],
    'FIPSStateCode': [1, 2],
    'FIPSCountyCode': [1, 2],
    'Header-FIPSStandCtyCode': [1, 2],
    'StateName': ['State1', 'State2'],
    'StateNameAbbreviation': ['ST1', 'ST2'],
    'CountyName': ['County1', 'County2'],
    'SomeOtherColumn': ['data1', 'data2']
}

df_sample = pd.DataFrame(sample_data)
df_sample.to_csv(raw_csv_path, index=False)

# Mock the load_ahrf_health function
def load_ahrf_health(data_dir=oj('..', '..', 'raw', 'ahrf_health')):
    """Mock function to load AHRF health data"""
    csv_path = oj(data_dir, 'ahrf_health.csv')
    return pd.read_csv(csv_path)

# Inject the mock into the module namespace
import sys
current_module = sys.modules[__name__]
current_module.load_ahrf_health = load_ahrf_health

ARGS = {
    'data_dir': data_dir,
    'out_dir': out_dir
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1
Imports
pandas — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type DataFrame — a DataFrame output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a DataFrame output the recorded ndim 2 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block

Also present in other papers' code

Of 1 samples lifted from this paper's linked repositories, 1 carry a function identity and 0 do not. Of the 1 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 1 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

As the COVID-19 outbreak evolves, accurate forecasting continues to play an extremely important role in informing policy decisions. In this paper, we present our continuous curation of a large data repository containing COVID-19 information from a range of sources. We use this data to develop predictions and corresponding prediction intervals for the short-term trajectory of COVID-19 cumulative death counts at the county-level in the United States up to two weeks ahead. Using data from January 22 to June 20, 2020, we develop and combine multiple forecasts using ensembling techniques, resulting in an ensemble we refer to as Combined Linear and Exponential Predictors (CLEP). Our individual predictors include county-specific exponential and linear predictors, a shared exponential predictor that pools data together across counties, an expanded shared exponential predictor that uses data from neighboring counties, and a demographics-based shared exponential predictor. We use prediction errors from the past five days to assess the uncertainty of our death predictions, resulting in generally-applicable prediction intervals, Maximum (absolute) Error Prediction Intervals (MEPI). MEPI achieves a coverage rate of more than 94% when averaged across counties for predicting cumulative recorded death counts two weeks in the future. Our forecasts are currently being used by the non-profit organization, Response4Life, to determine the medical supply need for individual hospitals and have directly contributed to the distribution of medical supplies across the country. We hope that our forecasts and data repository at https://covidseverity.com can help guide necessary county-specific decision-making and help counties prepare for their continued fight against COVID-19.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2005.07882")
get_code_for_paper("2005.07882")
have("2005.07882")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2005.07882.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2005.07882.svg)](https://syntology.ai/paper/2005.07882)

Connect an agent — have() is free.