Changes between Version 1 and Version 2 of DSC/Hurdle3
- Timestamp:
- Mar 18, 2013, 7:30:12 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DSC/Hurdle3
v1 v2 5 5 In this hurdle, teams will build a radio pair (transmitter and receiver) that can perform well in the presence of interference. The teams will be provided a baseline transmitter and receiver implementation. The transmitter will take input data from a specified source, packetize it and transmit it using a simple modulation scheme. The receiver module will take the received data and pipe it to a database file. Using these transmitter and receiver modules as starting points, the teams must write their own transmitter and receiver modules that can withstand a set of simple interference types and successfully deliver as many packets to the database over the course of 5 minutes. 6 6 7 By the end of the Qualification Period, teams must submit a final version of their radio pair for evaluation on ORBIT. In order to do this, teams must specify (in an email to challenge @orbit-lab.org) the name of a saved image they wish to be tested. In the event that a team does not inform the Challenge of their saved image within 24 hours of the Qualification Period ending, then they will be evaluated using the originally provided baseline. The evaluation of each team's design will be performed after 24 hours following the completion of the Qualification Period.7 By the end of the Qualification Period, teams must submit a final version of their radio pair for evaluation on ORBIT. In order to do this, teams must specify (in an email to challenge at orbit-lab dot org) the name of a saved image they wish to be tested. In the event that a team does not inform the Challenge of their saved image within 24 hours of the Qualification Period ending, then they will be evaluated using the originally provided baseline. The evaluation of each team's design will be performed after 24 hours following the completion of the Qualification Period. 8 8 9 9 Radio Operation: During development of their radio modules, teams will be rotated through the various USRP-enabled domains. Beyond ensuring fair exposure to ORBIT USRP resources, this allows teams to design/test their transmitter-receiver algorithms to work on as many different radios as possible. As in Hurdle 2, each domain has a specified 2.5MHz spectrum band that it is allowed to operate in. The ORBIT testbed monitors the frequencies used by each domain. Failure to restrict usage to the assigned frequency band may result in termination of the time slot. … … 31 31 WINLAB has created 16 virtual domains containing USRP2s and USRP N210s. Given the large number of teams participating in the Challenge Hurdles, teams will be assigned specific times at which they may access specified virtualdomains containing USRP2 and USRP N210s. In order to ensure fairness, teams will rotate through different domains, and hence no team will have a significantly larger amount of time on a particular domain compared to other teams. At the end of each 2 hour time period, teams will be removed from their domain in order to make that domain available for the next team. Teams are advised to plan their development and work according to the schedule slots they have been assigned. No reassignment or additional time slots will be given to any team. 32 32 33 a.) Look up your team's assigned time slot for a USRP virtual domain via https://www.orbit-lab.org/schedule/33 a.) Look up your team's assigned time slot for a USRP virtual domain at [https://www.orbit-lab.org/schedule/ scheduler page] 34 34 35 35 All teams have been given their time assignments, with domain name and frequency band, in an initial email from the Challenge. Note that each domain has a corresponding frequency band that must be used with that domain. The allowed frequency band can also be found using the online schedule by running the cursor over the virtual domain's name. … … 37 37 b.) ssh into console: 38 38 Teams may access their domain at the corresponding assigned timeslot by: 39 ssh username@console.grid.orbit-lab.org 39 {{{ 40 ssh username@console.grid.orbit-lab.org 41 }}} 40 42 Note that if a team does not use its time slot, then it will not be able to obtain a replacement time slot. Time slots have been assigned so as to give each team a fair and equitable exposure to USRP resources on ORBIT. No requests for additional time slots will be approved. 41 43 … … 64 66 This will save the node image into the image repository with the unique name displayed on the screen. 65 67 66 Teams are reminded that it is prudent to give themselves enough time to save their work before the end of their time slot. After saving their final image, teams must email the Challenge at challenge @orbit-lab.org to inform the Challenge of the team's final submission. This email must contain the name of the saved image (as provided on the screen after issuing the omf save command) that the team wishes to submit for evaluation. Teams that do not inform the Challenge of their saved image within 24 hours of the Qualification Period ending will be evaluated using the originally provided baseline. Teams should also note that the names of their radio transmitter and receiver must be benchmark_tx3 and benchmark_rx3, respectively,with unmodified packet source and packet destination modules, and command line argument for center frequency specification. Evaluation will only be performed using benchmark_tx3 and benchmark_rx3 names.68 Teams are reminded that it is prudent to give themselves enough time to save their work before the end of their time slot. After saving their final image, teams must email the Challenge at challenge at orbit-lab dot org to inform the Challenge of the team's final submission. This email must contain the name of the saved image (as provided on the screen after issuing the omf save command) that the team wishes to submit for evaluation. Teams that do not inform the Challenge of their saved image within 24 hours of the Qualification Period ending will be evaluated using the originally provided baseline. Teams should also note that the names of their radio transmitter and receiver must be benchmark_tx3 and benchmark_rx3, respectively,with unmodified packet source and packet destination modules, and command line argument for center frequency specification. Evaluation will only be performed using benchmark_tx3 and benchmark_rx3 names. 67 69 68 70 The Qualification Period ends March 5 at 11:59:59PM Eastern Standard Time. … … 72 74 Teams will be ranked according to the number of error free packets they successfully transmit during a 5 minute evaluation run. The evaluation run will consist of running the interference scenario, then initiating the team's receiver, then initiating the team's transmitter. In the unlikely event that teams end up with the same number of error free packets, the shortest transfer time will be used to break ties. A selection of the top performing teams will be chosen as contestants for the DARPA Challenge. Teams not selected may still be able to participate in the DARPA Spectrum Challenge as "Wild Card Teams." Further information related to Wild Card selection will be made available following the completion of the hurdles. 73 75 74 Questions or issues related to the hurdles should be sent by email to dsc-questions @orbit-lab.org. Answers will be posted to a public forum site at [wiki:DSC/QandA Q&A page].76 Questions or issues related to the hurdles should be sent by email to dsc-questions at orbit-lab dot org. Answers will be posted to a public forum site at [wiki:DSC/QandA Q&A page]. 75 77 76 78 Teams are reminded that the Qualification Period completes on March 5, 2013 at 23:59:59pm (Eastern). Submissions for Hurdle 3 must be turned in at the end of your time slot on that day.
