| 79 | | == Image Verification and Submission == |
| 80 | | |
| 81 | | |
| | 79 | == Image Validation and Submission == |
| | 80 | |
| | 81 | For the image to be considered for the tournament it must be successfully validated in both the Competitive and Cooperative modes. 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 with what was 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 type of matches) will be used. |
| | 82 | |
| | 83 | 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. |
