-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
Unify ecosystem.md
#1923
Unify ecosystem.md
#1923
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1923 +/- ##
=======================================
Coverage 86.43% 86.43%
=======================================
Files 18 18
Lines 1430 1430
=======================================
Hits 1236 1236
Misses 194 194 Continue to review full report at Codecov.
|
Co-authored-by: Carlo Lucibello <[email protected]>
Co-authored-by: Carlo Lucibello <[email protected]>
Co-authored-by: Kyle Daruwalla <[email protected]>
Thank you for all the suggestions! Should I also add |
…nsh-cpp/Flux.jl into inconsistent-ecosystem-docs
Co-authored-by: lorenzoh <[email protected]>
Co-authored-by: lorenzoh <[email protected]>
Co-authored-by: lorenzoh <[email protected]>
docs/src/ecosystem.md
Outdated
## Parameters | ||
|
||
- [Parameters.jl](https://github.com/mauro3/Parameters.jl) types with default field values, keyword constructors and (un-)pack macros. | ||
- [ParameterSchedulers.jl](https://github.com/darsnack/ParameterSchedulers.jl) standard scheduling policies for machine learning. | ||
|
||
## Statistics | ||
|
||
- [OnlineStats.jl](https://github.com/joshday/OnlineStats.jl) provides single-pass algorithms for statistics. | ||
|
||
## Time series | ||
|
||
- [FluxArchitectures.jl](https://github.com/sdobber/FluxArchitectures.jl) is a collection of advanced network architectures for time series forecasting. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice to have section headings, but perhaps they could be better ordered? Making rough groups, ordered by how closely associated they are to Flux:
- Actual Flux models: Vision / Language / Graph / Reinforcement learning / Time series
- Tools closely associated with Flux, maybe defined as things you're unlikely to have met if you never used Flux: Datasets / FastAI.jl / Plumbing / ParameterSchedulers.jl
- Differentiable but not necc. ML tools, like SciML, Probabilistic programming
- Useful things which aren't domain-specific at all: ArgParse.jl, ProgressMeter.jl, DataFrames.jl
Maybe they even want another level of headings, not sure. Or maybe there should be only 4-5 H2 headings, but some text between bullet point lists, e.g. under ## Flux models
lists Vision, NLP, RL, etc. ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, grouping these headings under broader H2 headings makes sense. This would definitely make it easier to navigate through the page. I'll add them!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closes #1922
Added all the packages from the website to the docs!
PR Checklist