Hi Nicolas, Sorry for the inconvenience. When I classifying the data set the last 600 data points are not coming to ModelAggregrator processor. The reason for that case is in the FilterProcessor it creates batches with 200 events and after creating a batch it feeds it to modelAggregator. In modelAggegrator, it gets events batch by batch and it stores 2nd, 3rd, and 4th batches like a buffer. When 5th batch comes 2nd batch release. The question is why they buffer 600 events and why it strat after 1st batch ?
Following screenshot got from ModelAggregator processor and it shows how it buffer 3 batches. On Mon, Oct 31, 2016 at 10:55 PM, Nicolas Kourtellis <[email protected]> wrote: > Hi Jayan, > > I am sorry for the delays but your emails keep going in my spam folder > (I think there are some redirection issues). > > In any case, it would always be helpful to provide more context on your > questions. > I am not sure I understand what you are asking, so please make sure you > provide > us with an example that reproduces your issue or a clear setup that you are > starting > with and what/where you get stuck. > > Thank you! > > Nicolas > > > > > On Mon, Oct 31, 2016 at 4:49 AM, Jayan Vidanapathirana <[email protected]> > wrote: > > > Anyone have any idea about this configuration ? Why they shift 3 batches > ? > > > > On Mon, Oct 31, 2016 at 9:18 AM, Jayan Vidanapathirana <[email protected]> > > wrote: > > > >> Hi, > >> > >> > >> > >> > >> -- > >> Regards, > >> > >> Jayan Vidanapathirana > >> Intern Software Engineer, > >> WSO2. > >> mobile +94715594516 > >> [email protected] > >> <[email protected]> > >> > > > > > > > > -- > > Regards, > > > > Jayan Vidanapathirana > > Intern Software Engineer, > > WSO2. > > mobile +94715594516 > > [email protected] > > <[email protected]> > > > > > > -- > Nicolas Kourtellis > -- Regards, Jayan Vidanapathirana Intern Software Engineer, WSO2. mobile +94715594516 [email protected] <[email protected]>
