Python Forum

Full Version: ValueError: Unknown label type: 'continuous-multioutput'
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am running this code: https://github.com/dyt08/diabetes-predic...etes.ipynb on google colab.

and on this part:

X_SMOTE, y_SMOTE = smote.fit_resample(X_train, y_train)
I get this error:

Error:
ValueError: Unknown label type: 'continuous-multioutput'
I have been looking it many days, and I have tried many solutions that people proposed via google search, without success. Does anybody know what is wrong? And how to fix it?
There is no answer because it is so difficult I assume... Smile
If i test on google colab NoteBook,it works for me.
Ok, so it seems that my dataset has the problem... So, what form ("rules") should my dataset follow? In other words, how can I fix it?
(Sep-13-2023, 08:10 AM)hobbyist Wrote: [ -> ]So, what form ("rules") should my dataset follow? In other words, how can I fix it?
The dataset that used in example Dataset of Diabetes.csv
Data Understanding
Under here you see all that the dataset have to include.
Did you try the example dataset?
(Sep-13-2023, 03:58 PM)deanhystad Wrote: [ -> ]Did you try the example dataset?

No
(Sep-13-2023, 05:11 PM)hobbyist Wrote: [ -> ]
(Sep-13-2023, 03:58 PM)deanhystad Wrote: [ -> ]Did you try the example dataset?

No
Why not? That would be the first thing I tried. I would likely do that before making my own dataset. I would run the example to test that I was using the software correctly. When the software raised an exception running my new dataset that would point me toward the dataset being the problem. I would then look to see if there was any guidance provided for creating a dataset. Actually. I would re-read the document describing how to make a dataset because I would've searched for that document before trying to make my own.

If I couldn't figure out the problem, I might post a question to this forum. I would give a history describing what I had done, providing useful information as opposed to "I have been looking it many days, and I have tried many solutions that people proposed via google search, without success". Something like: "I ran this project on colab and it ran fine until I tried using my own dataset. This is my dataset below..."

When you get no response to your question it usually means you didn't ask a good question. There is no way anybody here could answer your question since the error was in your dataset, something nobody but you have access to. Do better. Strive for your next post having enough detail that we don't have to go back-and-forth to get enough info to have a hope of understanding what is going on.