Changes between Version 13 and Version 14 of DSC/zdc_framework


Ignore:
Timestamp:
Jul 17, 2013, 9:43:15 PM (11 years ago)
Author:
seskar
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • DSC/zdc_framework

    v13 v14  
    6565Teams are also required to label their image with the image name they intend to use for submission, which should be stored in file named '''/.orbit_image''' on the root of the filesystem. For example, if the team intends to submit an image with image name '''orbit-bot.ndz''' the /.orbit_image directory should contain '''orbit-bot'''.
    6666
     67=== Packet Server ===
     68The packet server application running on the infrastructure machine has
     69* a packet source at port 5123 which serves fixed (1440 bytes). Clients can request packets from server with the following handshaking process after a TCP socket connection has been established:
     70    1. client sends server the request with packet size as 4 byte word ('''ignored''' for the matches).
     71    2. server sends client a single data packet (fixed at '''1440''' bytes)
     72
     73    The packet source sends out the first packet to each team only after it receives packet requests from all the teams (2 teams for competitive match and 3 for co-operative) and the start signal from the experiment script. It closes transmit socket on the first packet request after the end-of-file is reached or at the 180 second timeout. It will report the score via an email to whoever has a grid reservation (if at least one packet is received correctly).
     74 * a packet sink at port 5125 which receive packets from client and verifies that it matches one of the sent packets. Clients can send data to server after a connection has been established:
     75    1. server sends client a ready packet (4 byte word).
     76    2. client sends server data for scoring.
     77   
     78* a control interface used by the experiment script to prepare the packet server for a match by setting its mode, duration etc., and to send a start signal so the packet source can send packets to the teams.
     79
    6780== Setting up the arena ==
    6881 * To get started, first make a reservation on the [https://www.orbit-lab.org/loginService/ControlPanel Orbit Scheduler] for using the Grid.
    … …  
    107120
    108121The experiment script will execute '''/root/dsc-code_tx''' and '''/root/dsc-code_rx''' on the source and sink respectively (please note that there are no suffixes), for both (all three) pairs of nodes. Teams must ensure that their images contain '''/root/dsc-code_tx''' and '''/root/dsc-code_rx'''. No modifications to this execution format is allowed. The sender module draws packets from a packet server, while the sink module delivers packets to the same packet server. 
    109 
    110 === Packet Server ===
    111 
    112  * idb2
    113  * Ports
    114 
    115 1440 bytes fixed-size packets; closes transmit socket on the first packet request after the end-of-file is reached or at the 180 second timeout. It will report the score via an email to whoever has a grid reservation (if at least one packet is received correctly).
    116122
    117123 * Type to following command to run the experiment. This will start the packet server, start the source and sink for all teams and release the packet source, wait for 180 seconds and then terminate the match. The actual transmission/reception will run.