-
Updated
Feb 21, 2022 - Python
transfer-learning
Here are 2,444 public repositories matching this topic...
Related: awslabs/autogluon#1479
Add a scikit-learn compatible API wrapper of TabularPredictor:
- TabularClassifier
- TabularRegressor
Required functionality (may need more than listed):
- init API
- fit API
- predict API
- works in sklearn pipelines
-
Updated
Feb 9, 2022
-
Updated
Feb 22, 2022 - Python
-
Updated
Dec 9, 2021 - Python
-
Updated
Jul 9, 2021 - Python
-
Updated
Feb 20, 2022
-
Updated
Oct 6, 2021
-
Updated
Nov 23, 2021 - Python
-
Updated
Jun 14, 2021 - Jupyter Notebook
I'm playing around with this wonderful code but I'm running into a curious issue when I try to train the model with my own data.
I replicated the personachat_self_original.json file structure and added my own data. I deleted dataset_cache_OpenAIGPTTokenizer file but when I try to train, I get this error:
INFO:train.py:Pad inputs and convert to Tensor
Traceback (most recent call last)
-
Updated
Feb 3, 2022 - Python
-
Updated
Feb 24, 2022 - Python
-
Updated
Feb 10, 2022 - Python
-
Updated
Feb 25, 2022
-
Updated
Dec 27, 2021 - Jupyter Notebook
-
Updated
Jan 20, 2022 - Python
-
Updated
Sep 16, 2020 - Python
-
Updated
Jan 1, 2019 - Python
We have a lot of antiquated docstrings that don't render well into ReadTheDocs. A kind of grunge (but incredibly useful) task would be to refactor these docstrings into proper ReadTheDocs format. This would allow us to render them effectively...
-
Updated
Jul 26, 2019 - Python
-
Updated
Feb 15, 2022 - Jupyter Notebook
-
Updated
Dec 31, 2021 - Python
Per this comment in #12
-
Updated
Oct 16, 2019 - Python
-
Updated
Dec 7, 2020 - Jupyter Notebook
-
Updated
Jan 9, 2022
Improve this page
Add a description, image, and links to the transfer-learning topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the transfer-learning topic, visit your repo's landing page and select "manage topics."
_handle_duplicate_documentsand_drop_duplicate_documentsin the elastic search document store will always reportself.indexas the index with the conflict, which is obviously incorrect.Edit: Upon further investigation, this is actually a lot worse. Using multiple indices with the ElasticSearch DocumentStore is completely broken due to the fact, that this is used in `_handle_duplicate_do