Skip to content
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

Disable modelselection for some cases #58

Open
Saurabh7 opened this issue Jul 23, 2014 · 6 comments
Open

Disable modelselection for some cases #58

Saurabh7 opened this issue Jul 23, 2014 · 6 comments

Comments

@Saurabh7
Copy link
Contributor

No description provided.

@Saurabh7
Copy link
Contributor Author

@karlnapf
Things should be a bit better now with the fixes here and there. Have a look when you find some time.

The major problem still is using modelselection in web-demos on large dataset and various combination arising.
I think we should disable it when the data is larger than some point, and mention that in the description. That should simplify things and stop a lot of nastiness. Please let me know you thoughts.

@karlnapf
Copy link
Member

I agree, there should maybe be a timeout function?
Another alternative could be to provide an interface to cross-validation where people can evaluate the say accuracy/MSE for the parameters given and then do the model-selection themselves.
But for small datasets, its still very nice to have this.

Any ideas how to restrict larger datasets?

@Saurabh7
Copy link
Contributor Author

hmm I could set up client side timeouts but they won't help afaik and we have no idea about server stuff this is going to run on.

xval can be done but in similar way, exposing potential big computations through the interface will lead to problems, no?

about restricting datasets, maybe just check num of samples (say < 100 for demo purposes) ??

@karlnapf
Copy link
Member

yes you are right, exposing potantial big computation through this interface is critical, but i think we can restrict things in exacly that way, only allow for small number of samples. If there are more points, an error pops up saying "Model selection only supported for less than N samples due to computational costs)

@abinashmeher999
Copy link

@Saurabh7 @karlnapf are we doing all the computation on the server side and returning the results? Is the large dataset provided by the user? If computation is the issue, I have heard of JApplet that runs on the client side, maybe we can use that. What do you say?

@karlnapf
Copy link
Member

That is a good idea in principle, but we currently dont have ressources to think about this. If you wanna come up with something, feel free, but you would be on your own.
For now, restricting demos to toy problems is the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants