Competitor Final Results Certification Period

Dec. 2^nd: Competitors will individually receive their scores from the GO Competition administrator. Results will not be posted on the website at this time. Competitors may self-test their final event codebase on their own systems to confirm that they were well-evaluated on the GO platform. Competitors may request time to self-test a limited set of datasets on the GO Competition platform with ARPA-E approval.

Note: We do not expect that every competitor will be able to re-run every scenario on the platform in two weeks; competitors should use logs or error files to prioritize any scenarios that appear to have issues and could potentially require re-testing.

Dec. 13^th: If a competitor finds that any of their scores were adversely affected by an issue unrelated to their approach/codebase, that competitor may submit up to five scenarios for the GO Competition Administrator to re-evaluate on the GO Competition platform. Competitors should include a description of the perceived issue to receive this official re-evaluation of up to five of their scenarios from the final event. Competitors may refer to their error logs or any other helpful information while describing the issue.

Valid issues may include:

1. Platform, configuration, or hardware settings that are inconsistent with the specifications provided on the competition website
2. Clerical or numerical issues with the evaluation of the results, or in the presentation of the results to the competitor
3. Evidence of a temporary or passing hardware issue that could have led to lower performance or a failure of a particular scenario

We will not consider justifications that are similar in substance to these:

1. The codebase works better on a different or faster machine than the hardware described on the competition website
2. Any attempt to submit an altered or corrected codebase for re-evaluation. We will only use codebases provided in the original final event submission window for this re-evaluation period
3. Competitors should not request re-evaluations to only achieve marginal improvements on their results

Dec. 13^th – Jan. 6^th: If a competitor raises an issue that is found to be a valid point of widespread concern, ARPA-E will work with that competitor directly to remediate any other affected scenarios, including scenarios outside of the original five submitted for review.

February 12, 2020: Final scores posted for all teams on the GO Competition website. For purposes of awarding prizes, these team scores and rankings are final.