Hi Maheshakya, sorry for the incomplete message.I have set up the dev environment and now i am trying to remotely debug. The following steps were done. 1. build product-cep, carbon-ml and product-ml by source. 2. go through their code bases and trying to understand the way and the flow you developed. 3. i have set up break point in org.wso2.carbon.ml.siddhi.extension in carbon-ml 4. start the ./wso2server.sh debug 5005 in the SNAPSHOT directory of product-ml 5. trying to trigger the break points with the [1] reference.break points are placed in the PredictStreamProcessor.java file within the extention.
This is the way i followed. I was trying to remotely debug the ML core by putting break-points in ml core.(org.wso2.carbon.ml.core) in spark java files. Is this the right way to do those things. [1] https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension On Mon, May 2, 2016 at 11:19 AM, Mahesh Dananjaya <[email protected] > wrote: > Hi maheshakya, > I have set up the dev environment and now i am trying to remotely debug. > The following steps were done. > 1. build product-cep, carbon-ml and product-ml by source. > 2. go through their code bases and trying to understand the way and the > flow you developed. > 3. i have set up break point in > > > On Thu, Apr 28, 2016 at 7:05 PM, Mahesh Dananjaya < > [email protected]> wrote: > >> Hi Maheshakya, >> ok.i got it.thank you. >> regards, >> Mahesh. >> >> On Thu, Apr 28, 2016 at 6:56 PM, Maheshakya Wijewardena < >> [email protected]> wrote: >> >>> Hi Mahesh, >>> >>> The links was an example of remote debugging WSO2 server. What you need >>> to debug is org.wso2.carbon.ml.siddhi.extension in carbon-ml. >>> >>> Best regards. >>> >>> On Thu, Apr 28, 2016 at 4:52 PM, Mahesh Dananjaya < >>> [email protected]> wrote: >>> >>>> Hi Maheshakya, >>>> thank you for your help.i have already built all three sources and now >>>> i am trying to get familiar with your code base. i even build the >>>> carbon-kernel by source. >>>> As you mentioned [1] is related to debug the kernel, do i really need >>>> to debug the carbon kernel in my case. I am trying to remotely debug ml and >>>> as i got it correct it is the same way as reference[1, but not the kernel.I >>>> can go with others. >>>> BR, >>>> mahesh. >>>> >>>> [1] https://dzone.com/articles/how-debug-wso2-carbon-kernel >>>> >>>> On Mon, Apr 25, 2016 at 5:49 PM, Maheshakya Wijewardena < >>>> [email protected]> wrote: >>>> >>>>> Hi Mahesh, >>>>> >>>>> Congratulations and welcome to GSoC 2016. You did a great job in >>>>> preparing the proposal. Now it's time to dig deep and get started with the >>>>> project. >>>>> >>>>> First of all you need to familiarize with the code base. We have >>>>> agreed to implement this with CEP event streams. We already have a CEP >>>>> extension for predictions [1][2]. Go through this implementation and >>>>> familiarize your self with that. You need to understand how: >>>>> >>>>> 1. Even streams are consumed >>>>> 2. predictions are made from individual event >>>>> 3. Results are sent back >>>>> >>>>> Get WSO2 ML and CEP sources (You may use latest released version of >>>>> CEP) and build the products. Get both carbon-ml[3] and product-ml[4] >>>>> masters and create new branches for your work from masters. >>>>> >>>>> After you build the products, you may need to do remote debugging[5] >>>>> to understand the flow. So please follow an example of real time >>>>> prediction >>>>> with ML with debugging and get some idea. The component you need to debug >>>>> is org.wso2.carbon.ml.siddhi.extension. >>>>> >>>>> Next tasks would be implementing online learning algorithms in plain >>>>> java with spark ml lib and integrating those to ML. We also need to come >>>>> up >>>>> with a proper and detailed architecture to employ those algorithms in ML. >>>>> Getting familiar with the aforementioned sections would give you some >>>>> insight on how this should be implemented. >>>>> >>>>> So please try to get a quick grasp then you can start the >>>>> implementation. Let us know if you have any questions or you get stuck >>>>> somewhere. >>>>> >>>>> Also, please always add WSO2 developer's list as well when you >>>>> communicate with us regarding the project so that you can get opinions and >>>>> feedback from others as well. >>>>> >>>>> Best regards. >>>>> >>>>> [1] >>>>> https://docs.wso2.com/display/ML110/WSO2+CEP+Extension+for+ML+Predictions#WSO2CEPExtensionforMLPredictions-Siddhisyntaxfortheextension >>>>> >>>>> [2] >>>>> https://github.com/wso2/carbon-ml/tree/master/components/extensions/org.wso2.carbon.ml.siddhi.extension >>>>> >>>>> [3] https://github.com/wso2/carbon-ml >>>>> >>>>> [4] https://github.com/wso2/product-ml >>>>> >>>>> [5] https://dzone.com/articles/how-debug-wso2-carbon-kernel >>>>> >>>>> >>>>> On Mon, Apr 25, 2016 at 3:33 PM, Mahesh Dananjaya < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> thank you for accepting my GSOC 2016 proposal and i am looking >>>>>> forward for the further instruction and project continuation. thank you >>>>>> very much. >>>>>> regards, >>>>>> Mahesh. >>>>>> >>>>>> -- >>>>> Pruthuvi Maheshakya Wijewardena >>>>> [email protected] >>>>> +94711228855 >>>>> >>>>> >>>>> >>>> >>> >>> >>> -- >>> Pruthuvi Maheshakya Wijewardena >>> [email protected] >>> +94711228855 >>> >>> >>> >> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
