Submissions
For each FlightId, provide the recommended route for the remainder of the flight.
The submission format is as follows:
FlightId,Ordinal,Latitude,Longitude,Altitude,Airspeed
287383197,1,39.9,-81.08,41000,514.0
287383197,2,39.9,-80.90,40100,447.8
287383197,3,39.9,-80.72,39100,447.7
...
Model Submission
When you submit an Entry, you also will be able to upload your model to the Website. Your final model must contain all code and parameter settings necessary to evaluate your models on new data, and include a README file with instructions on how to do so. The purpose of this is to ensure this Competition is fair and no answers were looked up for the Final Evaluation Set period. This model submission is required to be eligible to win a prize. This final model will be used solely for the purpose of verifying eligibility for prizes. You may upload either the archive itself or a SHA-256 hash of the archive.
Kaggle will check the final submissions from the Entrants at the top of the Final Evaluation Leaderboard to make sure that Entrant’s final submission was created using that Entrant’s final model submission. If a potential winner did not use the final model codebase to create the final submission Entry, that potential winner will be disqualified and Kaggle will evaluate the final submission of the next Entrant on the Leaderboard as a potential winner.
For an entry to be eligible to win, any open source or third party code or other materials used in connection with that Entry must be limited to code that GE will be entitled to commercially use and exploit, and any open-source-related or third party licensor requirements and restrictions must be disclosed as part of the model submission.
Please do not upload Kaggle-provided data files, but mention which ones are used and how to link them to your agent in the readme.
Regarding non-Kaggle data (Previous leaderboard GRIB files):
Zip this data and paste its hash into a text file called 'Data Hash.txt'. Place this text file into your model archive. If your model is in-the-money, we'll contact you to retrieve the non-Kaggle data and validate the hash.