3 ms·
Right. At this point you kind-of have to just imagine the workflow (which is actually what I do quite a bit before tackling an analytics problem). You have to
by physcab 16y ago
Right. At this point you kind-of have to just imagine the workflow (which is actually what I do quite a bit before tackling an analytics problem). You have to envision an ultimate goal of what you want your output to be, an understanding of what's being done to your data, and then make sure you correctly accumulate and format your data to insert into the system. When they flush out their API docs (and let me use their API) I will write another post!
- carbocation 16y agoRight. I don't mean this negatively, but your post is not really about Google's prediction tool at all. It's a general setup to Naive Bayes. I understand that what got you enthusiastic to write this up was Google's announcement, but at the end of the day I could remove any reference to google and the post would be just fine. I suppose I got excited, despite knowing about the general procedure already, because I thought this post was directed at how to actually use the google offering. It's just a title issue, I guess.
- physcab 16y agoSorry about that. A lot of the meta-discussion I had with others (mostly non-techs or semi-techs) this past week about the Prediction API was simply "But what would I use this for?" kinds of questions. That's what this post was meant to address. Incidentally this is only my second post, and I'll continue to write both on general insights to existing public data, as well as more technical (with-code) posts geared towards those who want to get their hands dirty.
- carbocation 16y agoFantastic! This community (or, at least, I) will absolutely devour content written by someone with your background.