-
Notifications
You must be signed in to change notification settings - Fork 23
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
ValueError not explaining what's happening in metamodel.fit() #4
Comments
Hi Davide - never seen this error before. Can you please send the dimension of the dataset and the range of values for X? Thanks. |
Hi! Thank you for the very fast answer.
The dimension of my dataset is 963 rows x 121 columns.
Overall in the dataset the minimum and maximum values that I can have are -1 and 726964.
They are almost all integer from 1 to 10 and few columns with larger number. All of them are as float64.
Davide
…---------------------------------------------------------------
Davide Ferrari
Graduate Research Fellow @ UNIMORE
Dipartimento Chirurgico, Medico, Odontoiatrico e di Scienze Morfologiche con interesse Trapiantologico, Oncologico e di Medicina
Dipartimento di Scienze Matematiche, Fisiche e Informatiche
Contacts
email: davideferrari@unimore.it phone: +39 333 99 61 873
https://www.linkedin.com/in/davide-ferrari-195655a0/
---------------------------------------------------------------
On 29 Oct 2020, at 21:11, Ahmed M. Alaa ***@***.***> wrote:
Hi Davide - never seen this error before. Can you please send the dimension of the dataset and the range of values for X? Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQIFDNLBPIGOPPGA2CXTN3SNHD5NANCNFSM4TDNIGHQ>.
|
I am not sure if that's the source of error but 726964 is pretty big and maybe causing some numerical problems. I recommend you normalize all columns to [0, 1] and if that still giving an error you may try fitting a subset of the columns first e.g. 10 features only. Also note that this method does not scale well for very high dimensions, with 121 feature you will get super long equations that are not really interpretable anymore. |
That’s sounds good. I’ll try!
Thank you!
I’ll get to you if things still does not go well.
Have a nice day!!
Davide
… On 30 Oct 2020, at 11:00, Ahmed M. Alaa ***@***.***> wrote:
I am not sure if that's the source of error but 726964 is pretty big and maybe causing some numerical problems. I recommend you normalize all columns to [0, 1] and if that still giving an error you may try fitting a subset of the columns first e.g. 10 features only. Also note that this method does not scale well for very high dimensions, with 121 feature you will get super long equations that are not really interpretable anymore.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#4 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQIFDIAVTYLNF3NBIPHG4DSNKFCVANCNFSM4TDNIGHQ>.
|
Hi! I've got this problem trying to build the metamodel on my dataset.
This is a complete dataset (no NaN) and they are all float64 values, as shown here.
I leave here the trace of the error in which is shown that the ValueError is not explanatory on what is going on.
What do you think is happening?
Thank you very much!
Davide
The text was updated successfully, but these errors were encountered: