On Fri, Feb 27, 2015 at 7:26 AM, Srinath Perera srin...@wso2.com wrote:
Mohan, could you check when you can?
Sure, will do..
Thanks,
Mohan
On Fri, Feb 27, 2015 at 6:46 AM, Ginnaliya Gamathige, Lahiru Manananda
lginn...@indiana.edu wrote:
Hi Srinath,
I have wrapped up the
Mohan, could you check when you can?
On Fri, Feb 27, 2015 at 6:46 AM, Ginnaliya Gamathige, Lahiru Manananda
lginn...@indiana.edu wrote:
Hi Srinath,
I have wrapped up the implementation and sent a pull request. Please let
me know if there are any issues with merging the pull request.
I
Hi All,
I have finished implementing a Window (ClassifyHtWindowProcessor) to do the
classification based on Hoeffding Tree. So if you define the event stream as
below
you can send initial set of events to build the classification model then after
the building the tree with given number of
Can I suggest s/optional/options/
Optional means that you can leave this out. Options means you must choose
one of the following.
Paul
On 8 October 2014 08:31, Ginnaliya Gamathige, Lahiru Manananda
lginn...@indiana.edu wrote:
Hi All,
I have finished implementing a Window
Sorry to be picky, but if Ht stands for Hoeffding Tree then it should be HT
(all caps).
Paul
On 8 October 2014 09:40, Paul Fremantle p...@wso2.com wrote:
Can I suggest s/optional/options/
Optional means that you can leave this out. Options means you must choose
one of the following.
Paul
Also it seems like mostly this is known as VFDT in the literature (Very
Fast Decision Tree). So that might be a better name (e.g. ClassifyVFDT).
PS this is really cool.
Paul
On 8 October 2014 09:41, Paul Fremantle p...@wso2.com wrote:
Sorry to be picky, but if Ht stands for Hoeffding Tree
Hi Paul,
Sorry for the typo with option and I will fix it. But for VFDT there are
multiple algorithms that you can, do you think we shouldn’t show it in the
window name ?
Thanks
Lahiru
On Oct 8, 2014, at 4:45 AM, Paul Fremantle
p...@wso2.commailto:p...@wso2.com wrote:
ClassifyVFDT
In that case, I'd just call it ClassifyHT
Paul
On 8 October 2014 16:22, Ginnaliya Gamathige, Lahiru Manananda
lginn...@indiana.edu wrote:
Hi Paul,
Sorry for the typo with option and I will fix it. But for VFDT there are
multiple algorithms that you can, do you think we shouldn’t show it
Hi Suho,
I have modified Attribute class which will keep all the possible values in
attribute and can create the numeric value 2 for “rainy”. In the incoming event
we can have the possible values for each attribute. I have the code committed
to my local github[1] and once I have a working copy
I think this is really useful. I'm not convinced the word nominal is
well-known enough to be completely clear in this context.
what about
define stream weather( outlook options={sunny, overcast, rainy} )
Paul
On 21 September 2014 19:45, Ginnaliya Gamathige, Lahiru Manananda
Hi Paul,
On Sep 23, 2014, at 4:35 AM, Paul Fremantle
p...@wso2.commailto:p...@wso2.com wrote:
I think this is really useful. I'm not convinced the word nominal is well-known
enough to be completely clear in this context.
what about
define stream weather( outlook options={sunny, overcast,
I think this is OK. Suho, WDYT?
On Mon, Sep 22, 2014 at 12:15 AM, Ginnaliya Gamathige, Lahiru Manananda
lginn...@indiana.edu wrote:
Hi Devs,
I am developing a classification algorithm for siddhi and I have a
requirement of defining attributes as a nominal attribute.
Nominal attribute
Looks OK.
Can you please clarify how would you write queries in this case? (e.g If
its rainy how would you check?)
and internally how all of these will be processed?
Regards
Suho
On Tue, Sep 23, 2014 at 10:30 AM, Srinath Perera srin...@wso2.com wrote:
I think this is OK. Suho, WDYT?
On
Hi Devs,
I am developing a classification algorithm for siddhi and I have a requirement
of defining attributes as a nominal attribute.
Nominal attribute is similar to a string attribute but during the definition we
have to give the possible values for that attribute.
One of the value from that
14 matches
Mail list logo
