Repository navigation
Fix docs the EpiModel addition left stale - #29
Merged
Merged
Conversation
- Results: EpiModel's 1,000,000-agent memory peak (1,893 MiB) belongs in the list of the largest, above EoN's. The environment bullet said every scenario ran in one recorded environment; ABM's and EpiModel's records come from later, separate runs, so every scenario report warns about mixed environments. Methods now says which run the environment table describes. - Scenario 02: EpiModel's extraction (about 45 ms) is larger than epiworldR's. It is get_transmat(), which keeps one infector per new case by grouping with dplyr and sampling, about 45 µs per transmission. - Scenario 00: ABM belongs among the uncalibrated engines, and the model-lines note now covers EpiModel's modules. - scenarios.md: the runner layout and checklist list epimodel.R, agents.jl, and run_FRED.py. Co-Authored-By: Claude Opus 5.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.
Follow-up to #28. Docs only; no runner, record, or figure changes.
The README figures. The figures on
mainalready include EpiModel:README_files/figure-commonmark/summary-time-plot-1.pngas served by raw.githubusercontent.com matches the committed blob (EpiModel is the bottom row, 7 s at 100k and 79.3 s at 1M). GitHub serves repository images withmax-age=300, so a page opened shortly after the merge can show the earlier, twelve-engine figure until a hard refresh.What this fixes
docs/results.qmddocs/methods.qmd: after the environment table, a note that the table describes the run behind every engine except ABM and EpiModel, and how those two ran.scenario_02/README.qmd: the notes said extraction is small for every engine but epiworldR and FRED. EpiModel's is about 45 ms, nearly all of itget_transmat(). That function keeps one infector per new case with a grouped dplyrsample_n(), about 45 µs per transmission. A synthetic test confirmed it is linear: 28 ms for 1,000 rows and 0.27 s for 10,000.scenario_00/README.qmdscenario.tomlalready says it needs no factor.scenarios.md: the runner layout and the checklist now listepimodel.R, plusagents.jlandrun_FRED.py, which were also missing.Reports re-rendered with
make container-report. The scenario simulation-time PNGs were left as they were: those plots use unseeded jitter, so a re-render changes their bytes but not their data.Not changed
🤖 Generated with Claude Code