-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reward #26
Comments
Hello, @mratsim Its an interesting question. I along with some of the organizers of this reproducibility challenge organized the first reproducibility workshop. The aim of starting the workshop was two fold.
I'm not sure about ICLR, but I'm pretty sure, someone would keep on organizing Reproducibility workshop at ICML and NIPS, and that should allow you to atleast attend both these conferences. I've no involvement in this reproducibility challenge, so I'm speaking for myself. Thanks for your hard work! 👍 |
Reproducibility is a huge pain point to tackle and kudos for spearheading this initiative.
However implementing potentially sparsely documented papers with potentially implementation "details" that matter is a very time-consuming endeavour. And this is not counting producing several test cases, documenting the code, writing the paper.
I understand that your budget is probably quite limited but at the very least, inspectors should have the opportunity to attend ICLR (or maybe other staple conferences).
A "reproducer" workshop might also send a strong signal and incentive to the academic community that reproducibility is not just a nice-to-have but a must-have.
The text was updated successfully, but these errors were encountered: