Changes between Version 12 and Version 13 of TrafficModelATMSOverview
- Timestamp:
- 01/09/2018 05:52:41 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TrafficModelATMSOverview
v12 v13 111 111 The FEP Simulator runs persistently on the Linux Virtual Machine on the TMC network.The FEP Simulator acts as a socket server, and awaits the traffic conditions message from the CAD Server's Traffic Model Manager. 112 112 113 Upon receipt of this message, the FEP Simulator parses and reconfigures the data into fep_reply structs. To do so, it uses the Highways Parser class to parse the message from the Traffic Model into FEP_LINES and STATIONS. Once parsed, it configures the data into fep_reply structs. Part of this configuration is packing data into the Traffic Conditions Message. This message is "packed" or created by using the static packData() method from the DataPacker class. See the protocols section for more information. It then sends the fep_reply structs to the ATMS via RPC. Once this process is finished, the FEP Simulator awaits another traffic conditions message from the CAD Server, and the process repeats.113 Upon receipt of this message, the FEP Simulator parses and reconfigures the data into fep_reply structs. To do so, it uses the `HighwaysParser` class to parse the message from the Traffic Model into FEP_LINE and STATION structs. Once parsed, it reformats the data into fep_reply structs. fep_replys contain a Traffic Conditions Message, a char[] array that contains traffic condition data. This message is "packed" or created by using the static packData() method from the `DataPacker` class. See the Protocols section for more information. It then sends the fep_reply structs to the ATMS via RPC. Once this process is finished, the FEP Simulator awaits another traffic conditions message from the CAD Server, and the process repeats. 114 114 115 115 === ATMS === #atmsdetail … … 144 144 === FEP Simulator to ATMS === #feptoatms 145 145 146 The FEP Simulator communicates with the ATMS via RPC. It sends fep_reply structs which contain traffic condition data . Each fep_reply struct corresponds to a single FEPLine.146 The FEP Simulator communicates with the ATMS via RPC. It sends fep_reply structs which contain traffic condition data messages. Each fep_reply struct corresponds to a single FEPLine. 147 147 148 148 The FEP Simulator includes the generated rpc files: "fep.h", "fep_clnt.c", and "fep_xdr.c". These files need to be included to utilize RPC. … … 227 227 ==== Traffic Conditions Message Structure ==== #trafficmessage 228 228 229 As seen above in the fep_anser_short_msg struct, the traffic conditions message is a char array. The FEP Simulator uses the static packData(STATION*) method from the `DataPacker` class to pack the traffic condition data into a message.229 As seen above in the fep_anser_short_msg struct, the traffic conditions message is a char[] array. The FEP Simulator uses the static packData(STATION*) method from the `DataPacker` class to pack the traffic condition data into a message. 230 230 231 231 The message contains static data, such as station drop numbers, and dynamic data, like volume and occupancy.
