Changes between Version 21 and Version 22 of DSC/zdc_framework

Timestamp:

Aug 13, 2013, 1:46:46 AM (11 years ago)

Author:

seskar

Comment:

—

DSC/zdc_framework

@@ -6 +6 @@
 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.  Certification is required for both competitive and cooperative style matches. 
 
-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}'''). 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. 
+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}'''). 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 and for image certification, 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. 
 
 == Hardware / Software Resources Used ==
@@ -13 +13 @@
  3. ''team-image.ndz'': disk image that contains the team's radio. 
  4. Scoring packet server: This is the server that resides on the infrastructure machine and is used as the source of data packets as well as the sink for teams to submit received packets for scoring.
- 5. [attachment:dsc-wildcard.rb]: this is the OEDL experiment script to execute the matches.
+ 5. The OEDL experiment script to execute the matches.
 
 Teams must ensure that their images contain '''/root/dsc-code_tx''' and '''/root/dsc-code_rx'''. Only these names will be used for testing and scoring. Further, these executables/scripts must be able to receive as input three parameters: 
@@ -77 +77 @@
 * 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.
 
-== Setting up the arena ==
+== Image Verification and Submission ==
+
+
+
+== Setting Up the Arena ==
  * To get started, first make a reservation on the [https://www.orbit-lab.org/loginService/ControlPanel Orbit Scheduler] for using the Grid. 
  * After logging into grid console, make sure all nodes are turned off (in the example below, turn off all the nodes in the grid):
@@ -116 +120 @@
 }}}
 
- * Download the [attachment:dsc-challenge.rb OEDL experiment script] to your local directory.
-{{{
-username@console.grid:~$ wget http://www.orbit-lab.org/raw-attachment/wiki/DSC/zdc_framework/dsc-challenge.rb
-}}} 
-
-== Running the experiment script ==
+== Running the Experiment Script ==
 
 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.  
 
-Use the [attachment:dsc-challenge.rb attached OEDL script] to run the match. The script will start the packet server, start the transmitter and receiver for all teams and release the packet source, wait for 180 seconds and then terminate the match.
+Use the '''system:exp:dsc-match''' OEDL script to run the match. The script will start the packet server, start the transmitter and receiver for all teams and release the packet source, wait for 180 seconds and then terminate the match.
 [[BR]] [[BR]]
 For competitive matches, the command line is:
 {{{
-username@console.grid:~$ omf exec dsc-challenge.rb -- --mode COMP
+username@console.grid:~$ omf exec system:exp:dsc-match -- --mode COMP
 }}}
 
@@ -135 +134 @@
  * The output of the competitive match should look similar to the following:
 {{{
-username@console.grid:~# omf exec dsc-challenge.rb -- --mode COMP
+username@console.grid:~# omf exec system:exp:dsc-match -- --mode COMP
 
  INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228)
@@ -183 +182 @@
 For cooperative matches, the command line is:
 {{{
-username@console.grid:~$ omf exec dsc-challenge.rb -- --mode COOP
+username@console.grid:~$ omf exec system:exp:dsc-match -- --mode COOP
 }}}
 
@@ -189 +188 @@
  * The output of the cooperative match should look similar to the following:
 {{{
-username@console.grid:~# omf exec dsc-challenge.rb -- --mode COOP
+username@console.grid:~# omf exec system:exp:dsc-match -- --mode COOP
 
  INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228)
@@ -280 +279 @@
 }}}
 
+== Running Matches on Sandboxes ==
+
+In order to facilitate code development, all three sanboxes (sb2,sb3 and sb7) are haveg simplified version of the OEDL script and packet server. Please do note that, since they have only one pair of nodes, these environments are really not capable of generating interference, but are rather meant for code testing. Appropriately, the actual match script is named dsc-test and the sequence of commands to execute it is somewhat simplified and consist of:
+ 
+  * Loading the image:
+{{{
+  omf load -i team-image-name.ndz
+}}}
+  * Turning the nodes on:
+{{{
+  omf tell -a on
+}}}
+  * Executing the "match"":
+{{{
+  omf exec system:exp:dsc-test -- --mode COMP
+}}}
+  or
+{{{
+  omf exec system:exp:dsc-test -- --mode COOP
+}}}
+  * The output of the 30 second matches should look similar to the following:  
+[[CollapsibleStart(Competitive match output on the sanbox)]] 
+{{{
+console.sb2:~# omf exec system:exp:dsc-test -- --mode COMP --runtime 30
+
+ INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228)
+ INFO NodeHandler: Slice ID: default_slice (default)
+ INFO NodeHandler: Experiment ID: default_slice-2013-08-12t20.55.32.533-04.00
+ INFO NodeHandler: Message authentication is disabled
+ INFO Experiment: load system:exp:stdlib
+ INFO property.resetDelay: resetDelay = 230 (Fixnum)
+ INFO property.resetTries: resetTries = 1 (Fixnum)
+ INFO Experiment: load system:exp:eventlib
+ INFO Experiment: load system:exp:winlib
+ INFO Experiment: load system:exp:dsc-test
+ INFO property.freq: freq = 650000000 (Fixnum)
+ INFO property.server: server = "10.12.0.10" (String)
+ INFO property.port: port = 5123 (Fixnum)
+ INFO property.runtime: runtime = 30 (Fixnum)
+ INFO property.mode: mode = "COMP" (String)
+ INFO exp: Connecting to packet server
+ INFO stdlib: Waiting for nodes (Up/Down/Total): 1/1/2 - (still down: node1-1.sb2.orbit-lab.org) [0 sec.]
+ INFO ALL_UP_AND_INSTALLED: Event triggered. Starting the associated tasks.
+ INFO exp: Preparing packet server
+ INFO exp: Request from Experiment Script: Wait for 2s....
+ INFO exp: Start rx and tx applications
+ INFO exp: Request from Experiment Script: Wait for 5s....
+ INFO exp: Running the experiment
+ INFO exp: Request from Experiment Script: Wait for 30s....
+ INFO exp: Getting the score
+ INFO exp: Sent 2161440 Received 2131200 in 30 ms
+ INFO exp: Stopping the applications
+ INFO exp: Request from Experiment Script: Wait for 2s....
+ INFO NodeHandler: 
+ INFO NodeHandler: Shutting down experiment, please wait...
+ INFO NodeHandler: 
+ INFO run: Experiment default_slice-2013-08-12t20.55.32.533-04.00 finished after 0:52
+}}}
+[[CollapsibleEnd]] 
+
+[[CollapsibleStart(Cooperative match output on the sandbox)]]
+{{{ 
+console.sb2:~# omf exec system:exp:dsc-test -- --mode COOP --runtime 30
+
+ INFO NodeHandler: OMF Experiment Controller 5.4 (git 5385228)
+ INFO NodeHandler: Slice ID: default_slice (default)
+ INFO NodeHandler: Experiment ID: default_slice-2013-08-12t21.00.56.411-04.00
+ INFO NodeHandler: Message authentication is disabled
+ INFO Experiment: load system:exp:stdlib
+ INFO property.resetDelay: resetDelay = 230 (Fixnum)
+ INFO property.resetTries: resetTries = 1 (Fixnum)
+ INFO Experiment: load system:exp:eventlib
+ INFO Experiment: load system:exp:winlib
+ INFO Experiment: load system:exp:dsc-test
+ INFO property.freq: freq = 650000000 (Fixnum)
+ INFO property.server: server = "10.12.0.10" (String)
+ INFO property.port: port = 5123 (Fixnum)
+ INFO property.runtime: runtime = 30 (Fixnum)
+ INFO property.mode: mode = "COOP" (String)
+ INFO exp: Connecting to packet server
+ INFO ALL_UP_AND_INSTALLED: Event triggered. Starting the associated tasks.
+ INFO exp: Preparing packet server
+ INFO exp: Request from Experiment Script: Wait for 2s....
+ INFO exp: Start rx and tx applications
+ INFO exp: Request from Experiment Script: Wait for 5s....
+ INFO exp: Running the experiment
+ INFO exp: Request from Experiment Script: Wait for 30s....
+ INFO exp: Getting the score
+ INFO exp: Sent 2161440 Received 1990080 in 30 ms
+ INFO exp: Stopping the applications
+ INFO exp: Request from Experiment Script: Wait for 2s....
+ INFO NodeHandler: 
+ INFO NodeHandler: Shutting down experiment, please wait...
+ INFO NodeHandler: 
+ INFO run: Experiment default_slice-2013-08-12t21.00.56.411-04.00 finished after 0:52
+}}}
+[[CollapsibleEnd]] 
+
+Please note that the sandboxes use different frequencies in order to minimize the interference, are not going to produce the scoring email (the score is printed on the screen only) and that your code must support the scoring server hostname option (since the scoring server is running on respective consoles of each of the sandboxes).  
+
 NOTES: