1. From the Calculate menu, choose General procedure settings.
The General procedure settings window opens.
2. In the navigator, select PuT settings > Assignment.
3. Make the desired changes in the Save assignment results section.
|
Element |
Description |
|
Save paths |
Do not save The assignment result stores only the resulting volumes of network objects, the calculated paths are not stored. This option saves memory. As routes Calculated paths are stored as routes, i.e. only the spatial component is stored. As connections Calculated paths are stored as connections, i.e. both the temporal and the spatial component are stored. Note The larger the network the more computation time is required if paths are to be stored as connections. We recommend to only use this option if the path list is required for subsequent analyses or PuT flow bundle calculation (Fundamentals: PuT paths). |
|
Save volumes |
Only for time profiles Network volumes are saved by line, by line route and by time profile. Additionally for vehicle journeys Additionally, the network volume is saved separately by vehicle journey. Note The memory required also increases when storing volumes at the vehicle journey level. We recommend to use this option only if you would like to analyze the volumes by vehicle journey. |
|
Save transfers |
Note This option applies only to the timetable-based assignment. Between time profiles As before, transfers are stored for pairs of time profiles. Both time profile numbers (FromTP and ToTP) are returned. Between vehicle journeys Transfers are saved for pairs of vehicle journeys. Both vehicle journey numbers (FromVehJourney and ToVehJourney) are returned. |
|
Save PJT and search impedance |
Note This option applies only to the headway-based and the timetable-based assignment. The search impedance is not saved when using shortest path search and non-iterative assignments. Do not save Perceived journey time and search impedance are not stored with the assignment. Save The perceived journey time and search impedance are stored beyond the assignment and are displayed in the PuT path list in the columns PerceivedJourneyTime and SearchImp. Note If several demand segments are calculated simultaneously in an assignment, Visum only saves the PJT of the demand segment which is used for the skim matrix as well. |
|
Save imported fare data |
Do not save Fares read in from a connection file are not saved with the assignment. They still take effect within the scope of the impedance calculation. On path level The fare per connection is saved beyond the assignment (PuT path attribute Fare). On path leg level The connection fare prorated for each path leg of the connection is saved beyond the assignment (PuT path leg attribute Fare) Notes During assignment, the fare per path or path leg is calculated by default by the Visum internal fare model. Optionally, they may be replaced by user-defined fares. These may be permanently stores and used for later line costing calculations. Fares are not stored per demand segment but only once per assignment. If several demand segments are calculated simultaneously in an assignment, Visum calculates the fares for the demand segment which is used for the skim matrix as well. This predefinition is necessary since different DSegs may refer to different ticket types and thus different fares, too. Saving fares without regard to demand segment reduces memory requirements for storage capacity and also for connection files *.con. In line costing calculations, the distribution of revenues of paths for which imported fares have been saved is not calculated with the fare model. Instead, it is extracted directly from the entered values. Regardless of this setting, you may calculate and export path-based or path leg-based fares during connection export (Timetable-based assignment: Connection export page). |
|
Save path volumes per demand interval |
If this option is selected, the volumes are displayed per analysis time interval for all public transport paths. The volumes from the intervals of the demand time series are converted to the analysis time intervals. If several demand segments are assigned separately, the analysis time interval is split between the demand segments. The results are displayed in the list PuT paths in the calculated attributes OD trips-Time interval and OD trips-DSeg-Time interval. Note By default this option is not activated due to the high memory requirements. |
The changes are applied. The results of the next PuT assignment will be calculated and stored according to your settings.
