Changes between Version 13 and Version 14 of TrafficModelATMSOverview
- Timestamp:
- 01/12/2018 03:24:34 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TrafficModelATMSOverview
v13 v14 37 37 == Purpose == #purpose 38 38 39 An important function of the TMC simulator is to simulate the traffic flow that results from a simulated traffic incident. The traffic flow is shown to the Cal Trans dispatcher as a road map with sensor locations displayed in different colors that correspond to stopped, slowed, or free flowing traffic. In the real world, data from sensors embedded in highways is transmitted in real time to a computer called the ATMS which then determines the flow of traffic along a network of highways. For the TMC Simulator there is no actual sensor data so this must be simulated with a traffic model. In previous versions of the TMC Simulator the traffic model used was a commercial product called Paramics. For a variety of technical, legal, and economic reasons the use of Paramics became infeasible and we choose to abandon it and develop our own solution. 40 39 41 This document provides an overview of the Traffic Model, the FEP Simulator, and the ATMS. Each of these components work together in the TMC Simulation System to simulate traffic conditions, and display them to trainees. This document will explain to the reader, at a high level, the system architecture and how the components work together to simulate the traffic conditions, an overview of each component, and lastly, the protocols between each component. 40 42 … … 51 53 === What is the FEP Simulator? === #fepsimoverview 52 54 53 The FEP Simulator simulates the actual FEP that is used in production systems at Cal Trans. It is a C++ program that runs on a Linux VM on the TMC network. It acts as a mediator between the Traffic Model and the ATMS. Its purpose is to receive the traffic condition data over a socket from the Traffic Model, parse and reformat this received data into fep_reply structs, and send the fep_reply structs to the ATMS via RPC.55 The FEP Simulator simulates the actual FEP that is used in production systems at Cal Trans. The actual FEP gathers the real time highway sensor data and transmits it to the ATMS. The FEP Simulator will gather simulated highway sensor data from the traffic model and transmit it to the ATMS. It acts as a mediator between the Traffic Model and the ATMS. Its purpose is to receive the traffic condition data over a socket from the Traffic Model, parse and reformat this received data into fep_reply structs, and send the fep_reply structs to the ATMS via RPC. The FEP Simulator is a C++ program that runs on a Linux VM on the TMC network. 54 56 55 57 === What is the ATMS? === #atmsoverview … … 115 117 === ATMS === #atmsdetail 116 118 117 The ATMS is a complete production server purchased from CalTrans. We do not know much about it,other than its ability to receive fep_reply structs via RPC and feed the received data to the ATMS Client interactive map GUI.119 The ATMS is a complete production server purchased from CalTrans. We were unable to find detailed documentation about ATMS features other than its ability to receive fep_reply structs via RPC and feed the received data to the ATMS Client interactive map GUI. 118 120 119 121 == Protocols == #protocols … … 247 249 || Last Byte || VARIES || check sum value || 248 250 249 1/8 7:27AM: NOTE TO SELF. DO I NEED TO CALL DYNAMIC DATAPACK BEFORE STATIC DATA PACK??????? 251
