Changes between Version 6 and Version 7 of DSC/dc_trial2

Timestamp:

Jun 26, 2013, 3:47:59 PM (11 years ago)

Author:

trappe

Comment:

—

DSC/dc_trial2

@@ -6 +6 @@
 Use an OEDL script to execute a competitive-style game (similar to what will occur in the Wildcard and Preliminary matches). The example game involves a simple house bot, and the teams provide their own radio script. Teams may modify this script to use other radio bots of their own design in place of the house bot.  
 
-The example OEDL script can use four different topological configurations for team nodes: dsc-teamA, dsc-teamB, dsc-teamC, and dsc-teamD (the actual topology descriptions are '''system:topo:dsc-team{A,B,C,D}'''). The configurations should be considered to be fixed for purpose of the games, and teams simply choose which node-pair topology (A, B, C, or D) to place their image in. In the case described in this example, the first team is being placed in the '''A''' topology while the second team is placed in topology '''C'''. Also, we are using a house bot for both teams so that the example can be tested as-is. Teams should note that they should replace dsc-bot.ndz with their respective team-image.ndz.
+The example OEDL script can use four different topological configurations for team nodes: dsc-teamA, dsc-teamB, dsc-teamC, and dsc-teamD (the actual topology descriptions are '''system:topo:dsc-team{A,B,C,D}'''). The configurations should be considered to be fixed for the purpose of the games, and teams simply choose which node-pair topology (A, B, C, or D) to place their image on. In the case described in this example, the first team is being placed in the '''A''' topology while the second team is placed in topology '''C'''. Also, we are using a house bot for both teams so that the example can be tested as-is. Teams should note that they should replace dsc-bot.ndz with their respective team-image.ndz.
 
 == Hardware / Software Resources Used ==
- 1. Four grid nodes with USRP N210s.
- 2. ''dsc-bot.ndz'': disk image loaded onto one pair of nodes. This image has all the prerequisite software to configure the USRPs and execute a house radio bot. 
+ 1. Four grid nodes with USRP N210s (two for each team).
+ 2. ''dsc-bot.ndz'': house bot disk image loaded onto one pair of nodes. This image has all 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. In the explanation that follows, we use the house bot as the team's radio, effectively placing house bot against house bot.
- 4. Scoring packet server: This is server that resides on the grid console (for the practice) and is used by the transmitting nodes to send data packets over the air via USRP as well as by the receiving nodes to submit received packets for scoring.
+ 4. Scoring packet server: This is the server that resides on the grid console (for the practice) and is used by the transmitting nodes to send data packets over the air via USRP as well as by the receiving nodes to submit received packets for scoring.
  5. [attachment:dsc-wildcard.rb]: this is the OEDL experiment script to execute the game.
 
 == Setting up the nodes ==
- * To get started first make a reservation on the [https://www.orbit-lab.org/loginService/ControlPanel Orbit Scheduler] for using the Grid. 
+ * 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):
@@ -51 +51 @@
 == Running the experiment script ==
 
-By default, the experiment script will execute '''/root/gnuradio/gr-digital/examples/narrowband/bot1_tx.py''' and '''/root/gnuradio/gr-digital/examples/narrowband/bot1_rx.py''' on the transmitter and receiver respectively, for both the house bot and the team's bot. In the example described above, where house bot is competing against house bot, each team will use a separate set of parameters for a very simple bot: a brute-force radio that sends a random number of packets at random intervals. The sender module draws packets from a packet server, while the receiver module delivers packets to the same packet server.  The code is based on the same benchmark radio that was used for Hurdle 3.
+By default, the experiment script will execute '''/root/gnuradio/gr-digital/examples/narrowband/bot1_tx.py''' and '''/root/gnuradio/gr-digital/examples/narrowband/bot1_rx.py''' on the transmitter and receiver respectively, for both the house bot and the team's bot. In the example described above, where the house bot is competing against another house bot, each team will use a separate set of parameters for a very simple bot: a brute-force radio that sends a random number of packets at random intervals. The sender module draws packets from a packet server, while the receiver module delivers packets to the same packet server.  The code is based on the same benchmark radio that was used for Hurdle 3.
 
  * Type to following command to run the experiment. This will start the packet server, start the transmitter and receiver for both teams and release the packet source. The actual transmission/reception will run for 100 seconds (which can be adjusted with the property at the top of the script) or until one radio successfully transmits the file. 
@@ -149 +149 @@
 
  * Please note that actual Wildcard and Tournament games will be longer than 100 seconds. 
- * As noted earlier, this example uses dsc-bot.ndz for both teams; if the teams want to test their own designs, they need to load their image to one pair of nodes and adjust the script (if their script name/path is different from what the bot image is using).
+ * As noted earlier, this example uses dsc-bot.ndz for both teams; if the teams want onto test their own designs, they need to load their image to one pair of nodes and adjust the script (if their script name/path is different from what the bot image is using).