Changes between Version 28 and Version 29 of DSC/zdc_framework
- Timestamp:
- Aug 13, 2013, 2:05:57 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DSC/zdc_framework
v28 v29 14 14 3. ''team-image.ndz'': disk image that contains the team's radio. Please note that it is this image file that will be validated, and that once the image has been loaded for validation, no modification to the radio designs within the image prior to completion of the validation process are allowed. 15 15 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. 16 5. The OEDL experiment script to execute the matches .16 5. The OEDL experiment script to execute the matches and perform image validation. 17 17 18 18 Teams must ensure that their images contain '''/root/dsc-code_tx''' and '''/root/dsc-code_rx'''. Only these names will be used for testing and scoring. Further, these executables/scripts must be able to receive as input three parameters: … … 100 100 }}} 101 101 102 In the case of Wildcardmatches these two nodes will receive the competitor's image (and hence replace the house bot image name with the team's image name).102 In the case of the validation matches these two nodes will receive the competitor's image (and hence replace the house bot image name with the team's image name). 103 103 104 104 * Image the two nodes to be used for the second team's radios (in this case team C nodes): … … 123 123 }}} 124 124 125 == Running the Experiment Script ==125 == Running the Validation/Experiment Script == 126 126 127 127 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.