Changes between Version 5 and Version 6 of DSC/zdc_framework

Timestamp:

Jul 17, 2013, 5:42:38 PM (11 years ago)

Author:

trappe

Comment:

—

DSC/zdc_framework

@@ -4 +4 @@
 
 == Objective ==
-Use an OEDL script to execute a competitive-style and cooperative-style games for both Wildcard and Preliminary matches. Even though the use of framework is illustrated by using 2 (3) house bots, it the actual competition, the teams will be using their own radio implementations. Teams have to use the script in this framework to certify their image before submission.  
+Use an OEDL script to execute either a competitive-style or cooperative-style game for both Wildcard and Preliminary matches. Even though the use of the framework is illustrated by using 2 house bots (or 3 in the case of a cooperative game), in the actual competition, the teams will use their own radio implementations. An additional purpose of the framework is to provide certification to the images that teams submit for the Wildcard and Preliminary matches: teams must use the script in this framework to certify their image before submission.   
 
-The OEDL script uses three pair of nodes: dsc-teamA, dsc-teamB, dsc-teamC (the actual topology descriptions are '''system:topo:dsc-team{A,B,C,D}'''). The competitve matches will use teamA and temaC nodes, while cooperative will use teamA, teamB and teamC nodes (contestant radios will be only on teamA nodes for the wildcard tournament while house bots will be using teamB and teamC nodes); configurations should be considered to be fixed and will be changed only in the case of hardware failures.
+The OEDL script uses three pair of nodes: dsc-teamA, dsc-teamB, dsc-teamC (the actual topology descriptions are '''system:topo:dsc-team{A,B,C,D}'''). The competitive matches will use teamA and teamC nodes, while cooperative matches will use teamA, teamB and teamC nodes (contestant radios will be only on teamA nodes for the Wildcard tournament, while house bots will be using teamB and teamC nodes); configurations should be considered to be fixed and will be changed only in the case of hardware failures. For example, the use of dsc-teamD nodes is reserved in case a backup pair of nodes is needed.
 
 == Hardware / Software Resources Used ==
- 1. Four grid nodes with USRP N210s (two for each team) for competitive match and six nodes with USRP N210s for cooperative match.
+ 1. Four grid nodes with USRP N210s (two for each team) for competitive match and six nodes with USRP N210s for cooperative match (two for each team).
  2. ''dsc-wbot1.ndz,dsc-wbot2.ndz,dsc-wbot3.ndz'': house bot disk images with the prerequisite software to configure the USRPs and execute a house radio bot. 
  3. ''team-image.ndz'': disk image that contains the team's radio. 
@@ -31 +31 @@
 }}}
 
-In the case of wildcard matches these two nodes will receive competitor image
+In the case of Wildcard matches these two nodes will receive the competitor's image (and hence replace the house bot image name with the team's image name). 
 
  * Image the two nodes to be used for the second team's radios (in this case team C nodes): 
@@ -56 +56 @@
 == Running the experiment script ==v
 
-The 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. The sender module draws packets from a packet server, while the sink module delivers packets to the same packet server.  
+The 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.  
 
 === Packet Server ==
@@ -63 +63 @@
  * Ports
 
-1440 bytes fixed packets; closes transmit socket on the first packet request after the end-of-file is reached or on the 180 second timeout. It will report the score with the email (if at least one packet is received correctly).
+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).
 
- * 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 . 
-For competitive match, the command line should is:
+ * 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. 
+For competitive matches, the command line is:
 {{{
 username@console.grid:~$ omf exec dsc-challenge.rb -- --mode COMP
 }}}
 
-For cooperative match, the command line is:
+For cooperative matches, the command line is:
 {{{
 username@console.grid:~$ omf exec dsc-challenge.rb -- --mode COOP