To compare two scenarios, create a comparison pattern. It contains the network objects and attributes that you want to compare. The procedure is the same as for version comparison (Comparing versions and networks). You can use both types of version comparison.
1. Make sure the desired project is open (Editing basic settings of the project).
2. In the Edit project window, click the Comparison patterns tab.
3. Then click the 
Create a comparison pattern icon.
|
Tip: Alternatively, click the |
The Define comparison pattern window opens.
4. Make the desired changes.
|
Element |
Description |
|
Define comparison |
On calculated results of the scenarios If this option is activated, you open the version files of the two scenarios calculated to create a comparison pattern. Select this option e.g. to show calculation results using link bars. On input data of the scenarios If this option is activated, you open the networks of the scenarios to create a comparison pattern. They do not contain any calculation results. This option is used to compare the networks of scenarios. |
|
Scenarios for the comparison definition |
Leading scenario Select the scenario used as a leading version file to create the comparison pattern. This file contains the comparison attributes. Comparison scenario Select the scenario used as a comparison version file to create the comparison pattern. This version file contains the comparison attributes listed in the leading version file. Notes Select the On calculated results of the scenarios option, to only show the calculated scenarios in the drop-down lists. You can change the scenarios you choose here later on, when applying the comparison patterns. You should choose scenarios that contain the data you want to compare, so that you can e.g. select the appropriate graphic parameters. |
|
Header data of the comparison pattern |
Code Code of comparison pattern Description Short description of the comparison pattern |
5. Click the Edit the comparison pattern button.
The Generate version comparison window opens.
Creating a comparison pattern for version comparison, including the adoption of attributes
To perform a version comparison, including the adoption of attributes into the leading network:
6. In the Type of version comparison section, select Use attributes from comparison network.
7. Make the desired changes.
|
Element |
Description |
|
Type of version comparison |
Use attributes from comparison network If this option is selected, Visum adopts the attributes of the comparison network into the leading network. |
|
Load paths |
If this option is selected, the paths of the comparison network are also loaded. Loading paths allows for the evaluation of comparative network volumes even if filtered network volumes are present in the currently loaded network. |
|
Change link bars automatically to differences |
If this option has been selected, scaling and classification attributes of link bars are automatically converted to the new attribute generated by the version comparison with the difference between the original and the newly added attribute value. |
8. Confirm with OK.
The Create version comparison (User-defined) window opens.
9. If required, reduce the amount of data you want to compare.
|
Element |
Description |
|
Hide calculated attributes |
|
|
Hide attributes with default values |
Note You can find the default attribute values in the Attributes.xls file in the ...\Program files\PTV Vision\PTV Visum 2022\Doc folder. |
|
Hide empty tables |
If this option has been selected, only tables containing network objects are compared. |
If this option has been selected, only selected readable attributes and their values are compared additionally to the key attributes.
If this option has not been selected, both readable and non-readable attributes and their values are compared.10. Select the network object types to be compared.
|
Element |
Description |
|
|
This network object type is used for comparison. |
|
|
This network object type is not used for comparison. |
|
Check all tables |
Click this button to select all network object types. |
|
Uncheck all tables |
Click this button to deactivate all network objects and their attributes. |
11. Click a network object type.
The attributes and, if applicable, the subattributes of the network object type are displayed.
|
Tip: Click the Ctrl key and keep it pressed while clicking the desired entries one by one to show the attributes of multiple network object types at the same time. |
|
Note: Due to current settings in the upper section of the window not all attributes of a network object type may be displayed. |
12. Select the attributes and subattributes you want to compare.
|
Element |
Description |
|
|
The attribute has been selected and is compared. |
|
|
The attribute has not been selected and is not compared. |
|
|
The attribute is a key attribute and cannot be switched off. |
|
|
The attribute is a mandatory attribute. |
|
Attribute groups |
Via this button you can either select or switch off predefined groups of attributes in a separate window (Selecting or deselecting groups of attributes for comparison). |
|
Default |
Click this button to hide empty tables and display calculated attributes. The attribute selection is reset to the standard setting. |
|
Tip: Right-click a network object type. On the shortcut menu to activate or deactivate all currently displayed attributes of the network object type. |
|
Tip: Alternatively, you can read selected network object types and attributes from a network file *.net (Reading a selection from a network file). |
13. Confirm with OK.
The selected leading scenario opens as a version file in which you can make further settings.
14. If required, specify the graphic parameters and filter settings in the version file.
|
Tip: To do so, use the corresponding menus or read in new data. |
15. If required, open the lists of your choice in the version file to specify their layout.
|
Tip: You can e.g. show specific columns or load a list layout. |
16. Click the Finish button.
A new entry is then listed in the Comparison patterns tab. The graphic parameters used in the current version file, filter settings and the displayed lists including layouts are saved with the global layout in the comparison pattern.
Creating a comparison pattern for version comparison, including comparison network in the background
If you want to compare versions and keep the comparison network open in the background with the attributes linked via relations, please follow this approach after step 6:
1. Select Load comparison network in the background below Type of version comparison.
|
Note: Visum loads the comparison network in the background and links the attributes with the leading network via relations (Fundamentals: Version comparison). |
2. Specify any further settings you need.
|
Element |
Description |
|
Load matrices |
Note Use this option if you want to display values, differences and relative deviations between matrix values in a zone pair list or main zone pair list. |
|
Load paths |
If this option is selected, the paths of the comparison network are also loaded. Loading paths allows for the evaluation of comparative network volumes even if filtered network volumes are present in the currently loaded network. |
|
Change link bars automatically to differences |
If this option has been selected, scaling and classification attributes of link bars are automatically converted to the new attribute generated by the version comparison with the difference between the original and the newly added attribute value. |
3. Confirm with OK.
The selected leading scenario opens as a version file in which you can make further settings.
4. If required, specify the graphic parameters and filter settings in the version file.
|
Tip: To do so, use the corresponding menus or read in new data. |
5. If required, open the lists of your choice in the version file to specify their layout.
|
Tip: You can e.g. show specific columns or load a list layout. |
6. Click the Finish button.
A new entry is then listed in the Comparison patterns tab. The graphic parameters used in the current version file, filter settings and the displayed lists including layouts are saved with the global layout in the comparison pattern.
