Components

The full UHTIMv2 application suite consists of seven, small executable files, compiled for the Windows operating system. Each of these executable files reads input from a particular directory (and sub-directories) associated with a given model run. Outputs from each stage of a model run (i.e. outputs from individual applications) are saved into sub-directories of the main. In that way, all inputs and outputs for a given run of TIM will exist, collated in the same location.

Application files:

The individual applications and their functions are as follows:

  1. M4InitialiseProject.exe: Takes a model run name and creates the main directory, and all required sub-directories for a given run. Also copies required pollution Look-Up Tables (LUTs) from the TIM installation location, to the main directory.
  2. M4BaseTraffGen.exe: Takes a timetable of traffic events as input, and creates a ‘typical’ traffic pattern (flow only) for a week as output. The traffic patterns for an individual hour may be based on provided values (i.e. statically defined traffic on a particular road), based on traffic assignment (e.g. using ‘All-or-Nothing’, ‘Incremental Loading’ or ‘Frank-Wolfe’ cost-based assignments), or based on scaling data from another hour for which traffic has already been defined;
  3. M4RegTimeGen.exe: Takes a timetable of events throughout the region, and collates them into a series of ‘time-slices’, with associated traffic patterns, that may be applied to the network in sequence;
  4. M4FleetPollProc.exe: Calculates fleet-weighted LUTs for all used fleets (‘Baseline’ and ‘SiteActive’) using a ‘palette’ of vehicles. It is these fleet-weighted LUTs that are used in the final emissions calculations;
  5. M4RegTraffGen.exe: Takes the baseline traffic pattern from ‘M4BaseTraffGen.exe’, and loops through the time slices provided by ‘M4RegTimeGen.exe’, to create traffic patterns (flows, speeds and costs on links) for a typical week in each time slice;
  6. M4RegPollProc.exe: Uses the traffic patterns output from ‘M4RegTraffGen.exe’, combined with the fleet-weighted LUTs  output from ‘M4FleetPollProc.exe’, and the time-slice durations output from ‘M4RegTimeGen.exe’ to produce ‘Baseline’ and ‘SiteActive’ emissions for the required pollutants in the period time-slices, and hourly values if necessary;
  7. M4RegPostProc.exe: Post-processes outputs from ‘M4RegPollProc.exe’ to give inputs appropriate for the 3rd Party ADMS software.

Workflow:

The full workflow through the individual applications is described in the user manual, available from the Documentation section.

Sample datasets:

The tutorial scenario, provided with the UHTIMv2 downloads includes region, network and pad data, used previously for example wells in the published Environment International article. The emissions factors are derived from a previous version of the DEFRA Emission Factors Toolkit (v5.1.3) and have been superseded by subsequent EFT versions (currently Version 7) in the UK.