Benjamin-Lee / Benjamin-Lee/deep-rules
Have access to adequate infrastructure
- Dominant language
- HTML
- Stars
- 226
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
**Have you checked the [list of proposed rules](https://github.com/Benjamin-Lee/deep-rules/issues?q=is%3Aissue+is%3Aopen+label%3Arule) to see if the rule has already been proposed?**
- [x] Yes
**Did you add yourself as a [contributor](https://github.com/Benjamin-Lee/deep-rules/blob/master/contributors.md) by making a pull request if this is your first contribution?**
- [x] Yes, I added myself or am already a contributor
**Feel free to elaborate, rant, and/or ramble.**
As far as I know, we don't have anything about infrastructure demands, yet. I.e., using DL in one's research will likely require access to multiple GPUs etc and is usually of higher computational demand compared to traditional models. So, researchers who relied on laptops and off-the-shelf desktop workstations for computational analyses should made aware that DL usually requires a bit more :).
This could potentially be mentioned in several places, e.g.,
- 2 Use traditional methods to establish performance baselines ([#41](https://github.com/Benjamin-Lee/deep-rules/issues/41), [#11](https://github.com/Benjamin-Lee/deep-rules/issues/11), [#10](https://github.com/Benjamin-Lee/deep-rules/issues/10))
- 3 Understand the complexities of training deep neural networks
- 6 Tune your hyperparameters extensively and systematically ([#42](https://github.com/Benjamin-Lee/deep-rules/issues/42), [#11](https://github.com/Benjamin-Lee/deep-rules/issues/11))
**Any citations for the rule?** (peer-reviewed literature preferred but not required)
- [DOI](doi.org/DOI_goes_here)
Contributor guide
Assessment
This issue has not been assessed yet.