Changes between Version 2 and Version 3 of DSC/dc_trial2
- Timestamp:
- Jun 25, 2013, 2:32:29 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DSC/dc_trial2
v2 v3 9 9 1. Four grid nodes with USRP N210s. 10 10 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. 11 3. ''team-image.ndz'': disk image that contains the team's radio. 11 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. 12 12 4. Scoring packet server: This is server that resides on the grid console (for the practice) and is used by a transmitting nodes to send data packets over the air via USRP as well as by the receiving nodes to submit received packets for scoring. 13 13 5. [attachment:dsc-wildcard.rb]: this is the OEDL experiment script to execute the game. … … 26 26 }}} 27 27 28 * Image the two nodes to be used for the first team's radios (in this case the first team is team A, and corresponds to the participant team):28 * Image the two nodes to be used for the first team's radios. The example dsc-bot.ndz image contains four different topology configurations, dsc-teamA.rb, dsc-teamB.rb, dsc-teamC.rb, and dsc-teamD.rb. The configurations should be considered to be fixed for purpose of the games, and teams simply choose which topology slot (A, B, C, or D) to place their image. In the case described in this example, the first team is being placed in the team A topology slot. Also, in the example described, we are using a house bot for the participant team 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 filename: 29 29 {{{ 30 30 username@console.grid:~$ omf load -i dsc-bot.ndz -t system:topo:dsc-teamA … … 49 49 == Running the experiment script == 50 50 51 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 . 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.51 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. 52 52 53 53 … … 72 72 Please note that actual Wildcard and Tournament games will be longer than 100 seconds. 73 73 74 A lso notethat this example uses dsc-bot.ndz for both teams, and that team A needs to replace this field in the omf load command with team-image.ndz.74 As noted earlier, that this example uses dsc-bot.ndz for both teams, and that team A needs to replace this field in the omf load command with team-image.ndz.