Cube 6.4 Overview

Cube 6.4 Overview
presented by
Robert G. Schiffer, AICP
Director of Professional Services, Citilabs
May 6, 2015
Cube 6.4 Features
Overview
Cube Base
Cube Voyager
Other Cube programs
• Cube 6.4 vs. legacy software
• Installation, licensing, and activation
•
•
•
•
Overview
• 64‐bit Cube
• Compatibility updates
• Network size increase CUBE
• New Cube 6.4 installer
• New licensing system
• Welcome window
VOYAGER
3
64-Bit Cube
• Eliminates memory limitations and uses more physical or virtual memory on a given machine (therefore solving RAM allocation error with ‘BIG’ data).
• Data can be processed in larger chunks with more accuracy.
• Uses double precision numbering, eliminating need for rounding.
Compatibility Updates
• Cube is now compatible with ESRI ArcGIS 9.3 to 10.3
• Also compatible with Windows 8/Server 2012
10.3
10 Million Links and Nodes
• Cube 6.4 handles ‘BIG’ networks – up to 10 MILLION links and nodes.
New Cube 6.4 Installer
• License no longer required prior to installing
• One standard installer for ArcGIS or non ArcGIS engine
• Faster install/uninstall run times
• Easier to localize (e.g., language – no separate installer needed)
7
New Licensing System
• No dongles any more
• Use License Manager to activate and administer your Citilabs license (runs in background)
8
Welcome Window
9
Cube Base
•
•
•
•
•
Network/GIS Window
Data Manager
Text Editor
IF Statement
CUBE VOYAGER
DBF Table Editor
10
Network/GIS Window
Cube Base
• Reverse scrolling behavior: control zooming behavior with mouse scrolling tool.
• Decimal Places for Numeric Display: global setting for number of decimal places displayed by link & node attributes in Network and GIS windows.
Data Manager
• Updated user interface
• Improved response time of Data Manager when handling large databases
• Faster response in using ‘Build Network from Shape/ Features Class’ tool when working with large shape files
• Improved SDE database functions
12
DBF Table Editor – Beta
• To Activate new DBF table Editor, go to File > Options and uncheck ‘Use the default DBF editor’. Then close Cube and start Cube again.
DBF Table Editor – Beta (cont’d)
• Now users can view/edit DBF files in an EXCEL like environment.
o Multiple‐row selection and operation
o Convenient data view, editing and manipulation options
Text Editor
• New code folding mechanism for:
o RUN…ENDRUN
o PROCESS..ENDPROCESS
o JLOOP…ENDLOOP
o LINKLOOP…ENDLOOP
o LOOP…ENDLOOP
o Multiline‐comments
• Added option to customize text editor colors
15
IF Statement
IF (condition) THEN
…..
ELSEIF (condition) THEN
……
ELSE
……
ENDIF
IF (condition)
……
ELSEIF (condition)
…..
ELSE
…..
ENDIF
16
Cube Voyager Programs
•
•
•
•
•
PILOT
MATRIX
NETWORK
HIGHWAY
CUBE
PT
VOYAGER
17
PILOT
• New functions for retrieving and formatting system time:
o CurrentTime
o FormatDateTime
o Format
18
MATRIX
• CheckName, GetMatrixRow: checks for matrix table names and retrieve row values
• FILLMW: handles batch matrix transpose operations
19
NETWORK
• CheckName, GetValue：checks for link attribute names and retrieve values
• New CSV formats for LINKO and NODEO outputs
• Additional sub keyword under GEOMI*:
– AFIELD: specify the A field
– BFIELD: specify the B field
– SEQFIELD: specify the sequence field
*The GEOMI keyword can be used to input Shape and Geodatabase geometry sources. GEOMI has three advantages over using LINKI as geometry source:
1. eliminates need to read & merge GDB network into final network if needed as geometry source only. 20
2. allows using shape files as geometry source as LINKI does not allow shape files as input. 3. will not merge data fields or data records into base network because it is not LINKI. NETWORK (Cont’d)
• New set of keywords to access adjoining link attributes:
Both NODEMERGE/LINKMERGE
_N.MaxConnect
Maximum number of connections for the whole network
NODEMERGE
_N.Connections
_N.Legs
_N.Inbounds
_N.Outbounds
_NI.{name}[#]
_NO.{name}[#]
_NI._Angle[#]
_NO._Angle[#]
Number of Connecting nodes to N
Number of Legs at N
Number of inbound links to N
Number of outbound links to N
Inbound link attributes, {name} is the attribute name, [#] is leg number
Outbound link attributes, {name} is the attribute name, [#] is leg number
Inbound link angles in degrees, # is the leg number
Outbound link angles in degrees, # is the leg number
21
NETWORK (Cont’d)
• New set of keywords to access adjoining link attributes (cont’d):
LINKMERGE
_A.Connections/_B.Connections
_A.Legs/_B.Legs
_A.Inbounds/_B.Inbounds
_A.Outbounds/_B.Outbounds
_A.CurrentLeg/_B.CurrentLeg
_AI.{name}[#]/_BI.{name}[#]
_AO.{name}[#]/_BO.{name}[#]
_L.Angle
_AI._Angle[#]/_BI._Angle[#]
_AO._Angle[#]/_BO._Angle[#]
Number of connecting nodes to A/B
Number of Legs at A/B
Number of inbound links to A/B
Number of outbound links to A/B
The leg number of the current link
Inbound link attributes, {name} is name of attribute name, # is the leg number
Outbound link attributes, {name} is name of attribute name, # is the leg number
Link angle for current link in degrees, 0 is north and counter‐clockwise
Inbound link angles in degrees, # is the leg number
Outbound link angles in degrees, # is the leg number
22
NETWORK (Cont’d)
• New set of keywords to access adjoining link attributes (cont’d) – example:
23
HIGHWAY
• Intersection Uturns
Modeling: CirculatingLanes
ByPassType
includes CenterLanePercent
HCM2010 CriticalGap
FollowUpTime
methodologies HeavyVehicles
for all‐way stop, two‐way SixLaneMajor
CriticalGap
stop and FollowUpTime
roundabouts.
Roundabouts
Number of U‐Turns per approach, 0
Number of Circulating lanes per approach, 1
ByPass lane type per approach
0 ‐ none, 1‐yielding, 2‐nonyielding
Utilization percentage per approach, 47% or 53%
Critical Gap per approach, 3.0 to 6.0
Follow up time per approach, 2.0 to 5.0
All‐Way Stop
Number of heavy vehicles per approach
Two‐Way Stop
To specify the major roadway has six lanes
3 values per movement ‐ single stage/stage1/stage2
default added for six lane major roadways
24
HIGHWAY (Cont’d)
• CheckName, GetValue: checks for link attribute names to retrieve values.
• AllowLambda0: helps eliminate oscillation of solutions and terminates iterative procedures sooner (by allowing Lambda to go to zero if low value of increment is zero)
25
HIGHWAY (Cont’d)
• MaxPathCost: restricts maximum path cost in path building
• FromNode: formats and reports paths from a single origin to a range of destinations.
Output File:
26
HIGHWAY (Cont’d)
• TRACESUMMARY: controls path trace printing to print files
TRACESUMMARY=T
TRACESUMMARY=F
27
HIGHWAY (Cont’d)
•
TREEO: outputs path tree information
How to get a path from zone 4 to zone 1?
4 ‐> 18 ‐> 15 ‐> 1
28
PUBLIC TRANSPORT
• PT can handle large networks.
• Updated PT time tabling process.
• Modified PT fare calculation to include 64‐bit higher precision variables.
• Updated stop to stop analysis：
• DEC: controls decimal precision of passenger volume outputs
• ACCUMULATE=ADJACENT: allows mode information for each movement in output file
• New LINKO file formats (CSV and TXT)
29
Other Cube Programs
• AVENUE
• ANALYST DRIVE
CUBE VOYAGER
30
AVENUE
• AVENUE has been upgraded to 64‐bit compatible code and is capable of handling large networks and trip matrices.
• Updated packet allocation methodology (PACKETS=PA).
• Modified average queue time across the entire number of packets during a time segment.
31
AVENUE (Cont’d)
• Added new key words to control packet generation and path building:
– DEMANDDISTRIB: controls vehicle departure distribution (random/uniform)
– BUILDALLPATHS: controls if all possible paths are built between all OD pairs under DYNAMICLOAD (T/F)
– GENPKTBYITER: controls if generate new packets each iteration and discard previously‐generated packets at the start of every iteration (T/F)
• Added new link output attribute ‐ AVGQDELAY
32
ANALYST DRIVE
• Performance enhancement with reduced run time
• Improved functionality to perform dynamic trip estimation capabilities using Bluetooth and other detector/survey data.
• Supports PT OD estimation.
• Updated integer precision to 8 bytes for dealing with large ICP files.
33
Cube 6.4 vs. Legacy Versions
CUBE 6.4
VS.
LEGACY VERSIONS
34
Cube 6.4 vs. Legacy Versions
Legacy Cube Versions
Cube 6.4
RAM
2GB (32‐bit OS)/4GB (64‐bit OS)
All available physical RAM
Network Size
999,999 links & nodes
10million links & nodes
ArcGIS Compatibility 9.3‐10.2.2 (depends on the Cube version)
9.3‐10.3
Licensing System
Allow dongle license
Uses License Key
Installer
•
•
•
•
•
Two separate installers (with/without
ArcGIS Engine)
Requires license installation first
Issues with ArcGIS dependency
A separate language package
Longer run times for installation/uninstallation
•
•
•
•
•
One standardized installer
License no longer required prior to installation
No fussing with MSI ArcGIS dependency issues
Language package is included in the installer
Faster install/uninstall times
35
Cube 6.4 vs. Legacy Versions
(Cont’d)
• Since Cube 6.4 programs have been re‐written in 64‐
bit computing architecture code, internal variables now have higher precision. This will affect some calculations, especially in HIGHWAY and PT programs:
– PT: route enumeration (skimming) and evaluation might be different when compared to previous Cube versions.
– HIGHWAY：due to improved precision of PATH variables, path building results might be different compared to previous Cube versions.
– Intersection Modeling: delay calculation methodology updated.
36
– AVENUE: packet allocation methodology updated.
Installation, Licensing, and Activation
CUBE 6.4 INSTALLATION
AND LICENSE ACTIVATION
37
Installation Prerequisites
• Public agencies – obtain via FDOT/Central Office
• Other users:
– Request a License Key
– Download the installer
http://citilabs.com/software/releases/cube64/
Request for a License Key 38
Download the Installer
Installation Process
• Multi‐language is available during the installation process.
• Cube 6.4 is available in English, Chinese, German and Italian.
39
Floating License
• Floating License
– Single seat
– Multiple seats
• License key must be activated on a physical machine.
• License key is tied to machines
40
Activate License Key
•
•
•
•
Open License Manager
Go to Menu > Activate a License Key
Enter your License Key
Click OK
1
2
41
Manual Activation
• Open License Manager
• Go to Menu > Manual Activation
• Contact [email protected] and provide the HOSTID.
• Citilabs® will send you an activated license file
(*.lic)。
• Open Manual Activation again and click Browse to locate the *.lic file.
1
2
42
3
Connecting to License Server
•
•
•
•
Open License Manager
Go to Menu > Connect to a License Server
Enter your server name
1
Click OK
2
43
License Manager – Main Window
44
Q&A
• For software and/or license inquiries please contact:
– Licensing Department > [email protected]
– Technical Support Team > [email protected]