Changes between Version 4 and Version 5 of TrafficModelATMSOverview


Ignore:
Timestamp:
01/05/2018 09:15:34 PM (8 years ago)
Author:
jtorres
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TrafficModelATMSOverview

    v4 v5  
    3535=== How do these components work together? === 
    3636 
    37 When the CAD Server starts, the Traffic Model Manager and the Highways model are instantiated. The Traffic Model Manager creates a thread, the WriteToFEPThread, which creates a client socket connection with the FEP Simulator. The traffic conditions message is sent over this socket, to the FEP Simulator, on every 30 second interval. To do so, the WriteToFEPThread calls upon the Highways class' writeToFEP() method. 
     37When the CAD Server starts, the Traffic Model Manager and the Highways model are instantiated. The Traffic Model Manager spawns a thread, the WriteToFEPThread, which creates a client socket connection with the FEP Simulator. The traffic conditions message is sent over this socket, to the FEP Simulator, on every 30 second interval. To do so, the WriteToFEPThread calls upon the Highways class' writeToFEP() method. 
    3838 
    3939The FEP Simulator acts as a socket server, and awaits the traffic conditions message from the CAD Server's Traffic Model Manager. Upon receipt of this message, the FEP Simulator parses and reconfigures the data into fep_reply structs. 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. 
    … …  
    7171=== ATMS === 
    7272 
    73 The ATMS is a completed, preexisting, production server from CalTrans. We do not know much about it, other than its ability to recieve fep_reply structs via RPC and feed the received data to the ATMS Client interactive map GUI. 
     73The ATMS is a completed, pre-existing, 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. 
    7474 
    7575== Protocols == 
    7676 
    77 === Traffic Model to FEPSimulator === 
     77=== Traffic Model to FEP Simulator === 
     78 
     79The Traffic Model communicates with the FEP Simulator by sending the traffic conditions message over a socket connection. 
     80 
     81==== Traffic Conditions Message Format ==== 
     82 
     83TODO: document traffic conditions message 
     84 
     85=== FEP Simulator to ATMS === 
     86 
     87The FEP Simulator communicates with the ATMS via RPC. It sends fep_reply structs which contain traffic condition data. 
     88 
     89==== fep_reply struct ==== 
     90 
     91TODO: document fep_reply struct 
     92