visummodelwiki - User contributions [en]

7.4 Version NERPMAB2.2

2023-03-13T07:50:58Z

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

7.4 Version NERPMAB2.2

2023-03-13T07:47:53Z

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 Visum model provides various other benefits such as:

- faster run times
- ABM data visualization
- On-the-fly flow bundles

7.4 Version NERPMAB2.2

2023-03-13T07:47:34Z

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 Visum model provides various other benefits such as:

- faster run times
- ABM data visualization
- On-the-fly flow bundles

7.4 Version NERPMAB2.2

2023-03-13T07:46:34Z

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 Visum model provides various other benefits such as:

* faster run times
* ABM data visualization
* On-the-fly flow bundles

7.4 Version NERPMAB2.2

2023-03-13T07:46:22Z

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 Visum model provides various other benefits such as:
* faster run times
* ABM data visualization
* On-the-fly flow bundles

7.4 Version NERPMAB2.2

2023-03-13T07:45:57Z

Bpaul: Created page with "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..."

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 Visum model provides various other benefits such as:
* faster run times
* ABM data visualization
* On-the-fly flow bundles

Chapter: 7.0 Version Updates

2023-03-13T07:31:40Z

Bpaul:

*[[7.1 Version NERPMAB1v2]]
*[[7.2 Version NERPMAB1v3]]
*[[7.3 Version NERPMAB2]]
*[[7.4 Version NERPMAB2.2]]

File:Update scenario settings.png

2023-03-13T07:30:47Z

Bpaul: Bpaul uploaded a new version of File:Update scenario settings.png

File:Add scenario directory.png

2023-03-13T07:30:37Z

Bpaul: Bpaul uploaded a new version of File:Add scenario directory.png

6.3 Creating a New Scenario

2023-03-13T07:29:22Z

Bpaul:

[[Category:6.0 Configuring a Scenario]]

Follow these steps to create a new scenario:

* To create a 2015 or 2045 scenario, open the respective version file and create a copy using the "Save As" option.

* Update the network or land use data as per the specification for the scenario

* Add a scenario directory in the /Scenario sub-directory. Since the directory structure remains the same, simply copy the Base2015 folder and rename it appropriately

[[File:add_scenario_directory.png]]

* Update the model settings as needed

[[File:Update_scenario_settings.png]]

File:Update scenario settings.png

2023-03-13T07:28:40Z

Bpaul:

File:Add scenario directory.png

2023-03-13T07:28:22Z

Bpaul:

6.3 Creating a New Scenario

2023-03-13T07:28:11Z

Bpaul: Replaced content with "Category:6.0 Configuring a Scenario Follow these steps to create a new scenario: * To create a 2015 or 2045 scenario, open the respective version file and create a c..."

6.2 Existing Scenarios

2023-03-13T07:20:13Z

Bpaul:

[[Category:6.0 Configuring a Scenario]]

In NERPMAB v2.2, each scenario is defined in a separate version file. The model package comes with two predefined scenarios - Base2015 and CF2045. These two scenarios can be used as-is to get results for these standard years. The two version files contain MAZ data for 2030. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3.

6.1 General Overview

2023-03-13T07:01:45Z

Bpaul:

<p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP
“2045 Path Forward” effort. These are for the years 2015, 2018 (E+C), 2030 and
2045. The information regarding the period of
construction related to the planned roadway projects within the North Florida
TPO’s area is listed in [http://pathforward2045.com/wp-content/uploads/2020/05/2045-Cost-Feasible-Plan-Tech-Report-VR03-5_6_20.pdf 2045 Cost Feasible Plan Technical Report].</p><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Scenarios\{SCENARIO_NAME}\
Input\DaySimInput\02_Parcel\buffered_maz_year.dat. Follow the instructions in [[3.6 Updating Input Data]] section to configure the model procedure sequence for land-use data changes</p>

<h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\02_Parcel\
buffered_maz_year.dat)</li><li>Household file
(\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\03_Household\household_year.dat)</li><li>Person file
(\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\04_Person\person_year.dat)</li></ul>

<p class="BodyParagraph">To update the buffered parcel file, follow the instructions in [[3.6 Updating Input Data]] section to configure the model procedure sequence for land-use data changes.</p>

<p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is
generated using PopulationSim. NERPMAB v2.2 has been designed to handle synthetic population update relating to changes in zonal households. the update_controls.py Python script adjusts the PopulationSim controls as per changes in the number of households at the MAZ level. For more significant changes involving changes in distributions, the marginal control files for population synthesis will need to be updated manually. After that synthetic population needs to be generated using the new input files (Please refer to PopulatinSim guide for synthesis instructions).</p>

6.1 General Overview

2023-03-13T06:53:14Z

Bpaul:

<p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP
“2045 Path Forward” effort. These are for the years 2015, 2018 (E+C), 2030 and
2045. The information regarding the period of
construction related to the planned roadway projects within the North Florida
TPO’s area is listed in [http://pathforward2045.com/wp-content/uploads/2020/05/2045-Cost-Feasible-Plan-Tech-Report-VR03-5_6_20.pdf 2045 Cost Feasible Plan Technical Report].</p><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Scenarios\{SCENARIO_NAME}\
Input\DaySimInput\02_Parcel\buffered_maz_year.dat. Follow the instructions in [[3.6 Updating Input Data]] section to configure the model procedure sequence for land-use data changes</p>

<h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\02_Parcel\
buffered_maz_year.dat)</li><li>Household file
(\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\03_Household\household_year.dat)</li><li>Person file
(\Scenarios\{SCENARIO_NAME}\Input\DaySimInput\04_Person\person_year.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps
as employment change accommodation needs to be performed. First, the land-use file (output of the allocation tool) is updated and then it is used in the buffering tool to generate a new buffered parcel file that goes into DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is
generated using PopulationSim. The marginal control files for population synthesis need to be updated to reflect the new control totals. After that synthetic population needs to be generated using the new input files (Please refer to PopulatinSim guide for synthesis instructions).</p>

6.1 General Overview

2023-03-13T06:50:16Z

Bpaul:

<p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP
“2045 Path Forward” effort. These are for the years 2015, 2018 (E+C), 2030 and
2045. The information regarding the period of
construction related to the planned roadway projects within the North Florida
TPO’s area is listed in [http://pathforward2045.com/wp-content/uploads/2020/05/2045-Cost-Feasible-Plan-Tech-Report-VR03-5_6_20.pdf 2045 Cost Feasible Plan Technical Report].</p><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Scenarios\{SCENARIO_NAME}\
Input\DaySimInput\02_Parcel\buffered_maz_year.dat. Follow the instructions in [[3.6 Updating Input Data]] section to re-run the model with land-use data updates</p>

<h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Master\{SCENARIO_DIR}\Input\DaySimInput\02_Parcel\
buffered_maz_year.dat)</li><li>Household file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\03_Household\household_year.dat)</li><li>Person file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\04_Person\person_year.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps
as employment change accommodation needs to be performed. First, the land-use file (output of the allocation tool) is updated and then it is used in the buffering tool to generate a new buffered parcel file that goes into DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is
generated using PopulationSim. The marginal control files for population synthesis need to be updated to reflect the new control totals. After that synthetic population needs to be generated using the new input files (Please refer to PopulatinSim guide for synthesis instructions).</p>

6.1 General Overview

2023-03-13T06:50:08Z

Bpaul:

<p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP
“2045 Path Forward” effort. These are for the years 2015, 2018 (E+C), 2030 and
2045. The information regarding the period of
construction related to the planned roadway projects within the North Florida
TPO’s area is listed in [http://pathforward2045.com/wp-content/uploads/2020/05/2045-Cost-Feasible-Plan-Tech-Report-VR03-5_6_20.pdf 2045 Cost Feasible Plan Technical Report].</p><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Scenarios\{SCENARIO_NAME}\
Input\DaySimInput\02_Parcel\buffered_maz_year.dat. Follow the instructions in [[3.6 Updating Input Data]] section to re-run the model with land-use data updates</p>

</ul><h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Master\{SCENARIO_DIR}\Input\DaySimInput\02_Parcel\
buffered_maz_year.dat)</li><li>Household file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\03_Household\household_year.dat)</li><li>Person file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\04_Person\person_year.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps
as employment change accommodation needs to be performed. First, the land-use file (output of the allocation tool) is updated and then it is used in the buffering tool to generate a new buffered parcel file that goes into DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is
generated using PopulationSim. The marginal control files for population synthesis need to be updated to reflect the new control totals. After that synthetic population needs to be generated using the new input files (Please refer to PopulatinSim guide for synthesis instructions).</p>

6.1 General Overview

2023-03-13T06:49:01Z

Bpaul:

<p><strong><em>Network Change</em></strong></p><p class="BodyParagraph">There are four networks officially part of the LRTP
“2045 Path Forward” effort. These are for the years 2015, 2018 (E+C), 2030 and
2045. The information regarding the period of
construction related to the planned roadway projects within the North Florida
TPO’s area is listed in [http://pathforward2045.com/wp-content/uploads/2020/05/2045-Cost-Feasible-Plan-Tech-Report-VR03-5_6_20.pdf 2045 Cost Feasible Plan Technical Report].</p><p></p><h4 id="id-6.1GENERALOVERVIEW-EmploymentChange"><em>Employment Change</em></h4><p class="BodyParagraph">In future, some areas may see growth/decline in employment due to increase/decrease in business establishments or some other reasons. In addition, the distribution of different employment types could change over the years.</p><p class="BodyParagraph">In order to reflect those changes in the model, the DaySim buffered parcel file needs to be updated - \Scenarios\{SCENARIO_NAME}\
Input\DaySimInput\02_Parcel\buffered_maz_year.dat. Follow the instructions in [[3.6 Updating Input Data]] section to re-run the model with land-use data updates</p>

</li></ul><h4 id="id-6.1GENERALOVERVIEW-PopulationChange"><em>Population Change</em></h4><p class="BodyParagraph">After a base year population has been synthesized, new synthetic populations may need to be generated based on the type scenario being run or the policy being tested. For example, a change in the network may not require the population to be synthesized again. On the other hand, if a land-use policy variable is being tested which would result in significantly different patterns in the population and employment levels in the TAZs than in the base case, a new synthetic population would be have to be generated. The same would be the case for a future year run when the population mix or distribution of specific population characteristics may deviate from those in the base synthetic population. Population is likely to increase in future, however, it may not increase proportionately geographically. A change in employment may also alter the existing geographic distribution of the population. To accommodate a change in population following three input files need to be updated:</p><ul><li>Buffered parcel file (\Master\{SCENARIO_DIR}\Input\DaySimInput\02_Parcel\
buffered_maz_year.dat)</li><li>Household file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\03_Household\household_year.dat)</li><li>Person file
(\Master\{SCENARIO_DIR}\Input\DaySimInput\04_Person\person_year.dat)</li></ul><p class="BodyParagraph">To update the buffered parcel file, the similar steps
as employment change accommodation needs to be performed. First, the land-use file (output of the allocation tool) is updated and then it is used in the buffering tool to generate a new buffered parcel file that goes into DaySim.</p><p class="BodyParagraph">Synthetic population data (household and person files) would also need updates. As previously described, the synthetic population is
generated using PopulationSim. The marginal control files for population synthesis need to be updated to reflect the new control totals. After that synthetic population needs to be generated using the new input files (Please refer to PopulatinSim guide for synthesis instructions).</p>

5.3 Running the Model

2023-03-13T06:35:26Z

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.

File:Save version.png

2023-03-13T06:34:12Z

Bpaul:

5.3 Running the Model

2023-03-13T06:34:03Z

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_procedure_sequence.png]]

5.3 Running the Model

2023-03-13T06:30:41Z

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]]

5.3 Running the Model

2023-03-13T06:30:20Z

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] | 3.8 Configuration]

5.3 Running the Model

2023-03-13T06:29:12Z

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.

File:Set project directory.png

2023-03-13T06:14:08Z

Bpaul: Bpaul uploaded a new version of File:Set project directory.png

File:Procedure seq menu.png

2023-03-13T06:12:39Z

Bpaul:

File:Select project directory.png

2023-03-13T06:12:30Z

Bpaul:

File:Edit project directory.png

2023-03-13T06:12:21Z

Bpaul:

File:Set project directory.png

2023-03-13T06:12:10Z

Bpaul:

5.3 Running the Model

2023-03-13T06:07:43Z

Bpaul:

5.3 Running the Model

2023-03-13T06:07:07Z

Bpaul:

5.3 Running the Model

2023-03-13T06:05:44Z

Bpaul: Created page with "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 f..."

Chapter: 5.0 User Interface & Running the Model

2023-03-13T06:05:08Z

Bpaul:

PTV Visum serves as the Graphical User Interface (GUI) for the NERPMAB v2.2. The software is used to view, edit, and execute the procedure sequence which runs the model steps sequentially in the prescribed sequence. The procedure sequence steps interface with other model components such as PopulationSim, DaySim, DaySim Data Tools, etc. using the Python API, and executes them using stored configuration settings and input data. All the tools that generate inputs for DaySim have been integrated to run from within Visum. However, the user can still run these tools independently if needed. The following sections provide details on running these tools and finally instructions on running NERPMAB v2.2.

*[[5.1 Running DaySim Data Tools]]
*[[5.2 Running PopulationSim]]
*[[5.3 Running the Model]]

5.2 Running PopulationSim

2023-03-13T06:03:47Z

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.2 Running PopulationSim

2023-03-13T06:00:01Z

Bpaul: Created page with "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 TAZ..."

[[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. The video webinar also demonstrates the process in detail. </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]]

Chapter: 5.0 User Interface & Running the Model

2023-03-13T05:59:57Z

Bpaul:

5.1 Running DaySim Data Tools

2023-03-13T05:59:33Z

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]]

5.1 Running DaySim Data Tools

2023-03-13T05:57:40Z

Bpaul:

5.1 Running DaySim Data Tools

2023-03-13T05:57:22Z

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.

[[File:Buffertool.png]]

File:DaySim data tools.png

2023-03-13T05:56:50Z

Bpaul:

5.1 Running DaySim Data Tools

2023-03-13T05:55:38Z

Bpaul: Created page with "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 Da..."

[[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:Datatools.JPG]]

<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.

[[File:Buffertool.png]]

Chapter: 5.0 User Interface & Running the Model

2023-03-13T05:55:34Z

Bpaul:

Chapter: 5.0 User Interface & Running the Model

2023-03-13T05:51:13Z

Bpaul:

PTV Visum serves as the Graphical User Interface (GUI) for the NERPMAB v2.2. The software is used to view, edit, and execute the procedure sequence which runs the model steps sequentially in the prescribed sequence. The procedure sequence steps interface with other model components such as PopulationSim, DaySim, DaySim Data Tools, etc. using the Python API, and executes them using stored configuration settings and input data. All the tools that generate inputs for DaySim have been integrated to run from within Visum. However, the user can still run these tools independently if needed. The following sections provide details on running these tools and finally instructions on running NERPMAB v2.2.

*[[5.1 DaySim Input Preparation - Running DaySim Data Tools]]
*[[5.2 DaySim Input Preparation - Running PopulationSim]]
*[[5.3 DaySim Input Preparation - Running the Model]]

4.7 Post Processing

2023-03-13T05:45:42Z

Bpaul:

[[Category:4.0 Directory & Data Structures]]

<h2>Reports</h2>

<h3>Highway Assignment Report</h3>

The highway validation report in HTML format is generated in the following directory: \Scenarios\{SCENARIO_NAME}\Output\HTML.

<h3>Transit Assignment Report</h3>

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.

<h3>DaySim Reports</h3>

An established R process is used to automatically execute the summary R scripts and populate the DaySim summary spreadsheets. This process is called from within Visum procedure sequence and executed at the end of the model system run. All these files can all be found in “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” folder of the scenario directory. The summary script is called “main.R” and can be found in \tools\DaySim_Summaries\. The Daysim reports include spreadsheets summarizing the following:

*Usual work location
*Usual school location
*Vehicle availability
*Day Pattern
*Escort tour destination
*Personal business tour destination
*Shop tour destination
*Meal tour destination
*Social / recreational tour destination
*Work-based tour destination
*Tour mode
*Tour time-of-day
*Trip destination
*Trip mode
*Trip time-of-day

The DaySim summaries are also output in “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” folder of the scenario directory. All the summaries are *.xlsm spreadsheets that are macro-enabled which updates the calculations and graphs in them automatically each time they are opened. The summaries range from work place distance distribution to tour/trip generation rates to modal shares.

Prior to the running of R summary script, all the spreadsheet templates are copied over to “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” in the scenario directory from “\tools\DaySim_Summaries\output” in the model directory. These help in the validation of DaySim outputs. The summary R script uses files from NHTS that have been processed in the same format as DaySim output files. The processed NHTS files for Florida that include the add-on survey can be found in “tools\DaySim_Summaries\NHTS”.

All the steps have been fully automated using Visum's Python API.

4.7 Post Processing

2023-03-13T05:45:23Z

Bpaul:

[[Category:4.0 Directory & Data Structures]]

<h2>Reports</h2>

<h3>Highway Assignment Report</h3>

The highway validation report in HTML format is generated in the following directory: \Scenarios\{SCENARIO_NAME}\Output\HTML.

<h3>Transit Assignment Report</h3>

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.

<h3>DaySim Reports</h3>

An established R process is used to automatically execute the summary R scripts and populate the DaySim summary spreadsheets. This process is called from within Visum procedure sequence and executed at the end of the model system run. All these files can all be found in “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” folder of the scenario directory. The summary script is called “main.R” and can be found in \tools\DaySim_Summaries\. The Daysim reports include spreadsheets summarizing the following:

*Usual work location
*Usual school location
*Vehicle availability
*Day Pattern
*Escort tour destination
*Personal business tour destination
*Shop tour destination
*Meal tour destination
*Social / recreational tour destination
*Work-based tour destination
*Tour mode
*Tour time-of-day
*Trip destination
*Trip mode
*Trip time-of-day

The DaySim summaries are also output in “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” folder of the scenario directory. All the summaries are *.xlsm spreadsheets that are macro-enabled which updates the calculations and graphs in them automatically each time they are opened. The summaries range from work place distance distribution to tour/trip generation rates to modal shares.

Prior to the running of R summary script, all the spreadsheet templates are copied over to “\Scenarios\{SCENARIO_NAME}\Output\DaySim\Reporting\R_Summary” in the scenario directory from “\tools\DaySim_Summaries\output” in the model directory. These help in the validation of DaySim outputs. The summary R script uses files from NHTS that have been processed in the same format as DaySim output files. The processed NHTS files for Florida that include the add-on survey can be found in “User.prg\DaySim_Summaries\NHTS”.

All the steps have been fully automated using Visum's Python API.

4.6 Network Assignment

2023-03-13T05:38:50Z

Bpaul:

[[Category:4.0 Directory & Data Structures]]

<h2>Assignment Inputs</h2>

<h3>Highway Assignment</h3>

All demand matrices pertaining to different demand segments are stored in the Visum version files matrix objects. The demand matrices from DaySim, Jacksonville port freight, and EE and IEEI vehicle and trucks are combined to create the final assignment matrices using Visum's built-in matrix operations.

All network-level inputs required for the assignment are stored within the Visum version file itself.

<h3>Transit Assignment</h3>

The transit trip tables for both peak and off-peak periods are stored in the Visum version file. All other inputs such as headways and stop locations are also stored in the version file

<h2>Assignment Outputs</h2>

<h3>Highway Assignment</h3>

Highway assignment primarily produces these outputs:

*Loaded highway network containing assigned volumes by time period. Daily link volumes and for each period are stored in user-defined link fields - VOL_AM, VOL_MD, VOL_PM, VOL_EV, VOL_DA
*Skim network for creating skims for the next iteration. These are exported in the required format.

<h3>Transit Assignment</h3>

Transit assignment is performed only in the final iteration of the model run. Boarding and Alighting and stop and route level are all stored in the Visum version file itself.

4.5 Auxiliary Demand

2023-03-13T05:28:47Z

Bpaul:

[[Category:4.0 Directory & Data Structures]]

<h3>Freight</h3>

As described earlier, JAX port freight trips are generated by a Python script (''interpolate_port_truck_tt.py'') that interpolates the JAXPORT demand for 2012 and 2040 to the analysis year between 2010 and 2040 (or beyond) based on the implied growth. The Python script makes use of Visum's Python API to import the JAXPORT trip table into Visum version file.

<h3>Non-HH</h3>

These trip tables are created by the ''tgen_main.py'' Python script using Visum's Python API to access all inputs and import the production (P) and attraction (A) vectors into the version file. These Ps and As are distributed using Trip Distribution procedures in Visum to generate Non-HH trip tables that are combined with DaySim trip tables for assignment.

4.5 Auxiliary Demand

2023-03-13T05:28:38Z

Bpaul:

4.4 DaySim-Visum Linkage

2023-03-13T05:19:30Z

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.