tuning-parameters
Here are 42 public repositories matching this topic...
-
Updated
Jun 7, 2018 - Python
-
Updated
Oct 27, 2020 - Jupyter Notebook
-
Updated
Feb 20, 2020 - Python
-
Updated
Oct 21, 2020 - Jupyter Notebook
-
Updated
Dec 13, 2019 - R
-
Updated
Dec 6, 2019 - HTML
-
Updated
Apr 19, 2018 - R
-
Updated
Nov 29, 2018 - C++
-
Updated
Jun 5, 2020 - Python
-
Updated
Apr 24, 2020 - Python
-
Updated
Sep 30, 2020 - R
-
Updated
Oct 7, 2020 - Python
-
Updated
Dec 2, 2019 - Python
-
Updated
Apr 27, 2020 - Jupyter Notebook
-
Updated
Sep 16, 2020 - Jupyter Notebook
-
Updated
Mar 7, 2019 - Jupyter Notebook
-
Updated
Oct 21, 2020
-
Updated
Mar 17, 2019 - Python
-
Updated
Jun 16, 2019 - Jupyter Notebook
-
Updated
Jun 30, 2017
Is your feature request related to a problem? Please describe.
Generally, it's desirable to keep package dependencies as lean as possible. We use humanfriendly to parse a strings like "50b", "100kb", and "250mb" and convert them to integer values. We should be able to remove this dependency by implementing the parse_size() function in util.py (see [here](https://github.com/umayrh/sparkt
-
Updated
Mar 2, 2018 - Python
-
Updated
Aug 28, 2019 - Jupyter Notebook
-
Updated
Dec 8, 2018 - Jupyter Notebook
-
Updated
May 21, 2019 - HTML
-
Updated
Jan 11, 2018 - Jupyter Notebook
-
Updated
Feb 14, 2020 - Python
-
Updated
Nov 15, 2019 - Jupyter Notebook
-
Updated
Feb 4, 2020 - MATLAB
Improve this page
Add a description, image, and links to the tuning-parameters topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the tuning-parameters topic, visit your repo's landing page and select "manage topics."


The PR JuliaData/CategoricalArrays.jl#310 means that an array with elements of type
Symbolcan no longer be wrapped as aCategoricalArray.This means all MLJ documentation and test code that uses symbols in categorical data must be refactored to use strings instead.
These repos, at least, need checking/refactoring, in order of priority:
MLJ
[ ]