wiki:DSC/zdc_framework

Version 2 (modified by seskar, 11 years ago) ( diff )

—

Match Execution Framework

Table of Contents

  1. DARPA Spectrum Challenge
    1. Hurdles
    2. Wildcard tournament
    3. Preliminary round
    4. Final round
  2. DARPA Spectrum Challenge Q&A
    1. Tournament Q&A
    2. Hurdles Q&A
  3. Tutorial for Hurdle3-like experiment
    1. Objective
    2. Hardware / Software Resources Used
    3. Setting up the nodes
    4. Running the experiment script
  4. Tournament game example !#1
    1. Objective
    2. Hardware / Software Resources Used
    3. Setting up the nodes
    4. Running the experiment script
  5. Match Execution Framework
    1. Objective
    2. Hardware / Software Resources Used
    3. Setting up the arena
    4. Running the experiment script ==v
  6. Bot Images
  7. Tournament Scripts
    1. Objective
    2. Running Competitive Matches
    3. Running Cooperative Matches
  8. Match Visualization
    1. Competitive Match Visualization
    2. Cooperative Match Visualization
  9. Calibration Reports (2014-03-13)
    1. Primary Competitive
    2. Secondary Competitive
    3. Primary Cooperative
    4. Secondary Cooperative
    5. Full Arena
    6. Calibration Procedure
  10. Image Validation Procedure (Preliminary Torunament)
  11. Image Validation Procedure (Final Tournament)
    1. Validate With Basic Script
    2. Validate With Tournament Scripts
    3. Additional Arena Testing

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.

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.

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.
  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.
  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. dsc-wildcard.rb: this is the OEDL experiment script to execute the matches.

Setting up the arena

  • To get started, first make a reservation on the ​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): 
    username@console.grid:~$ omf tell -a offh -t system:topo:all
  • Verify state of node before continuing. Make sure nodes are in the POWEROFF state. 
    username@console.grid:~$ omf stat
  • Image the two nodes to be used for the first team's radios (team A nodes): 
    username@console.grid:~$ omf load -i dsc-wbot1.ndz -t system:topo:dsc-teamA

In the case of wildcard matches these two nodes will receive competitor image

  • Image the two nodes to be used for the second team's radios (in this case team C nodes): 
    username@console.grid:~$ omf load -i dsc-wbot2.ndz -t system:topo:dsc-teamC
  • FOR COOPERATIVE MATCHES: image the third pair of nodes to be used for the third team's radios (in this case team B nodes): 
    username@console.grid:~$ omf load -i dsc-wbot3.ndz -t system:topo:dsc-teamB
  • Turn nodes back on and verify they are in POWERON state 
    username@console.grid:~$ omf tell -a on -t system:topo:dsc-teamA
username@console.grid:~$ omf tell -a on -t system:topo:dsc-teamC
  • Download the 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 ==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.

Packet Server ==

  • idb2
  • 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).

  • 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 . 
    username@console.grid:~$ omf exec dsc-challenge.rb -- XXXXXXXXXXXXXXXXXXXXXX
  • The output should look similar to the following: 
    username@console.grid:~# 
username@console.grid:~#
  • Turn the nodes off 
    username@console.grid:~$ omf tell -a offh -t system:topo:all

NOTES:

Note: See TracWiki for help on using the wiki.