Debug submission clarifications and instructions #33
Pinned
fpetric
announced in
Announcements
Replies: 1 comment 2 replies
-
Hi, I wanted to confirm a few things:
Thank you |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
here are some clarifications on the debug submission.
Purpose
The goal is for you to test whether your code will work on our machines. This includes proper build of docker container, cloning, copying files, python nodes being executable, missing packages, failed imports and whatever may prevent your code from running at all. Ideally, your solution should be mostly ready.
Is it mandatory
No, but it is highly suggested you use this opportunity. We had more than a couple of teams not have their solutions evaluated due to "silly" issues.
What is the deadline for this
It was supposed to be today, but to clarify the confusion and give you some time, February 22nd, 2025, 23:59 AOE is the deadline.
How to submit
Package your solution in the same way as intermediate, upload to the same folder. It should overwrite the existing file. If it doesn't, let me know via email
Teams that missed intermediate deadline
Due to me not clearly stating that the intermediate submission is mandatory and serves as a proof of participation, the teams that missed the email with links for the intermediate submission MUST submit a debug submission to confirm their participation.
Will we move the final deadline?
If we do, it will only be for a couple of days (March 2nd at the latest).
Beta Was this translation helpful? Give feedback.
All reactions