NEXTA Data Structure For Rail Scheduling, Version 1.0 Users Guide RAS
User Manual:
Open the PDF directly: View PDF 
.
Page Count: 11
| Download | |
| Open PDF In Browser | View PDF |
NEXTA Data Structure for Rail Scheduling, Version 1.0 Prepared for INFORMS 2012 RAS Problem Solving Competition Movement Planner Algorithm Design for Dispatching on Multi-Track Territories http://www.informs.org/Community/RAS/Problem-Solving-Competition/2012-RAS-Problem-SolvingCompetition RAS Toy Network Data Set is prepared by 2012 RAS Problem Solving Competition Organizing Committee NEXTA Document is prepared by Jeffrey Taylor (jeffrey.taylor.d@gmail.com) and Xuesong Zhou (zhou@eng.utah.edu) Last Revised: 7/26/2012 If you have any questions about the competition problem, submit your question to RASProblemSolvingCompetition@gmail.com. Please feel free to send any questions, feedback, and corrections to Jeffrey Taylor (jeffrey.taylor.d@gmail.com) or Dr. Xuesong Zhou (zhou@eng.utah.edu) by adding comments in this document and including the file as an attachment. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in www.gnu.org/licenses/fdl.html. Table of Contents NEXTA Data Structure ........................................................................................................................3 Simple Step-by-Step User Guide .........................................................................................................3 Input Files ..........................................................................................................................................4 1. Network Files ........................................................................................................................................ 4 input_rail_node.csv [Essential input data] ........................................................................................... 4 input_track_type.csv [Essential input data] ......................................................................................... 6 input_rail_arc.csv [Essential input data] ............................................................................................... 6 input_train_info.csv [Essential input data] ........................................................................................... 7 input_MOW.csv [Essential input data] ................................................................................................. 8 2. Output Files ........................................................................................................................................... 9 output_schedule.xml [Essential output data]....................................................................................... 9 NEXTA Data Structure This document describes all input files associated with NEXTA for visualizing rail scheduling output. Each input/output file includes descriptions for all variable names, followed by a short description of their type, purpose, function, interaction with other variables, and the use cases in which the variable is required/not required. Simple Step-by-Step User Guide ) Download the zipped file GUI_release_For_RAS.zip from the Google code site: http://code.google.com/p/nexta/downloads/list 2) Unzip the file to a folder on a Windows machine. 3) Go to subfolder “RAS_Toy_problem”, which has a reformatted input data set. The file output_schedule.xml follows the exactly same format as specified in the sample data set. 4) Go back to the installation folder, click NEXTA.exe 5) File->Open Rail Network Project, Open a train schedule *.xml in the subfolder RAS_Toy_problem. 6) Use mouse wheeler to zoom in and zoom out, and move network. If the network does not appear initially, click on button 7) Click on tool bar in the tool bar to display the network and train/string diagram. to show timestamps of train entries, by min and by second. 8) Train trajectories are shown in solid lines when they are running on main tracks, otherwise as dotted lines on switches and sidings. 9) Go to menu tools->Train List, select a train to highlight its corresponding path on the network and schedule on train/string diagram. 10) Go to menu tools-> Check Schedule Feasibility to check the feasibility of train schedule. Currently, only headway, nonconcurrency and MOW constraints are checked. 11) Similar to using a GIS package, you can select link layer, and click on “ mouse to select a link in order to show the corresponding attributes. ” in the tool bar and use Input Files The following tables describe the input files used in NEXTA for rail scheduling. Most tables can be defined as either essential input data (indicated by Essential input data label) or nonessential input data, while individual variables (columns) in each table may also be considered as optional variables. 1. Network Files Network input files define the basic node-link structure used in DTALite and NEXTA, along with attributes for each link and node. Additionally, nodes are related to zones and activity locations, which can be used to disaggregate trips from zones to nodes and activity locations. input_rail_node.csv [Essential input data] The input_rail_node table defines the nodes in the network in terms of names, ID numbers, location/position, and characteristics. Variable Name Name Type Optional String X node_id location_x Integer Double location_y Double TSdiagram_x Double TSdiagram_ y Double Example from RAS Toy Network: Acceptable Values/ Example Usage Value >= 0 Description Optional: Name label given to node for KML visualization, not currently used in NEXTA Node identification number describe horizontal coordinate of a node for network visualization describe vertical coordinate of a node for network visualization describe horizontal coordinate of a node for space-time diagram visualization, this coordinate can be different from describe vertical coordinate of a node for spacetime diagram visualization Why do we use TSdiagram_x, TS_diagram_y, which are different from location coordinates in some cases? Answer: NEXTA computes the time axis of a time-space diagram by offsetting the TSdiagram x/y coordinates of each node. Thus, a user needs to shift the physical location coordinates of those nodes on switches (e.g., node 3 and 4 in the figure below) so that the time axis of a space time diagram is aligned horizontally or vertically. Train trajectories are shown in solid lines when they are running on main tracks, otherwise as dotted lines on switches and sidings. input_track_type.csv [Essential input data] The input_track_type table allows users to define their own specific track types. Link types can also be used to determine how links are visualized in NEXTA. Variable Name track_type_code Type String Optional Acceptable Values Description Optional: Name label assigned to link type in the same row, used for visualization purposes in NEXTA name String 0 or 1 Identifies link type as belonging to a freeway class. Only one flag may be used in each row. Maximum speed for trains running this type of tracks max_speed float >o Example from RAS Toy Network: track_type_code Name max_speed 0 First Main Track 80 1 Second Main Track 80 2 Third Main Track 80 SW Switch 15 S Siding 20 C Crossover 15 input_rail_arc.csv [Essential input data] The input_rail_arc table defines all links in the network, along with their corresponding characteristics and traffic flow model input data. Several optional fields are included for generating/converting networks for use with microscopic simulation (e.g., VISSIM). Variable Name Name Type Optional Acceptable Values String X arc_id A_node_id Integer Integer Value > 0 Value > 0 B_node_id Integer Value > 0 Description Optional: Name label assigned to link in current row, used for visualization purposes in NEXTA and KML export Arc identification number Identification number corresponding to the node located at the beginning of the link Identification number corresponding to the node located at the end of the link Defined in Table (input_rail_ node.csv) (input_rail_ node.csv) bidirectional _flag Integer 1 = single-track 0 or 2= double track Length Double Value ≥ 0.00001 track_type String 0, 1, 2, …, S, SW, C… default_AB_ speed_per_ hour Integer Value > 0 mph, kmph default_BA_ speed_per_ hour Integer Value > 0 mph, kmph Identifies the direction of travel on the link. When 1, we allow train traverse from A_node_id to B_node_id , and from B_node to A_node The length of the link (between end nodes), measured in units of miles or KM. Track type identification code, corresponding to track type (main track, switch, etc.) Speed limit on the A-> B direction defined link in units of miles or KM per hour, used to define the free-flow speed. (input_tra ck_type.cs v) Speed limit on the B-> A direction defined link in units of miles or KM per hour, used to define the free-flow speed. Example from RAS Toy Network: input_train_info.csv [Essential input data] Variable Name Type Optional Acceptable Values train_header string entry_time Integer Value ≥ 0 origin_node_id Integer Value > 0 destination_no de_id Integer Value > 0 Description Defined in Table Train identification number Time in the schedule at which the train trip begins Departure/origin node identification number Arrival/destination node identification number (input_rail_n ode.csv) (input_rail_n ode.csv) direction string speed_multipli er double train_length x Direction which the train trip takes Value > 0 The train speed on each main track link = speed_multiplier* default_BA_speed or default_AB_speed e.g. default_BA_speed = 80 mph, a train travels through link B to A with a speed multiplier of 0.8, then the actual speed is 80*0.8 = 0.64. Double tob Integer hazmat string sa_status_at_o rigin terminal_want _time Integer Integer Value >= 0; Default: 0 For non-main tracks, such as switches, sidings, and cross-overs, the speed_muliplier. E.g. Switch’s default speed 15 mph, the actual speed is also 15 mph for all trains. In output_schedule.xml, exit time is the exit time of a train’s tail = exit time of the head of a train + train_length/actual speed on this link. If train_length is set to 0, then exit time refers to the exit time of a train’s head directly. This variable is used together with speed value in input_rail_arc.c sv This variable is used in output_sch edule.xml Not used in visualization Not used in visualization Not used in visualization Value > 0 Not used in visualization Example from RAS Toy Network: input_MOW.csv [Essential input data] Variable Name A_node_id Type Integer Optional Acceptable Values Description Value >= 0 Identification number corresponding to the node located at the beginning of the link with MOW Defined in Table (input_rail_ node.csv) B_node_id Integer Value >= 0 start_time_i n_min end_time_in _min Integer Value >= 0 Identification number corresponding to the node located at the end of the link with MOW Starting time of MOW in min Integer Value > 0 Ending time of MOW in min (input_rail_ node.csv) Example from RAS Toy Network: A_node_id B_node_id 11 12 0 20 2. Output Files output_schedule.xml [Essential output data] Variable Name Type train id string movement arc string entry exit int int Optional Acceptable Values '(%d,%d)' Description Defined in Table train_header input_train _info.csv A node and B node of a link used along the train path AB or BA direction should be defined in input_rail_ar ac.csv Entry time of a train’s head in seconds exit time of a train’s tail in seconds = exit time of a train’s head + train_length/actual speed*3660 seconds/hour Example from RAS Toy Network:
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Page Count : 11 Language : en-US Tagged PDF : Yes Title : NEXTA Data Structure for Rail Scheduling, Version 1.0 Author : Prepared by Jeffrey Taylor (jeffrey.taylor.d@gmail.com) Subject : Prepared for INFORMS 2012 RAS Problem Solving Competition Creator : Microsoft® Office Word 2007 Create Date : 2012:08:06 06:44:46-06:00 Modify Date : 2012:08:06 06:44:46-06:00 Producer : Microsoft® Office Word 2007EXIF Metadata provided by EXIF.tools