Reports and other output
After the simulation finishes, a reporter extracts simulation data, aggregates it, and
outputs it to a file (known as an output report). You can use any of the reporters below
to get different information about your simulation, from memory usage to relationship pairing
to ART usage.
General reports
| Report |
Description |
| BinnedReport |
Channel data stratified by age, gender, or other properties; enabled together with DemographicsSummary. |
| DemographicsSummary |
Demographic channel data aggregated across the simulation; enabled together with BinnedReport. |
| InsetChart |
Automatically generated; simulation-wide averages of key channels at each time step. |
| PropertyReport |
Channel data broken down by individual property values. |
| ReportEventCounter |
Counts how many times each event occurs per time step. |
| ReportEventRecorder |
Records health events and interventions for each individual. |
| ReportHumanMigrationTracking |
Tracks individual migration events across nodes. |
| ReportInfectionDuration |
Records the duration of each infection at the time it clears. |
| ReportNodeDemographics |
Node-level demographic snapshot at each time step. |
| ReportSimulationStats |
Tracks performance, memory usage, and simulation object counts at each time step. |
| SpatialReport |
Channel data broken down per geographic node. |
| SqlReport |
Outputs individual-level epidemiological data to a SQLite relational database. |
HIV reports
Relationship reports
Other
| File |
Description |
| Error and logging files |
Error output and logging information generated during a simulation run. |
| stdout.txt |
Contains the logging output written by EMOD to standard output during a simulation run. |
| stderr.txt |
Contains error messages written by EMOD or Python to standard error during a simulation run. |
| Troubleshooting |
Help resolving common simulation errors. |