Changes between Version 1 and Version 2 of DSC/Backup/zdc_framework
- Timestamp:
- Nov 12, 2013, 5:06:05 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DSC/Backup/zdc_framework
v1 v2 1 = Match Execution Framework =1 ''' Match Execution Framework''' 2 2 ''(Last Modified: Monday 8/12/2013 11:45PM)'' 3 3 4 4 [[TOC(DSC*,depth=2)]] 5 5 6 == Objective == 6 '''Objective''' 7 7 8 Use an OEDL script to execute either a competitive-style or cooperative-style game for both Preliminary matches of the DARPA Spectrum Challenge. 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 validation to the images that teams submit for the Preliminary matches: teams must use the script in this framework to validate their '''image''' before submission. Validation is required for both competitive and cooperative style matches. 8 9 9 10 The OEDL script uses three pairs 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 image validation, 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. 10 11 11 == Hardware / Software Resources Used == 12 '''Hardware / Software Resources Used''' 13 12 14 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). 13 15 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. … … 65 67 Teams are also required to label their image with the image name they intend to use for submission, which should be stored in file named '''/.orbit_image''' on the root of the filesystem before node is saved. For example, if the team intends to submit an image with image name '''orbit-bot.ndz''' the /.orbit_image file should contain '''orbit-bot'''. 66 68 67 === Packet Server === 69 '''Packet Server''' 70 68 71 The packet server application running on the infrastructure machine has 69 72 * a packet source at port 5123 which serves fixed size packets (1440 bytes). Clients can request packets from the server with the following handshaking process after a TCP socket connection has been established: … … 78 81 * 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. 79 82 80 == Image Validation and Submission == 83 ''' Image Validation and Submission ''' 81 84 82 85 For the image to be considered for the tournament it must be successfully validated in ''both'' the Competitive and Cooperative modes. Different images for different tournament modes will not be accepted. Successful execution of the system:exp:dsc-match script (i.e. with at least one error-free packet received by the scoring server) is considered validation of the image for that match type. Please note that the email sent by the scoring server to contestants (as well as the ORBIT team) contains all the information about images that were used for the match. '''It is essential that teams validate their final image without any modifications'''. The best way to ensure that is to simply save the final image, re-image the nodes and execute the scripts (without any further login/access to the nodes). This guarantees that the image checksum will be the same as what gets reported in the validation email. You may run the validation script as often as desired and on multiple images. If the team successfully validates multiple images, the ORBIT team needs to be informed of the actual image to be used, otherwise the last successfully validated image (i.e. passing both types of matches) will be used. … … 84 87 Each team is also advised that the file /.orbit_image should contain the final image name (or team name) in order to facilitate proper reporting by the framework. 85 88 86 == Setting Up the Arena == 89 ''' Setting Up the Arena ''' 87 90 * To get started, first make a reservation on the [https://www.orbit-lab.org/loginService/ControlPanel Orbit Scheduler] for using the Grid. 88 91 * After logging into grid console, make sure all nodes are turned off (in the example below, turn off all the nodes in the grid): … … 123 126 }}} 124 127 125 == Running the Validation/Experiment Script == 128 ''' Running the Validation/Experiment Script ''' 126 129 127 130 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.
