The model inputs are organized by type and the components where they are used in the model.

Some of these files are explicitly identified by the model Scenario Manager, specifically any files that are likely to change between scenarios

• ABM contains the files that define the component structures, alternatives, and parameters (UEC). The visitor models have their own set of UEC files, and are stored in the visitor sub-folder
• GIS contains the polygon shape files for the MAZ, TAZ, and SuperDistricts; the polyline shape files for the highway networks, and the GeoDatabase containing the highway and transit networks. Note that SERPM 8 runs from the .NET and .LIN files for highway and transit inputs respectively, but these files were exported from the GeoDatabase.
• heval contains the air quality and accessibility parameter files used in the HEVAL summaries conducted at the conclusion of a model run
• Highway contains the files to support the highway network building, such as the speed/capacity factors (Parameters subfolder) as well as the seed skims and loaded network (seed_net_skm2015)
• SEData contains the land use and demographic data. This includes the synthetic population and households/population/employment by MAZ.
• SpecGenTrk contains the inputs for Special Generator (airports, cruiseports), trucks, and externals
• Transit contains the transit line and factor files.

The model programs are grouped by the program type: ABM (java), Cube scripts, and Reports (R)

• ABM includes the scripts that are called by Cube to manage the java runs and the compiled CTRAMP java file (application). The jdk is necessary to support CTRAMP operation. The config folder contains the files that specify how the different java programs communicate.
• Cube contains all of the cube scripts (*.S) and application group definitions (*.APP) as well as the helper programs (mleg.exe, mkturn.exe)
  • NOTE: the Cube scripts should be only modified through the Cube Application Manager, especially the definition of input/output files.
• Reports contains the R scripts, support files, and Excel report templates

The top level scenarios folder contains child scenarios. Within each child scenario is a local copy of the model inputs, the model outputs, log files generated during the model run, and report files from the model run.

Note that the folders associated with the parent folder scenario are prefixed with an "_". Folders that do not have an underscore (e.g. HwyOnly is a child scenario and contains a full complement of results).

• _abm contains most of the files generated by the activity-based model component. The trip rosters converted into Cube matrix format are stored in the _cube folder.
• _archive contains a copy of the generated Cube and ABM files from previous model iterations
• _cube contains files generated by Cube as part of the model run
• _inputsDoNotEdit contains the input files. These are copied over from the Inputs folder (or another scenario) dynamically at the beginning of the model run. As the name indicates, changes to the scenario inputs should be made in the Inputs folder and pointed to through the scenario manager. Files in this folder will be overwritten if the scenario is rerun.
• _logs contains files from Cube (*.PRN) and the ABM (resident and visitor). Not all Cube model programs produce a PRN and it may be necessary to examine the SERPM**.PRN file for a full picture. This file is stored in the Inputs\Programs\Cube folder.
• _reports contains Cube reports, R reports, and the runtime and feedback summaries