User 1375 | 3/9/2015, 7:55:09 PM
I've successfully launched a GraphLab Server in EC2 via launchEC2, loaded some data from S3 into that server, done some feature engineering, trained a default logistic regression classifier, and now I'm ready to calibrate, say, the regularization hyperparameter l2penlaty using modelparametersearch. I'm finding that there's no way to use that API function in a way that makes use of the existing EC2 instance running the GraphLab Server. Is that correct? I've tried environment.Local and environment.AsyncLocal, but those seem to refer literally to my local ipython process outside of EC2, instead of "local" from the point of view of the GraphLab Server running in EC2, which was another possible interpretation. I was looking to perform this parameter search within the existing GraphLab Server so as not to have to move the data around i.e. copy to S3, spin up new EC2 machines via modelparametersearch feeding it environment.EC2(...), etc. I just wanted to exploit the various vCPUs in the existing GraphLab Server, and thought that environment.LocalAsync would do it. Any help would be highly appreciated. Thanks.