* added documentation about small time budget
* small change for better clarity
* Update website/docs/Use-Cases/Task-Oriented-AutoML.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
---------
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update Research.md
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Research.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
---------
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
Co-authored-by: Qingyun Wu <qingyun.wu@psu.edu>
* Refactor into automl subpackage
Moved some of the packages into an automl subpackage to tidy before the
task-based refactor. This is in response to discussions with the group
and a comment on the first task-based PR.
Only changes here are moving subpackages and modules into the new
automl, fixing imports to work with this structure and fixing some
dependencies in setup.py.
* Fix doc building post automl subpackage refactor
* Fix broken links in website post automl subpackage refactor
* Fix broken links in website post automl subpackage refactor
* Remove vw from test deps as this is breaking the build
* Move default back to the top-level
I'd moved this to automl as that's where it's used internally, but had
missed that this is actually part of the public interface so makes sense
to live where it was.
* Re-add top level modules with deprecation warnings
flaml.data, flaml.ml and flaml.model are re-added to the top level,
being re-exported from flaml.automl for backwards compatability. Adding
a deprecation warning so that we can have a planned removal later.
* Fix model.py line-endings
* Pin pytorch-lightning to less than 1.8.0
We're seeing strange lightning related bugs from pytorch-forecasting
since the release of lightning 1.8.0. Going to try constraining this to
see if we have a fix.
* Fix the lightning version pin
Was optimistic with setting it in the 1.7.x range, but that isn't
compatible with python 3.6
* Remove lightning version pin
* Revert dependency version changes
* Minor change to retrigger the build
* Fix line endings in ml.py and model.py
Co-authored-by: Qingyun Wu <qingyun.wu@psu.edu>
Co-authored-by: EgorKraevTransferwise <egor.kraev@transferwise.com>
* make performance test reproducible
* fix test error
* Doc update and disable logging
* document random_state and version
* remove hardcoded budget
* fix test error and dependency; close#777
* iloc
* Pending changes exported from your codespace
* Update flaml/automl.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update flaml/automl.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update flaml/ml.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update flaml/ml.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Examples/Integrate - Scikit-learn Pipeline.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* added documentation for new metric
* Update flaml/ml.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* minor notebook changes
* Update Integrate - Scikit-learn Pipeline.md
* Update notebook/automl_classification.ipynb
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update integrate_azureml.ipynb
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* install editable package in codespace
* fix test error in test_forecast
* fix test error in test_space
* openml version
* break tests; pre-commit
* skip on py10+win32
* install mlflow in test
* install mlflow in [test]
* skip test in windows
* import
* handle PermissionError
* skip test in windows
* skip test in windows
* skip test in windows
* skip test in windows
* remove ts_forecast_panel from doc
* Small docstring change for clarity
* Added tentative changes to docs
* Update website/docs/Use-Cases/Task-Oriented-AutoML.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update flaml/model.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Updated model.py to reflect `n_jobs = None` suggestion
* Updated tutorial to reflect `n_jobs=None` suggestion
* Update model.py
Improved string
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
Co-authored-by: Qingyun Wu <qingyun.wu@psu.edu>
As described in #777, I had trouble executing the setup using zsh.
Eventually, I noticed that I had to escape the brackets.
My proposed change includes both brackets to be escaped, however for me it was enough to escape the opening one only, since as far as I know a trailing non-escaped closing bracket will then be recognized, accordingly.
* rm classification head in nlp
* rm classification head in nlp
* rm classification head in nlp
* adding test cases for switch classification head
* adding test cases for switch classification head
* Update test/nlp/test_autohf_classificationhead.py
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* adding test cases for switch classification head
* run each test separately
* skip classification head test on windows
* disabling wandb reporting
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* fix test nlp custom metric
* Update website/docs/Examples/AutoML-NLP.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* Update website/docs/Examples/AutoML-NLP.md
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
* fix test nlp custom metric
Co-authored-by: Chi Wang <wang.chi@microsoft.com>
Animaholic