FRED Output Directory Structure

Below is an example FRED output directory of a run with at least one of all possible outputs represented.

Scroll right! -->

OUT ---------------------------------------------------- The output directory of the run. The name of the directory may differ depending on how FRED was run.
├── conditions.json ------------------------------------ A json file representing all of the conditions/states in the model that was run.
├── return_code.txt ------------------------------------ The return code of the FRED run.
├── logs.txt ------------------------------------------- A file containing logs from the run. Messages are prefixed with a timestamp and log level. Error messages appear here. Use the model file in the MODEL directory for referencing line numbers.
├── MODEL
│   ├── visualization.gz ------------------------------- A visualization of the model in graphviz format.
│   └── <MODEL_NAME>.fred ------------------------------ The complete model code that was run by the simulation engine. This will include internally preprocessed code and the default model if enabled.
├── USER_OUTPUT
│   ├── <USER_OUTPUT>.csv ------------------------------ CSV files that the users print using `print_csv` appear here.
│   ├── <USER_OUTPUT>.txt ------------------------------ Custom text that the users print using `print_file` appear here.
│   └── print_output.txt ------------------------------- Results of `print()` function.
├── DAILY
│   ├── <MY_CONDITION_NAME>.<MY_STATE_NAME>.txt -------- File containing lines representing `<simulation_day> <number_of_agents_currently_in_state>`
│   ├── <MY_CONDITION_NAME>.new<MY_STATE_NAME>.txt ----- File containing lines representing `<simulation_day> <number_of_agents_entering_state_this_day>`
│   ├── <MY_CONDITION_NAME>.tot<MY_STATE_NAME>.txt ----- File containing lines representing `<simulation_day> <number_of_times_an_agent_has_entered_state>`
│   ├── <MY_CONDITION_NAME>.Gt.txt --------------------- File containing generation time info for each day. Logged iff condition is transmissible.
│   ├── <MY_CONDITION_NAME>.Rt.txt --------------------- File containing effective reproductive number info for each day. Logged iff condition is transmissible.
│   ├── Date.txt --------------------------------------- File containing lines representing `<simulation_day> <date_string>`.
│   ├── EpiWeek.txt ------------------------------------ File containing lines representing `<simulation_day> <simulation_year>.<epiweek_number>`.
│   └── Popsize.txt ------------------------------------ File containing lines representing `<simulation_day> <number_of_agents_in_simulation>`
├── VARIABLES
│   ├── numeric.<MY_SHARED_NUMERIC>.csv ---------------- Generated if you have `set_output_interval(MY_SHARED_NUMERIC, <some_number>)` in your model. Lines represent `<simulation_day> <variable_value_at_end_of_day>`
│   ├── list.<MY_LIST_VAR>.csv   ----------------------- Contains contents of a list at the end of the simulation, similar to the above. Enable with `set_output_interval`.
│   ├── list_table.<MY_LIST_TABLE_VAR>-<day#>.csv ------ Contains contents of a list_table at end of day at the specified interval. Enable with `set_output_interval`.
│   └── table.<MY_TABLE_VAR>-<day#>.csv ------------------ Contains contents of a table at end of day at the specified interval. Enable with `set_output_interval`.
└── NETWORKS
    └── MY_NETWORK_NAME-<day#>.gv ---------------------- File which will be generated if you set the `output_interval` on a network to some non-zero value. Contains information about a network's edges in DOT graph description language.