Re: evaluating classification accuracy

2014-07-30 Thread SK
I am using 1.0.1 and I am running locally (I am not providing any master URL). But the zip() does not produce the correct count as I mentioned above. So not sure if the issue has been fixed in 1.0.1. However, instead of using zip, I am now using the code that Sean has mentioned and am getting the c

Re: evaluating classification accuracy

2014-07-29 Thread Sean Owen
Yes, in addition, I think Xiangrui updated the examples anyhow to use a different form that does not rely on zip: test.map(v => (model.predict(v.features), v.label)) It avoid evaluating test twice, and avoids the zip. Although I suppose you have to bear in mind it now calls predict() on each elem

Re: evaluating classification accuracy

2014-07-28 Thread Xiangrui Meng
Are you using 1.0.0? There was a bug, which was fixed in 1.0.1 and master. If you don't want to switch to 1.0.1 or master, try to cache and count test first. -Xiangrui On Mon, Jul 28, 2014 at 6:07 PM, SK wrote: > Hi, > > In order to evaluate the ML classification accuracy, I am zipping up the > p