CUBE Preparing Data and Scripting

1
CUBEPreparing Data and Scripting

• Jong S Lee

2
Modeling Network
3
How can we represent the streets in order to use
in the computer?
4
Is it enough?
How about one-way street?
5
Is it enough?
How about the turn restrictions?
6
Single node representation
Expanded representation
Miller, J. H. Shaw, S. (2001), Geographic
Information Systems for Transportation
Principles and Applications, 56
7
Modeling Network

• Traffic network is represented by two types of
  elements
• a set of points -gt Nodes
• a set of line segments connecting these points -gt
  links

8

• The figure below depicts a set of network
  including five nodes connected by 10 links. For
  example, link 5 represents flow from node 3 to
  node 2, while link 6 represents the reverse flow,
  2 3.

9
TAZ

• Origins and destinations are locations where
  trips originate or terminate. In reality, these
  locations are distributed almost continuously in
  a given study area
• These locations are often spatially aggregated
  into traffic analysis zones for computational
  tractability
• Each traffic analysis zone (TAZ) is represented
  by a node known as centroid.
• The centroids are those source and sink nodes
  where traffic originates and to which traffic is
  destined.

10

• The figure shows a traffic zone that is
  surrounded by four two-way streets. The node in
  the middle of the zone is the centroid and it is
  connected to the roadway network by special
  centroid connector links.

11
Matrix
12
Matrix
Column Vector (Origin Matrix)
Row Vector (Destination Matrix)
13
Lab 1
14
Developing Highway Network

• You can build a highway network from a shapefile
• Cube needs to know about the shapfile such as
• A-node (from node) and B-node (to node) field
• 1-way/2-way option
• Distance option
• Starting new node number (not zone centroid
  number)
• Highest zone number

15
(No Transcript)
16
Developing Highway Network

• Initially network contains the abstract
  representation of links and nodes. (not true
  shape of street link)
• You can turn on true shape display option
• You can add zone centroids based on boundary
  layer (shapefile)
• With the zone centroids, you can add zone
  centroid connectors

17
(No Transcript)
18
Developing Highway Network

• After generating connectors, you need to set
  attributes (such as speed, number of lanes and so
  on)
• _CENTROID variable automatically generated
• 1 centroid or centroid connector
• 0 regular node and links

19
Map display and Legend

• You can display different color or symbol based
  on the attribute
• A criterion consists of two parts condition and
  comments
• These two parts are separated by semi-colon
• POPULATION/ACRESlt1 Density lt 1
• The comments can be used in Legend

20
Legend displays the comments in criteria
21
Catalogs

• Catalog
• The Catalog File is the only file which you must
  remember its name and location.
• The Catalog is the root of a model. Everything
  else is linked to it.
• The Catalog tracks all the components of a model
• Applications (Model Processes)
• Model Keys (User Input Data)
• Scenario Data (Unique Sets of Keys)

22
Applications

• Applications
• The Applications are the Model Processes.
• A single Catalog may have many Applications
• Passenger Forecasting
• Sub-Area Analysis
• Impact Studies
• The Application file is a single page which
  tracks data flows and organizes modeling
  functions. These functions may be either from
  Cube Libraries or User Defined.
• Application files may be nested to provide model
  structure.

23
Group code and version No. will be used to
generate a filename automatically
24
Processing Step (program)

• In addition to groups, applications contain
  processing steps.
• These steps can be Cube programs (Voyager,
  TranPlan, TP, Trips, Cargo, Land, ME, DTA)
• These steps can be any user defined program (EXE,
  DLL)

25
Processing Step (program)

• Voyager provides to several steps (programs)

26
Program Structure

• A program has input files, output files, and
  execution order.
• The input files are displayed on the left.
• The output files are displayed on the right.
• The execution order is the number attached
  program.
• Every program has two key files
• Script file Contains Program Instructions
• Automatically created
• Print File Contains Run Results
• Auto-Named by the user

27
Linking Data Files

• Data can be linked in two ways
• Link to File
• A hard link to a specific file. This file cannot
  be changed when running the model scenarios.
• Link to Catalog Key
• A soft link to a user input. For each model
  scenario the user is responsible to verify the
  input.

28
Catalog Keys

• Keys are the parameters that are input to the
  model which the developer would like the applier
  to be able to access and change.
• The values of the Keys are unique for each
  scenario and are tracked by the scenario manager.
  
• Numeric variables, file names, or text strings.
• The user accesses the keys through a user menu by
  double-clicking on a scenario.
• When the developer defines a key, they also
  define the user menu.

29
(No Transcript)
30
Generated Script Files

• When a script file are created and maintained by
  AM
• AM automatically generate the basic structure
• AM keeps track of all the input and output files
• The user
• will add Parameters, Process blocks, Calculations
• should NEVER edit the file names and locations
• All changes to the file names and locations
  should be done in AM

31
Script File Structure
32
Comments

• Comment is any text following a (on the same
  line)
• may be at start of line
• may be midway through a line
• may be midway through a command
• Example
• A1 command followed by comment
• comment line here
• Block comment enclosed by / /
• Example
• A1 / comments start here
• comments end here /
• B2

33
Voyager Programs

• NETWORK
• Building, Comparing and Manipulating Highway
  Networks
• HIGHWAY
• Pathbuilding, Skimming, and Assignment of Highway
  Networks
• PT
• All Public Transit Functions
• GENERATION
• Trip Generation
• DISTRIBUTION
• Trip Distribution
• FRATAR
• Matrix Growth Factoring
• MATRIX
• Demand Modeling and Matrix Manipulations

34
HIGHWAY

• Primary function is to Build Paths between all
  (i,j) pairs
• Once Paths are built, the user may
• Skim network variables
• Assign trips to network
• Input may include
• Highway network
• Zonal matrices
• Zonal data files
• Turn penalties
• Output may include
• Loaded network
• Matrices
• Junction Output Data

35
(No Transcript)
36
Highway PHASELINKREAD

• Defines required values for each link.
• Built-in Variables and Functions may be set here.
• DISTANCE travel distance (or link distance)
• T0 Free-Flow Time (Minutes)
• TIME travel time (T0)
• DIST travel distance (DISTANCE)
• COST travel cost

37
(No Transcript)
38
Highway PHASEILOOP

• Builds paths from each origin zone to every
  destination
• Script
• PATHLOAD
• Defines Process
• PATHTIME,
• Defines Impedance Variable
• MW1PATHTRACE(TIME)
• Skims Network Variable

39
Skims Network Variable MW1 result matrix
number 1 MW2 result matrix number 2 MW3
result matrix number 3 PATHTRACE(value) sum of
link values (Time, Cost, LI. or LW.) on path for
I to J
PATHLOAD Defines Process
PATHTIME Defines Impedance Variable

• So, this command generate a matrix file that
  contains three matrices
• travel time for all origin-destination pairs
• Travel distance for all origin-destination pairs
• Travel cost for all origin-destination pairs

40
Highway File Definition

• The user needs to tell the output matrix what
  working matrixes will be saved.
• The user may name these matrices
• Script (appended to MATO)
• MO1-3, NAMEBYTIME,BYDIST,BYCOST

41
Script Editor Tips

• F2
• Context-sensitive help
• Right click
• Display possible commands, keys, and so on