Skip to content
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

Overall discussion for Tip 1 #242

Open
SiminaB opened this issue Oct 7, 2020 · 2 comments
Open

Overall discussion for Tip 1 #242

SiminaB opened this issue Oct 7, 2020 · 2 comments

Comments

@SiminaB
Copy link
Collaborator

SiminaB commented Oct 7, 2020

This is to discuss outstanding issues for Tip 1, on whether Deep Learning should be used in the first place, https://github.com/Benjamin-Lee/deep-rules/blob/master/content/03.ml-concepts.md. Related to: #241

@SiminaB
Copy link
Collaborator Author

SiminaB commented Oct 7, 2020

  • Part of tip 2 should also now go into Tip 1, since a simpler ML model may suffice. Eg the second paragraph:

Depending on the amount and the nature of the available data, as well as the task to be performed,
deep learning may not always be able to outperform conventional methods. As an illustration,
Rajkomar et al. [13] found that simpler baseline models achieved performance comparable with that
of DL in a number of clinical prediction tasks using electronic health records, which may be a surprise
to many. Another example is provided by Koutsoukas et al., who benchmarked several traditional
machine learning approaches against deep neural networks for modeling bioactivity data on
moderately sized datasets [14]. The researchers found that while well tuned deep learning
approaches generally tend to outperform conventional classiers, simple methods such as Naive
Bayes classication tend to outperform deep learning as the noise in the dataset increases.

  • I'm not a huge fan of the heritability example, because there's no citation. Like, this could be a problem, sure, but has it ever been a problem in practice? We can use reference 39 as an example instead (or another similar example). This is also related to Tip 8, since if you can't interpret the models you don't even know what possible confounders may have gotten included.

@Benjamin-Lee
Copy link
Owner

I've gone and removed the heritability part in #241 and am moving the part from tip 2 over now

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

No branches or pull requests

2 participants