Spaces:
Running
on
CPU Upgrade
Competition Wrap Up
Thanks everyone for your participation and hard work!
The private leaderboad has been revealed.
Please prepare your writeups and repos for submission no later than June 13th.
We will follow up with additional details tomorrow and announce the official winners after reviewing the repos and writeups.
We strongly encourage all teams to submit a writeup regardless of leaderboard position: we have discretionary prize money and allocated short talks which we may award in the case of interesting solutions or analysis regardless of leaderboard position (in addition to the leaderboard based rewards).
Thanks again and we look forward to learning about your approaches!
All the best!
S23DR Organizing Team
Hi! Thanks for all your help in provding logs and helping with the required packages throughout the competition.
Regarding the write-up, is there a format for a workshop template that we should use? Also what's the expected length of the write-up? Maybe that's what you meant when you said you'll provide more details, but I was just curious. Thanks again!
Hi,
You can use standard LaTeX CVPR template https://github.com/cvpr-org/author-kit/releases and we will add it to the workshop website - that is a preferable way.
We don't have minimum or maximum page requirement, but we expect that description would be detailed enough, and any comparisons, ablations and discussion sections are encouraged.
Regarding the code, you also may open the repo with your solution, or share it privately with us (
@jacklangerman
and
@dmytromishkin
)
--
Best, orgs.
Thanks! So the write up should also be uploaded on the repo, right?
Yes.
@kcml do you plan to share your solution? :)
@dmytromishkin , Thanks for asking. I'd set the repo open. Let me know if you find anything I can add.
@kc92
we can see your solution, but there is no write-up yep. Could you please add it?
@Siromanec
Would you like to share your solution? You don't get the 1-3 place for the prize, but if we find your solution interesting, we may consider awarding discretionary prize.
@dmytromishkin I am currently writing the writeup and will gladly share the solution. To share it should I make the repo public and also share the repo link too? Also, I was writing a journal during the competition, which highlights my thought process in real time and has a lot of visualizations, but is quite informal and big. Should I share it too?
sharing both would be great @Siromanec .
This goes for everyone: any context, insights, etc. are welcome, helpful, and will be considered.
@kcml also it would be cool, if you could include the maybe not the best by score, but still interesting learning-based solution.
@kc92 we can see your solution, but there is no write-up yep. Could you please add it?
@dmytromishkin
I have added the write-up to the repo now. I had planned to do a few more ablations, but was short on time.
I also haven't cleaned up my the code as you had already taken a look at it. Will probably prepare a cleaner git repo soon and add you to that.
I uploaded the write-up and the journal
@dmytromishkin Yes, I will add more into the doc.