Difference between revisions of "6.2 Existing Scenarios"

Latest revision as of 07:20, 13 March 2023

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.

Revision as of 15:10, 9 November 2020 (view source) Bstabler (talk \| contribs) ← Older edit		Latest revision as of 07:20, 13 March 2023 (view source) Bpaul (talk \| contribs)
Line 1:		Line 1:
	[[Category:6.0 Configuring a Scenario]]		[[Category:6.0 Configuring a Scenario]]

−	~~<p>~~In ~~Cube a~~ scenario ~~defines~~ a ~~value for each key in the catalog~~. ~~NERPM-AB come~~ with 3 predefined scenarios, Base2015~~, INT2030~~ and CF2045. 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 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>	+	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.