http://visummodelwiki.northfloridatpo.com/index.php?action=history&feed=atom&title=6.2_Existing_Scenarios6.2 Existing Scenarios - Revision history2026-05-15T13:47:43ZRevision history for this page on the wikiMediaWiki 1.27.1http://visummodelwiki.northfloridatpo.com/index.php?title=6.2_Existing_Scenarios&diff=722&oldid=prevBpaul at 07:20, 13 March 20232023-03-13T07:20:13Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;' lang='en'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 07:20, 13 March 2023</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"><p></del>In <del class="diffchange diffchange-inline">Cube a </del>scenario <del class="diffchange diffchange-inline">defines </del>a <del class="diffchange diffchange-inline">value for each key in the catalog</del>. <del class="diffchange diffchange-inline">NERPM-AB come </del>with <del class="diffchange diffchange-inline">3 </del>predefined scenarios<del class="diffchange diffchange-inline">, </del>Base2015<del class="diffchange diffchange-inline">, INT2030 </del>and CF2045. These <del class="diffchange diffchange-inline">3 </del>scenarios can be used as-is to get results for these standard years. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3. <del class="diffchange diffchange-inline">If this new scenario involves changes to the roadway network then the steps in <em><strong>Create a Master Network Alternative</strong> </em>to create an alternative should be followed. If the new scenario includes changes to demographic (population or employment) inputs then the steps in section 5.1.2 can be used to edit the parcel file and produce updated DaySim inputs. Finally, if the scenario is for a new year other than 2015, 2030, or 2045 then a new network alternative will need to be created (<em><strong>Create a Master Network Alternative</strong></em>) along with new DaySim inputs (section 5.1.2 Generate default files)</p></del></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>In <ins class="diffchange diffchange-inline">NERPMAB v2.2, each </ins>scenario <ins class="diffchange diffchange-inline">is defined in </ins>a <ins class="diffchange diffchange-inline">separate version file</ins>. <ins class="diffchange diffchange-inline">The model package comes </ins>with <ins class="diffchange diffchange-inline">two </ins>predefined scenarios <ins class="diffchange diffchange-inline">- </ins>Base2015 and CF2045. These <ins class="diffchange diffchange-inline">two </ins>scenarios can be used as-is to get results for these standard years<ins class="diffchange diffchange-inline">. The two version files contain MAZ data for 2030</ins>. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3.</div></td></tr>
</table>Bpaulhttp://visummodelwiki.northfloridatpo.com/index.php?title=6.2_Existing_Scenarios&diff=461&oldid=prevBstabler at 15:10, 9 November 20202020-11-09T15:10:24Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;' lang='en'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 15:10, 9 November 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p>In Cube a scenario defines a value for each key in the catalog. NERPM-AB come with 3 predefined scenarios, <del class="diffchange diffchange-inline">Base2010</del>, INT2030 and <del class="diffchange diffchange-inline">CF2040</del>. These 3 scenarios can be used as-is to get results for these standard years. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3. If this new scenario involves changes to the roadway network then the steps in <em><strong>Create a Master Network Alternative</strong> </em>to create an alternative should be followed. If the new scenario includes changes to demographic (population or employment) inputs then the steps in section 5.1.2 can be used to edit the parcel file and produce updated DaySim inputs. Finally, if the scenario is for a new year other than <del class="diffchange diffchange-inline">2010</del>, 2030, or <del class="diffchange diffchange-inline">2040 </del>then a new network alternative will need to be created (<em><strong>Create a Master Network Alternative</strong></em>) along with new DaySim inputs (section 5.1.2 Generate default files)</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p>In Cube a scenario defines a value for each key in the catalog. NERPM-AB come with 3 predefined scenarios, <ins class="diffchange diffchange-inline">Base2015</ins>, INT2030 and <ins class="diffchange diffchange-inline">CF2045</ins>. These 3 scenarios can be used as-is to get results for these standard years. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3. If this new scenario involves changes to the roadway network then the steps in <em><strong>Create a Master Network Alternative</strong> </em>to create an alternative should be followed. If the new scenario includes changes to demographic (population or employment) inputs then the steps in section 5.1.2 can be used to edit the parcel file and produce updated DaySim inputs. Finally, if the scenario is for a new year other than <ins class="diffchange diffchange-inline">2015</ins>, 2030, or <ins class="diffchange diffchange-inline">2045 </ins>then a new network alternative will need to be created (<em><strong>Create a Master Network Alternative</strong></em>) along with new DaySim inputs (section 5.1.2 Generate default files)</p></div></td></tr>
</table>Bstablerhttp://visummodelwiki.northfloridatpo.com/index.php?title=6.2_Existing_Scenarios&diff=231&oldid=prevGwineman at 14:34, 18 October 20162016-10-18T14:34:12Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;' lang='en'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 14:34, 18 October 2016</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>[[Category:6.0 Configuring a Scenario]]</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"><p>In Cube a scenario defines a value for each key in the catalog. NERPM-AB come with 3 predefined scenarios, Base2010, INT2030 and CF2040. These 3 scenarios can be used as-is to get results for these standard years. If a different scenario needs to be tested, then a new scenario should be created as detailed in section 6.3. If this new scenario involves changes to the roadway network then the steps in <em><strong>Create a Master Network Alternative</strong> </em>to create an alternative should be followed. If the new scenario includes changes to demographic (population or employment) inputs then the steps in section 5.1.2 can be used to edit the parcel file and produce updated DaySim inputs. Finally, if the scenario is for a new year other than 2010, 2030, or 2040 then a new network alternative will need to be created (<em><strong>Create a Master Network Alternative</strong></em>) along with new DaySim inputs (section 5.1.2 Generate default files)</p></ins></div></td></tr>
</table>Gwinemanhttp://visummodelwiki.northfloridatpo.com/index.php?title=6.2_Existing_Scenarios&diff=226&oldid=prevGwineman: Created page with "Category:6.0 Configuring a Scenario"2016-10-18T14:26:57Z<p>Created page with "<a href="/Category:6.0_Configuring_a_Scenario" title="Category:6.0 Configuring a Scenario">Category:6.0 Configuring a Scenario</a>"</p>
<p><b>New page</b></p><div>[[Category:6.0 Configuring a Scenario]]</div>Gwineman