visummodelwiki - New pages [en]

7.4 Version NERPMAB2.2

2023-03-13T07:45:57Z

Bpaul:

This version was developed using PTV Visum modeling software and includes the following updates:

* Highway and transit networks for 2015 and 2045were imported into Visum from the previous model

* The version files contains all network inputs and settings for running the model

* AN integrated system was developed using Visum's Python API to interface PopulationSim, DaySim Data Tools, and DaySim with Visum. This resulted in streamlining of workflow for various modeling tasks for the agency staff

* All procedures from the previous model were implemented using built-in procedures in Visum or in Python using Visum's Python API

* A major skim replacement bug was fixed which resulted in premature convergence in the previous model. VISUM Model corrects the replacement and averaging of skims which results in more iterations for convergence

* A highway validation dashboard was developed for easier viewing of calibration and validation summaries

* The updated model has faster run times

* Visum's latest features for ABMs can be used to visualize ABM data. Please note that this requires the ABM AddIn which is not required for running the model.

* Perform on-the-fly select link, zone, or transit stop analysis using Visum Flow Bundle tool

5.3 Running the Model

2023-03-13T06:05:44Z

Bpaul:

To get started with NERPM-AB v2.2, download the model package and unzip the contents into a directory with read/write access. Ensure that the directory has at least 28 GB of free disk space for a scenario run. If not already installed, install the latest version of the '''PTV Visum software (2023 [SP 1-3] or above)'''. Now, follow these steps to start a base or future-year model run:

*Open the appropriate version file from the root directory by double-clicking the file. Open the '''NERPM_D2_2015_MAZ.ver''' file for the base year run and '''NERPM_D2_2045_MAZ.ver''' for the CF2045 run.

*Before starting a model run, the project directories must be set to the root directory of the model setup. This ensures that all relative paths in the model scripts are valid. Set the project directories by selecting the ‘Edit project directories’ option from the main menu bar:

[[File:set_project_directory.png]]

In the ‘Edit project directories’ window, left-click the ‘Set path for all types’ button at the bottom of the window:

[[File:edit_project_directory.png]]

Choose the root directory of the model setup from the ‘select project directory’ dialog box and click OK to exit the dialog boxes:

[[File:Select project directory.png]]

*Next, open the procedure sequence window by clicking the ‘procedure sequence’ icon on the windows toolbar as circled in red below:

[[File:procedure_seq_menu.png]]

The following window will open with a preloaded procedure sequence with all procedures activated:

[[File:Grouped_procedure_sequence.png]]

*When running the model for the first time, simply start the model by left-clicking the ‘Start procedure sequence' button on the menu bar of the procedure sequence window:

[[File:Run_procedure_sequence.png]]

This will run all the procedures in sequence starting with PopulationSim and DaySim data tools. These tools need to be run only when running the scenario for the first time unless there is a change in the inputs. Running these again will not result in an error but is redundant and will increase the runtime significantly. For subsequent runs, load the ‘Model_only_no_tools.xml’ procedure parameter file which has the ‘Synthetic Population/DaySim Tools’ group deactivated.

*Refer [[3.8 Configuration]] section for instructions on setting the number of processors for DaySim, and update as needed.

*Save the version file after the model run completes to store the results for future reference. To save the version file click the save icon on the menu bar and choose to replace the version file:

[[File:Save_version.png]]

*Follow the same steps on the '''NERPM_D2_2045_MAZ.ver''' version file to start a 2045 run.

5.2 Running PopulationSim

2023-03-13T06:00:01Z

Bpaul:

[[Category:5.0 User Interface & Running the Model]]

<p class="BodyParagraph">PopulationSim should be run when there are changes in the population in the regions' MAZs and TAZs. For example, if additional households are added to an MAZ, the user should run PopulationSim again to account for that change. The following steps illustrates how to run PopulationSim manually. Please note that PopulationSim has been fully integrated with the Visum version file to automatically run all these steps for the use cases described above. </p>

<h3> Update the Controls</h3>

The user should update the control files according to the changes in the population. For example, if there are 100 additional households in MAZ 1215, then the user should open the ''nftpo_microzones_2015.csv'' file and add 100 additional households to MAZ 1215. The user should then edit ''update_controls.S'' script to point to correct directories and files to update. The user then should run ''update_controls.bat'' file by double-clicking. The control files should now be updated.

[[File:Step1popsim.JPG]]
[[File:Step11popsim.JPG]]

<h3> Run PopulationSim </h3>

PopulationSim is run from a batch file named ''RunPopulationSim.bat''. Once the user has updated the control files, the user should open a command window in the ''Population_Synthesis'' directory and run the batch file as shown in the figure below.

[[File:Step2popsim.JPG]]

<h3> Convert PopulationSim Outputs to DaySim Inputs </h3>

The primary outputs of PopulationSim are the synthetic_households.csv and the synthetic_persons.csv files. These files need to be reformatted before they can be used by DaySim. There is an python script that performs this conversion. This python script is called within a batch script. The user needs to run this batch script to perform the conversion. The training document demonstrates how to run this script.

[[File:Step3popsim.JPG]]

5.1 Running DaySim Data Tools

2023-03-13T05:55:38Z

Bpaul:

[[Category:5.0 User Interface & Running the Model]]

<p class="BodyParagraph">DaySim Data Tools are a set of three tools that are run sequentially to prepare input data for DaySim. [[3.4 Land Use Data Prep]] shows the inputs and outputs required for these tools. The video tutorial shows how to run the tools. </p>

<h3> DaySim Data Tools executables </h3>

The following image shows the 3 executable files for the 3 tools. There are settings files associated with each of these tools. In most cases, the user does not need to change the settings files for the NetPrep and DTALite tool. However, the user should update the settings for DaySim Buffer Tool before running it. The buffer tools user interface is show in the next image.

[[File:DaySim_data_tools.png]]

<h3> Run DaySim Buffer Tools </h3>

The important fields to notice in the interface are the input and output file fields. These file names should be updated accordingly when preparing inputs for a particular scenario. For example, if the user were to prepare inputs for CF2045 scenario, then the input and output file names be changed to 2045 instead of 2015. Please note that when running these tools from Visum, pre-configured properties are selected. These properties generally are not changed.

[[File:Buffertool.png]]

4.4 DaySim-Visum Linkage

2023-03-13T05:19:09Z

Bpaul:

[[Category:4.0 Directory & Data Structures]]

PTV Visum procedures generate highway and transit skims that are stored in the model version (.ver) file. The skims are converted to ASCII text files using Visum's Python API and are input to DaySim, which simulates person trips and outputs them into .tsv list format (_tour.tsv, _trip.tsv etc.). In addition, DaySim also writes out a simple trip list “Tdm_trip_list.csv” in \Scenarios\{SCENARIO_NAME}\Output\DaySim directory. This file just has origin TAZ, destination TAZ, mode, departure time, arrival time, trip duration, purpose, and VOT category. This trip list is transformed into time-of-day, mode, and purpose specific highway and transit matrices for assignment using Visum's Python API, which imports final trip tables into Visum for assignment.

3.15 Reporting

2023-03-11T01:12:27Z

Bpaul:

[[Category:3.0 Model Design]]

This section describes the various reports generated by the model run. These reports can be used to assess model performance and can inform model calibration and validation, as well as other analyses. All these reports are generated by the procedures in the '''Reports and Summaries''' group of the full model procedure sequence. The log file from the full model run is also copied to the output folder for future reference. The log file contains important information such as auxiliary model summaries, convergence statistics, and Visum-generated messages and warnings.

<h2>DaySim</h2>

The DaySim run produces multiple outputs in “DaySim” within the scenario output directory (\Output\DaySim). The primary outputs are

*_household.tsv
*_household_day.tsv
*_person.tsv
*_person_day.tsv
*_tour.tsv
*_trip.tsv

These files contain information about the various activities, tours, and trips generated by the Daysim activity-based model components. To make the information more interpretable by the user and also to help in the validation of the activity-based model, these outputs are summarized in a set of Excel spreadsheets. R scripts are available that run the summary as a post-process each time the model is run and update the excel spreadsheets. The '''''generate_daysim_report.py''''' Python script generates these Excel spreadsheets in the Output\DaySim\Reporting sub-directory of the scenarios folder.

The process consists of just two steps. The first creates an R script that sets the paths of various inputs required. In the second step, R is called in the batch mode to run the summary script created in the first step. The output files are a set of Excel spreadsheets that have tables and charts summarizing various model simulation results. This process is described in further detail in Section 4.7 |.

<h2>Highway Assignment</h2>

Highway evaluation and analysis conducted by post-processing the loaded assignment networks is a valuable tool for modelers. Traditionally in Florida, this type of analysis has been conducted with the use of the FSUTMS HEVAL and RMSE programs. Vehicle-miles-traveled (VMT), vehicle-hours-traveled (VHT), and vehicle-hours of delay are some of the most common measures.

A highway validation report is generated in HTML format. Highway validation statistics in HTML format are particularly easy to look at. Statistics include overall measures such as V\C ratios, VMTs and VHTs by facility types, etc. In addition, validation statistics are output at the screenline level.

<h2>Transit Assignment</h2>

Boardings and alightings by route as well as station-level summaries are stored in their respective databases. The user can simply load the ''List layout files (.llax)'' in the '''/listings''' sub-directory to generate boarding summaries.

3.14 Feedback

2023-03-11T01:11:47Z

Bpaul:

[[Category:3.0 Model Design]]

Feedback is used in two primary ways in the NERPM activity-based model system: between iterations within the highway assignment process, and between “system” iterations of the model system in which both the Daysim activity-based demand components and the Visum-based network supply components are executed.

The Method of Successive Averages (MSA) method is a common means of achieving overall stable model system results. The basic idea of the MSA method is to combine the link flows from the current system iteration with the best estimate of link flows from prior system iterations to produce the current best estimate of link flows. This is then used to compute congested link travel times using the volume delay function and these congested times are input to the skimming procedure.

Feedback during “system” iterations in the model is achieved using network skims. The skims generated from the MSA averaged link flows and resulting congested times are used for the auxiliary models and DaySim in the next iteration. Transit skims are updated based on congested link time for the next iteration. Currently, the model is set up to run up to 7 such iterations. At the end of each iteration, the overall model convergence is checked. The model run is terminated if convergence is achieved before 7 iterations. The convergence is achieved when all of the following conditions are satisfied between the current and previous iteration outputs:

* The % change in Vehicle Miles Travelled (VMT) is less than 5% for both AM and PM periods
* The % of links with under 5% change in link volumes is less than 5% for both AM and PM periods

3.13 Assignment

2023-03-11T01:11:12Z

Bpaul:

[[Category:3.0 Model Design]]

<h2>Highway</h2>

The ''PrT Assignment'' procedure step performs the final vehicle assignment by time period step. The ''PrT Assignment'' step is called in the '''''Assignment and Skim Update''''' group for each period in the full model procedure sequence.

Procedure Name = PrT Assignment

Procedure Purpose = Assigns vehicle demand onto the regional planning network

Primary Input = Vehicle trip tables and settings

Primary Output = Congested link volumes and congested link travel times (speeds)

The purpose of the trip assignment model is to load vehicle trips onto the representation of the transportation highway network. This process results in traffic estimates on individual links in the network that ultimately attempt to simulate general vehicular travel throughout the planning region.

The highway vehicle trips are loaded separately by occupancy class. The assignment classes are required in order to prohibit single-occupancy vehicles and truck from utilizing the high-occupancy vehicle only lanes on the highways and interstates. The external-external demand is also defined as a separate class as some links prohibits external-external demand. The assignment employs a user equilibrium method that is an iterative process to achieve a convergent solution where no travelers on the roadway network can improve travel-times by shifting routes. Throughout each of these iterations, Visum computes network-link flows, which incorporate link-capacity restraint effects and flow-dependent travel-times. At the end of assignment for each period, the congested link volumes are stored in user-defined fields for post-processing and analysis. Next, the loaded networks are skimmed to produce skim LOS variables to be used in the next global iteration of the model. At the end of the model run, validation reports are generated by comparing the modeled volumes to the observed traffic counts on network links.

<h2>Transit</h2>

Transit assignment is the process of loading the transit trips onto the transit paths. There are only two time periods (Peak and Off-peak) for transit assignment as opposed to four in highway assignment. Peak (PK) represents the combination of the AM peak and PM peak transit trips produced by Daysim, while Off-peak (OP) represents the combination of the midday and evening transit trips. All the transit trips that are assigned are generated from DaySim output. Only the transit portion of the transit trips are used to generate trip table for transit assignment. Transit assignment is performed at the end of the final feedback loop using the ''PuT Assignment'' procedure step. The ''PuT Assignment'' step is called in the '''''Network Assignment: Transit PK and OP''''' group.

Procedure Name = PuT Assignment
Procedure Purpose = Assigns transit vehicle trip matrices onto the regional transit network; Assigns two (2) periods of transit demand onto the regional planning transit network, peak (PK) and off-peak (OP) which summed together represent the daily transit assignment results.
Primary Input = Regional planning transit network and transit trip tables estimated from the DaySim activity-based model
Primary Output = Daily (peak + off-peak) transit route-level ridership and boardings/alightings by stop and station

Boardings and alightings by route as well as station-level summaries are stored in their respective databases. The user can simply load the ''List layout files (.llax)'' in the '''/listings''' sub-directory to generate boarding summaries.

3.12 Assignment Preparation

2023-03-11T01:10:37Z

Bpaul:

[[Category:3.0 Model Design]]

It should be noted here that the part of the trip-based model that generates passenger demand has been replaced by DaySim activity-based model. DaySim produces detailed outputs that include information on activities and tours simulated for the synthetic population. In addition, it also produces a simple trip list that has origin, destination, purpose, mode, value of time, and time of day information. This trip list is converted to vehicle trip matrices by a Python script using vehicle occupancy rates and are segmented by mode, value of time, and time period. Transit trips by peak and off-peak periods are also included in preparation for transit assignment.

The '''''generate_daysim_tt.py''''' Python script is run after ‘DaySim’ application and this does precisely as the name suggests, it prepares the vehicle trip tables that will be used in the final vehicle assignment step. This is a new application specifically built and configured for the NERPM-AB model system.

*'''Python Script Name''' = generate_daysim_tt.py
*'''Purpose''' = Generates daySim trip tables from DaySim outputs
*'''Primary Input''' = DaySim outputs
*'''Primary Output''' = Final Daily, AM, MD, PM and NT period vehicle trip tables for each model period. The matrices are stored in the Visum version file.

The '''Combination of matrices and vectors''' procedure is used for combining the trip tables.
The application combines the light truck, medium truck, heavy truck, the IE and EI vehicle trip matrices, the EE vehicle trip matrices, the JAXPORT freight truck trips and the internal passenger demand matrices from DaySim to produce four (4) individual vehicle trip matrices for the AM, MD, PM, and NT model periods representing the entire 24-hour day.

3.11 DaySim

2023-03-11T01:09:59Z

Bpaul: Created page with "Category:3.0 Model Design DaySim simulates 24-hour itineraries for regional residents including but not limited to choices of activity participation, destination, mode, a..."

[[Category:3.0 Model Design]]

DaySim simulates 24-hour itineraries for regional residents including but not limited to choices of activity participation, destination, mode, and time-of-day, with spatial resolution as fine as individual microzones and temporal resolution as fine as single minutes. DaySim’s predictions in all dimensions (activity and travel generation, tours and trip-chaining, destinations, modes, and timing) are sensitive to travel times and costs that vary by mode, origin–destination (OD) path, and time-of-day, so it can, in turn, effectively use as input to network supply models. DaySim captures the effects of travel time and cost upon activity and travel choices in a way that is balanced across modes and times of day and consistent with the econometric theory of nested choice models. DaySim can be used in a distributed manner by running separate instances on different processors on different partitions of the study area population, and then merging the results.

DaySim is comprised of a number of subcomponents and structured as a series of hierarchical or nested choice models. The general hierarchy places the long term models at the top of the choice hierarchy, and the short term models at successively lower levels in the hierarchy. The detailed hierarchy and flow through the model is illustrated in Figure 3‑4. Note that the general flow is down from the long term models to the short term models. Moving down from top to bottom, the choices from the long term models influence or constrain choices in lower level models. For example, household auto ownership affects both day pattern and tour (and trip) mode choice, by including auto ownership variables in those component models. In addition to these direct influences, utilities from lower level models flow upward to higher level models. “Logsums” (expected utilities) from tour destination and tour mode choice models affect other short term models, as well as the upper level, longer term models. Some of the logsums from lower level models are aggregated for use in the long term models, in order to reduce the computational load of using fully detailed disaggregate logsums in such a complex nesting structure.

'''FIGURE 3-4 DAYSIM MODELING COMPONENTS AND LINKAGES'''

[[File:Figure 3-4.png]]

3.10 Auxiliary Demand

2023-03-11T01:09:19Z

Bpaul:

[[Category:3.0 Model Design]]

<p class="BodyParagraph">DaySim provides detailed predictions of the long-term and short-term travel choices of regional residents, but this travel demand does not fully represent all trips that use the regional transportation networks. DaySim only represents the internal passenger travel demand made by residents of the region which accounts for about 80-85% of the total regional demand (<em>in the base year</em>). There is other auxiliary demand which must be accounted for that is contributed by trucks and commercial vehicles, truck freight to/from the Port of Jacksonville and most importantly three (3) different flavors of external travel made by both residents of the planning area as well as non-residents. The three (3) different flavors of external travel are internal-to-external, external-to-internal and external-to-external (<em>thru</em><em>trips</em>). Commercial and truck traffic typically comprise a significant shore of all roadway volumes. In addition, non-residents enter the region through key external gateways to access jobs, shopping or other opportunities, and similarly, the residents may leave the region to satisfy other needs. This “auxiliary demand” is derived from the existing four-step model system.

</p><h3 id="id-3.9AUXILIARYDEMAND-PortFreight"><span style="color: rgb(255,102,0);">Port Freight</span></h3><p class="BodyParagraph">The '''''interpolate_port_truck_tt.py''''' Python script prepares an origin-destination freight truck trip table representing the freight demand produced by and attracted to the Port of Jacksonville, Florida (JAXPORT). The script takes JAXPORT demand for 2010 and 2040 as inputs and interpolates the freight truck trip tables for analysis years between 2010 and 2040 (or beyond) based on the implied growth.

</p><h3 id="id-3.9AUXILIARYDEMAND-Non-HH"><span style="color: rgb(255,102,0);">Non-HH</span></h3><p class="BodyParagraph">Non household (non-hh) trips are generated and distributed separately. The '''''tgen_main.py''''' Python script in the '''Auxiliary Demand Generation''' group of the procedure sequence generates the zonal productions and attractions. The procedure steps in the '''Trip Distribution - Auxiliary Models''' group run trip distributions and create II truck, IE and EE truck, and IE and EE vehicle trip tables. This demand is added to the II vehicle demand created by DaySim before assignment. The table below illustrates the demand from the trip generation model which is retained in the NERPM-AB model system and which is replaced and overwritten by the DaySim activity-based demand model.</p><h4 class="BodyParagraph" id="id-3.9AUXILIARYDEMAND-TABLE3-10NERPM-ABMODELDEMANDESTIMATEDBYTRIPGENERATIONMODEL">TABLE 3-10 NERPM-AB MODEL DEMAND ESTIMATED BY TRIP GENERATION MODEL</h4><div class="table-wrap">
{| class="wikitable"
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Description</strong></p>
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>Acronym</strong></p>
| class="highlight-red confluenceTd" data-highlight-colour="red" | <p class="TableHeadingGray"><strong>NERPM-AB</strong></p>
|-
| class="confluenceTd" | <p align="center" class="BodyParagraph" style="text-align: left;">Home-based work</p>
| class="confluenceTd" | <p class="BodyParagraph">HBW</p>
| class="confluenceTd" | <p class="BodyParagraph"><em>Replaced by DaySim</em></p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Home-based shop</p>
| class="confluenceTd" | <p class="BodyParagraph">HBSH</p>
| class="confluenceTd" | <p class="BodyParagraph"><em>Replaced by DaySim</em></p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Home-based social and recreational</p>
| class="confluenceTd" | <p class="BodyParagraph">HBSR</p>
| class="confluenceTd" | <p class="BodyParagraph"><em>Replaced by DaySim</em></p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Home-based other</p>
| class="confluenceTd" | <p class="BodyParagraph">HBO</p>
| class="confluenceTd" | <p class="BodyParagraph"><em>Replaced by DaySim</em></p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Nonhome-based</p>
| class="confluenceTd" | <p class="BodyParagraph">NHB</p>
| class="confluenceTd" | <p class="BodyParagraph"><em>Replaced by DaySim</em></p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Four-wheeled truck</p>
| class="confluenceTd" | <p class="BodyParagraph">LT</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Single-unit truck</p>
| class="confluenceTd" | <p class="BodyParagraph">MT</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Combination truck-trailer</p>
| class="confluenceTd" | <p class="BodyParagraph">HT</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Single-occupancy vehicle internal-external</p>
| class="confluenceTd" | <p class="BodyParagraph">SOVIE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">High-occupancy vehicle internal-external</p>
| class="confluenceTd" | <p class="BodyParagraph">HOVIE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Light-duty truck internal-external</p>
| class="confluenceTd" | <p class="BodyParagraph">LDIE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Heavy-duty truck internal-external</p>
| class="confluenceTd" | <p class="BodyParagraph">HDIE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Single-occupancy vehicle external-external</p>
| class="confluenceTd" | <p class="BodyParagraph">SOVEE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">High-occupancy vehicle external-external</p>
| class="confluenceTd" | <p class="BodyParagraph">HOVEE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Light-duty truck external-external</p>
| class="confluenceTd" | <p class="BodyParagraph">LDEE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|-
| class="confluenceTd" | <p class="BodyParagraph">Heavy-duty truck external-external</p>
| class="confluenceTd" | <p class="BodyParagraph">HDEE</p>
| class="confluenceTd" | <p class="BodyParagraph">Retained from NERPM42</p>
|}</div>

3.9 Network Preparation & Skimming

2023-03-11T01:08:25Z

Bpaul:

[[Category:3.0 Model Design]]

For short distance trips, DaySim uses distance skims obtained from an all streets network. For all other trips, DaySim requires highway and transit skims obtained from the model highway and transit networks respectively. These skims are also needed for network assignment purpose. Initially, free flow highway skims are created and used. In subsequent iterations of the model, loaded/congested skims from the previous iteration are used.

<h2>Highway</h2>

The highway network in NERPM-AB v2.2 is maintained within the Visum version (.ver) file using the links and nodes network objects. The highway network was imported from the previous version of NERPM-AB. The highway network is processed for skimming using the built-in procedures in Visum (see '''''Network Prep''''' group in the full model procedure sequence). The initial freeflow highway skims are generated by the Calculate PrT Skim Matrix procedure step for each mode (see '''''Network Skimming PrT''''' group in the full model procedure sequence). The highway skim matrices are stored in the version file and exported in the required format for DaySim.

Highway networks represent the highway transportation system in the planning area represented by the regional travel model. A highway network includes a series of interconnected “links” connected to one another at “nodes” with each link and node containing a set of attributes relevant to simulating highway conditions. The links represent roadway segments and the nodes in most cases represent intersections (though not always). The most critical of these attributes in FSUTMS models are those pertaining to area type (AT), facility type (FT), and the number of lanes (NL). With these three user-specified link attributes, the network processing steps of the model include a calculation of speeds and capacities via lookup tables. The lookup table for speed and capacities is stored as a user-defined table ('''SPDCAP''') in the Visum version file.

In the first pass of the model, after assignment, the loaded networks are skimmed for creating congested skim inputs for the next iteration. This results in the use of more realistic and consistent skims as the model run progresses.

Highway skims are generated for four time periods (AM, MD, PM, and NT). The skims are also created separately for drive alone (D1), shared ride 2-persons (S2), and shared ride 3+ persons (S3) modes. The skims values derived for these are time, cost (tolls), distance, and generalized cost (expressed in minutes and includes tolls).

Generalized Cost (in minutes) = Time + Toll/(Value of Time)/Occupancy + Toll service time

Non-motorized skims (time and distance) are also created for walk and bike modes.

<h2>Transit</h2>

Like highway network, the transit network is also maintained within the Visum version file using the Stops, Line, and Time Profile network objects. The transit model process in NERPM42 was originally developed from the 2005 Jacksonville Transportation Authority (JTA) regional travel model. The micro-coded network was carefully developed from the JTA model’s master network file. This network included micro-coded transit station information as well as all fixed guideway facilities and optional transit links. Although a single master network was implemented initially, it was later desired by the long-range plan update contributors to make the network scenario specific. The transit network from the previous version of NERPM-AB was imported in the PTV Visum version file for NERPM-AB v2.2.

Transit network modeling is an integral component of the NERPM-AB model system. The transit model in NERPM-AB has been established to accommodate walk and auto access modes for local bus, express bus, and rail transit service. Transit skims are generated by the ''Calculate PuT Skim Matrix'' procedure step (see '''''Network Skimming PuT''''' group in the full model procedure sequence). Like other FSUTMS models, NERPM-AB uses the AM designation for “peak” transit trips and MD (midday) for “off-peak” transit trips.

Transit paths are built from the transit network by calculating the generalized-cost impedance along every path between pairs of traffic analysis zones in order to identify the shortest path between all zones in terms of a composite distance, travel time, and cost measure.

DaySim only needs the following skims for peak and off-peak periods:

*Walk bus

This is because DaySim automatically chooses the PNR or KNR station for a drive transit trip and it gets the skims for the drive portion from highway skims files.

3.8 Configuration

2023-03-11T01:06:17Z

Bpaul:

[[Category:3.0 Model Design]]

Configuring NERPM-AB involves setting the procedure sequence properties, the general model settings, and DaySim properties. The following sections provide details on these. The settings specific to all tools are specified in each tool’s configuration/settings files. Please refer to the previous sections in this chapter to learn more about various tools used in NERPM-AB.

<h2>Procedure Sequence Properties</h2>
Visum-based models are run via procedure sequence which makes it possible to run multiple model steps successively. A procedure sequence includes several pre-defined procedures with specific user-defined procedures. A procedure sequence is generally organized by grouping similar procedures. A grouped procedure sequence looks as follows:

[[File:Grouped_procedure_sequence.png]]

Double-click the procedure group to expand it to view individual procedures inside a procedure group. To expand all groups, click the ‘Expand all groups’ button on the side bar as shown below:

[[File:Expand_all_groups.png]]

Activate/deactivate the procedures to be run by checking/unchecking the ‘Active’ check box next to each procedure group. To activate all procedures, click the ‘Set all active’ button in the ‘Operations’ sidebar as shown below:

[[File:Check_all_procedures.png]]

Individual procedures within a group can be set as active/inactive by checking/unchecking the ‘Active’ check box next to the procedure. For example, the initialization of assignment results can be skipped as follows:

[[File:Uncheck_procedures.png]]

The settings specific to assignment and skimming are set in the procedure sequence settings. To view these settings, open the procedure sequence settings by clicking the ‘general procedure settings’ icon in the procedure sequence window:

[[File:General_procedure_settings.png]]

The general procedure settings window allows the configuration of link and node impedances, highway (PrT) and transit (PuT) assignment, and skimming settings.

[[File:Configure_general_procedure_settings.png]]

To start the procedure sequence, left click the ‘Start procedure sequence' button on the menu bar of the procedure sequence window. This will run all active procedures in sequence.

[[File:Run_procedure_sequence.png]]

To run the procedures step by step, left-click the ‘Single-step’ button to step through the procedure sequence one step at a time.

[[File:Step_procedure_sequence.png]]

Once the procedure sequence has been configured for a specific modeling task, it can be exported as procedure parameter files (XML format) for reuse later. To export a procedure sequence, left-click the ‘save’ icon on the menu bar of the procedure sequence window and follow the prompts.

[[File:Save_procedure_sequence.png]]

To load a pre-saved procedure parameters file, left-click the ‘open file’ icon on the procedure sequence menu bar:

[[File:Load_Procedure_Seq.png]]

Next, select the appropriate procedure parameters file from the select file window and follow the prompts.

[[File:Select_procedure_sequence_file.png]]

<h2>General NERPM-AB Settings</h2>

The general NERPM-AB settings, parameters, and auxiliary model data are specified in the version file as user-defined tables. A full list of user-defined tables is shown below:

[[File:Table_definitions.png]]

To open user-defined tables select the ‘Table entries’ option as shown below:

[[File:Table_entries.png]]

The tables can be selected by clicking the table name button as shown below. It opens the ‘Find Table Definitions’ box. Select the appropriate table and click the ‘Confirm selection’ button.

[[File:Select_table.png]]

The NERPM-AB settings are exposed to users via the '''''SETTINGS''''' and '''''DAYSIM_CONFIG''''' user-defined tables. The '''''SETTINGS''''' table contains more general model properties such as scenario directory name and model year. A complete list of settings in the '''''SETTINGS''''' table is presented in the table below.

[[File:settings_table.png]]

<h2>DaySim Settings</h2>

The configuration file is the main control file for DaySim. The configuration file informs DaySim about inputs/outputs and various model settings. These settings include input/output file names, types and locations, sample rates, DaySim pathbuilding weights, and also allow users to specify which DaySim model components should be executed. A detailed description of the setting used in the NERPM-AB model is provided in section 4.3.

The DaySim configuration settings are exposed to the user via the '''''DAYSIM_CONFIG''''' user-defined table. During the model run, this table is written out as the DaySim configuration file in the appropriate DaySim inputs folder. A snapshot of this table is shown below:

[[File:Daysim_config.png]]

This table uses two keywords – '''''SCENARIO_DIR''''' and '''''TOOLS_DIR'''''. These point to the scenario directory path and other ABM tools directory path. These are generated on the fly based on the Project Directory settings for Visum. The relative directory paths in this table should not be changed.

<h3>N Processors</h3>

Typically, users would need to set the '''NProcessors''' property. This property specifies the number of processing cores to be used for running DaySim. By default, the number of cores for DaySim is set at 12. The number of cores should be updated based on available logical cores on the machine. More cores can be used to achieve faster DaySim run times. To set the number of processors, search the '''NProcessors''' token in the '''''DAYSIM_CONFIG''''' table and set the value to the desired number of cores as shown below:

[[File:Nprocessor_settings.png]]

<h3>Shadow Pricing</h3>

Shadow prices are constants that are added to individual microzones during the simulation of work and school location choice models. This is done to result in a good match between the following:

*Work locations of workers and employment
*School locations of students and enrollment

DaySim can be run in two modes – '''regular''' or '''shadowprice'''. When run in '''shadowprice''' mode, DaySim runs the long-term models (work and school location choice) ten times while continuously updating the shadow prices in each iteration. The intent is to make sure that there is a good match between the number of job available in a microzones and the number of workers choosing the microzones as their usual work location. The same applies for students and school locations.

DaySim should be run in '''shadowprice''' mode once per scenario or when the user updates the employment and/or school enrollment data. In the '''regular''' mode, DaySim uses the shadow price file generated during the '''shadowprice''' run as the seed shadow price and runs only one loop of shadow pricing. The location of the seed shadow price file is specified in the '''SETTINGS''' user-defined table

3.7 Daysim Inputs

2023-03-11T01:03:16Z

Bpaul:

[[Category:3.0 Model Design]]

The following sections provide a brief overview of the inputs to the DaySim components of the model system.

<h2>Microzones (MAZ)</h2>

The NERPM activity-based model system uses microzones as the fundamental spatial unit for generating travel demand. Use of microzones improves the sensitivity of the model system to land use, fine-grained urban form and accessibility attributes. The microzone data input file contains fields that describe the quantities of households, school enrollment by type and employment by industrial sector within quarter mile and half-mile buffers. Note that these buffers are based on “all streets” based network accessibilities and employ decay functions that weight closer opportunities more than distant opportunities.

<h2>Synthetic Population</h2>

The synthetic population is comprised of lists of households and persons that are based on observed or forecasted distributions of socioeconomic attributes and are typically created by sampling detailed Census microdata. These lists function as the basis for all subsequent choice-making simulated in the activity-based model. The PopulationSim synthetic population tool was used to generate the synthetic population input to the NERPM-AB Daysim activity-based model system. Details pertaining to the design of synthetic population were described in the previous section.

<h2>Worker IXXI Fractions</h2>

Although the modeling area is defined in such a way as to capture as much “internal” travel by regional residents as possible (that is, travel with both origins and destinations with the modeling area), a certain portion of observed regional travel involves either regional residents travelling to destinations outside the modeling area or people who are not regional residents travelling to destinations within the modeling area. As in a traditional trip-based travel demand model system, these travel markets are typically incorporated into the model through the use of internal-external trip tables, which may be either fixed or dynamic.

A distinguishing feature of the DaySim activity-based model system is that, due to the spatial and behavioral detail embedded in the model, it is sensitive to how this internal-external travel affects the choices made by regional residents. A particular focus of this detail is on ensuring that the right numbers of workers are “out-commuting” to employment locations outside the modeling area, and that the right number of regional jobs are being consumed by non-residents “in-commuting” to the region. At present, this is accomplished by using a file (worker IXXI fractions) that contains TAZ-based shares of workers who are in-commuting and out-commuting, which is provided as an external input to the DaySim model system. The shares either can be held fixed, or may be updated by deriving updates shares from the trip-based model outputs.

The “out-commuting’ proportion of workers in each TAZ are assumed to go to work locations outside the model region. Since ABM involves simulating choices of each individual in the synthetic population, the workers that “out-commute” are determined as a probabilistic choice based on the fraction specified in the IXXI file. DaySim does not simulate the day patterns of such workers. Similarly, the “in-commuting” proportion results in a portion of job in each TAZ not being available for workers in the model region. These are assumed to be taken up workers from outside the model region.

<h2>TAZ Indexes</h2>

The TAZ index file enables users to flexibly define non-continuous zones numbering systems, and to identify the availability of external and other zones as destination choices, without impacting DaySim performance.

<h2>PNR Nodes</h2>

The PNR file provides park-and-ride (PNR) and kiss-and-ride (KNR) locations with corresponding capacity and parking cost. The locations of these nodes are used by DaySim inform the choice of PNR station for a PNR transit trip.

<h2>Coefficients</h2>

A coefficient file provides a list of variables used in the model and corresponding coefficient values and t-statistics. Each Daysim model component is associated with a coefficient file. For the NERPM-AB model, the model coefficients were borrowed from SACOG model and later calibrated to match Jacksonville survey data.

<h2>Roster</h2>

A key set of inputs to any travel demand forecasting model system are the files that contain the scenario, mode, user-class, and time period-specific measures of network impedance, often referred to as network “skims.” The roster provides users with the ability to flexibly specify the skims that are associated with the different mode, time period and user classes used in the NERPM activity-based models system, without necessitating changes to the core DaySim model code. For example, a user may want to increase the number of time periods used in the model system to better reflect changes in network impedance by detailed time-of-day. In order to implement such an enhancement, a user would first revise the network skimming procedure settings in PTV Visum in order to generate the desired skims and would only need to revise the DaySim impedance roster to make DaySim sensitive to this additional detail.

<h2>Roster Combinations</h2>

The "Roster Combinations" file gives the possible mode/path type combinations used in DaySim. The file has columns that enumerate the 9 modes used in the current model system (walk, bike, SOV, HOV2, HOV3, transit, park-and-ride, school-bus, other) and 8 rows that enumerate the path types currently used (full-network, local-bus, and local-bus-knr). The cells are TRUE for valid combinations within DaySim and FALSE otherwise.

3.6 Updating Input Data

2023-03-11T01:00:44Z

Bpaul:

Most input data in NERPM-AB is stored within the Visum version file. The MAZs in NERPM-AB are represented as the Point of Interest (POI) layer. TAZs are represented as Zones. The MAZ and TAZ level data is stored as the POI and Zone database (referred to as ‘list’ in Visum). The link and node level data are stored in the link and node lists. The lists can be viewed from the ‘Lists’ menu item as shown below in Figure 3-2.

'''FIGURE 3-2 PTV Visum List Menu'''

[[File:ListMenu.png]]

The data specific to tools are stored in their respective directories. For example, the seed sample and marginal control distribution data for PopulationSim are stored in the appropriate folder within the Population Synthesis directory (\tools\Population_Synthesis). The all-streets network data required for DaySim data tools are stored in the appropriate DaySim data tools directories (\tools\DaySim_Data_Tools).

The input data processing in NERPM-AB is streamlined using the Visum procedure sequence (''Synthetic Population/DaySim Data Tools'' group). Visum interfaces with various tools via Python scripts. The tools need to be run in a specific sequence as outputs from one tool become input to the next tool. The exchange of data between various tools is fully automated. All tools need to be run only once for each model run. For subsequent runs, these tools need to be run only when specific inputs are changed. The flowchart below shows the input data workflow between various tools.

'''FIGURE 3-3 NERPM-AB V2.2 DATA PROCESSING WORKFLOW'''

[[File:DataProcessingWorkflow.png]]

Below are instructions on making a few example input data changes.

<h2>Adding 100 households to a MAZ</h2>

Assuming the tools in the Synthetic Population/DaySim Data Tools group have been run at least once, follow these steps to add 100 households to a MAZ:

*Open network editor
[[File:OpenNetworkEditor.png]]

*Switch on and activate the POI layer in the '''Network''' panel:
[[File:POILayer.png]]

*Locate the MAZ to be updated on the map or use the ‘find network object’ feature by pressing the F3 key on the keyboard or clicking the search icon on the network editor menu bar:
[[File:FindPOI.png]]

Enter the MAZ ID of interest in the search network object and right-click to zoom into the object

[[File:POI_zoom.png]]

*After locating the MAZ/POI, double-click the network object to open the edit POI view. Go to the ‘User-defined attributes’ tab. Update the HH15 field if making changes to the base year model or update the appropriate field.

[[File:Edit_POI.png]]

*After updating the appropriate field, run the ‘Synthetic Population/DaySim Data Tools’ group with the following procedures activated:

[[File:MAZ_HH_Update.png]]

Alternatively, load the ‘MAZ_HH_Update.xml’ procedure parameters file which has the settings saved for this modeling task. Left-click on the ‘open procedure parameters’ icon:

[[File:Open_Procedure_Seq.png]]

Select the ‘MAZ_HH_Update.xml’ from the procedures directory in the '''open procedure parameters''' window. Thereafter, follow the steps in the [[5.3 DaySim Input Preparation - Running the Model]] section to run the procedure sequence with the activated procedures.

[[File:Select_procedure_seq.png]]

<h2>Adding 100 employment to a MAZ</h2>

Assuming the tools in the Synthetic Population/DaySim Data Tools group have been run at least once, follow these steps to update the employment data of a specific MAZ:

*Open network editor
[[File:OpenNetworkEditor.png]]

*Switch on and activate the POI layer in the '''Network''' panel:
[[File:POILayer.png]]

*Locate the MAZ to be updated on the map or use the ‘find network object’ feature by pressing the F3 key on the keyboard or clicking the search icon on the network editor menu bar:
[[File:FindPOI.png]]

Enter the MAZ ID of interest in the search network object and right-click to zoom into the object

[[File:POI_zoom.png]]

* After locating the MAZ/POI, double-click the network object to open the edit POI view. Go to the ‘User-defined attributes’ tab. Update the appropriate employment data field.
[[File:Edit_POI_emp.png]]

*After updating the appropriate field, run the ‘Synthetic Population/DaySim Data Tools’ group with the following procedures activated
[[File:MAZ_Emp_Update.png]]

Alternatively, load the ''MAZ_Emp_Update.xml'' procedure parameters file which has the settings saved for this modeling task. The '''export TAZ data''' step aggregates the MAZ-level employment data to update the TAZ-level data. Thereafter, follow the steps in the [[5.3 DaySim Input Preparation - Running the Model]] section to run the procedure sequence with the activated procedures.

<h2>Adding additional room to a TAZ</h2>

Assuming the tools in the Synthetic Population/DaySim Data Tools group have been run at least once, follow these steps to update the hotel room data of a specific TAZ:

*Open network editor
[[File:OpenNetworkEditor.png]]

*Switch on and activate the ‘Zones’ layer in the ‘Network’ tool window:
[[File:Activate_zones_layer.png]]

*Locate the TAZ to be updated on the map or use the ‘find network object’ feature by pressing the F3 key on the keyboard or clicking the search icon on the network editor menu bar:
[[File:Find_Zone.png]]

*After locating the TAZ/Zone, double-click the network object to open the edit Zone view. Go to the ‘User-defined attributes’ tab. Update the ‘HMUNITS’ data field
[[File:Edit_Zone_Hotel.png]]

*After updating the appropriate field, run the ‘Synthetic Population/DaySim Data Tools’ group with the following procedures activated:
[[File:MAZ_Hotel_Update.png]]

Alternatively, load the ''MAZ_Hotel_Update.xml'' procedure parameters file which has the settings saved for this modeling task. Thereafter, follow the steps in the [[5.3 DaySim Input Preparation - Running the Model]] section to run the procedure sequence with the activated procedures.

<h2>Activate a dummy TAZ</h2>

Follow these steps to activate a dummy TAZ

*Open network editor
[[File:OpenNetworkEditor.png]]

*Switch on and activate the ‘Zones’ layer in the ‘Network’ tool window:
[[File:Activate_zones_layer.png]]

*Locate the dummy TAZ to be activated
[[File:Edit_zones_buffer.png]]

*Relocate dummy TAZ centroid to the appropriate location by holding the left-click and dragging across the network.

*Next, switch on and activate the connectors layer
[[File:Activate_connector_layer.png]]

*Add connectors from the moved dummy TAZ centroid to appropriate points on the network by activating the insert mode on the network editor:
[[File:Insert_connector.png]]

*Double-click the newly added centroid connectors and update the connector attributes as needed
[[File:Edit_connector.png]]

*Next, identify existing MAZs to be associated with the dummy TAZ. Activate the POI layer and double-click the identified MAZ to open the edit POI window.
[[File:Edit_POI_buffer.png]]

*Select the ‘Allocation’ tabs and filter the network object type to Zones.
[[File:Edit_POI_allocation.png]]

*Click the ‘Edit allocations’ button
[[File:Edit_allocation.png]]

*Search for dummy TAZ ID and click confirm the selection
[[File:Find_dummy_TAZ.png]]

*Follow the prompts to finalize the allocation

*TAZ level marginal controls may need to be updated for PopulationSim. If not specified, regional distributions are automatically applied to the dummy TAZ. The required TAZ level variables are aggregated from the MAZ-level data based on the updated MAZ-TAZ allocation.

*Finally, run the ‘Synthetic Population/DaySim Data Tools’ group with the following procedures activated
[[File:Activate_dummy_TAZ.png]]

Alternatively, load the ''Activate_Dummy_TAZ.xml'' procedure parameters file which has the settings saved for this modeling task. The '''export TAZ data''' step aggregates the MAZ-level employment data to update the TAZ-level data. Thereafter, follow the steps in the [[5.3 DaySim Input Preparation - Running the Model]] section to run the procedure sequence with the activated procedures.