Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

Make the improvements suggested in improvements.pdf #4

Open
philipcmonk opened this issue Sep 8, 2017 · 4 comments
Open

Make the improvements suggested in improvements.pdf #4

philipcmonk opened this issue Sep 8, 2017 · 4 comments

Comments

@philipcmonk
Copy link
Contributor

philipcmonk commented Sep 8, 2017

The improvements suggested here seem like they would be very good. We're also interested in other improvements to the checks.

There is a 100 NMR bounty on this issue.

@isaykatsman
Copy link

Hi Philip! The improvements doc was a fairly interesting read. Sounds like there are some fairly interesting things there I would like to get into. However I have a clarification - is the 100 NMR bounty for implementing/solving all of the described issues? Or would it be possible to submit a PR for solving only some of the issues (e.g. focusing on improving Concordance specifically)?

@philipcmonk
Copy link
Contributor Author

@isaykatsman The 100 NMR bounty is for all of the issues, however I'm open to splitting that up into specific parts of it. Can you suggest a reasonable division of tasks/bounty?

Alternatively, if you work together with someone to solve all the tasks, you could split the bounty between yourselves.

@zoso95
Copy link
Contributor

zoso95 commented Sep 18, 2017

We need a quality benchmark before I'd feel comfortable pushing a large algorithmic change. To do this initially I used actual user submissions to calibrate things, but that would be hard to do.

@cpurta
Copy link
Contributor

cpurta commented Oct 12, 2017

For the third proposed concordance solution (use of the targets in the Test Set), how exactly would comparing the log loss of the validation and the test sets incur a data leak? Is it that users could modify only the test set predictions and based on the concordance outcome determine if their test set predictions are getting a better log loss?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants