**** BEGIN LOGGING AT Mon May 28 03:00:04 2018 May 28 10:12:28 2 reports in so far May 28 11:09:06 jkridner[m]: jkridner|pd : received the package today in good condition , Thanks a lot for the boards :) May 28 11:10:42 great May 28 11:12:38 @vaishnav98_ do you have a scope? did you check the pin mapping and pinmux? May 28 11:15:06 can you modify to build with the bone101 Makefile? mimic the C interface you built and align the API as improvements are made? May 28 11:25:33 jkridner[m]: yes I do have a access to a scope now , are you talking about installation on snappy? the pin mappings are same , but none of the gpio is exported by default and exportGPIOControls() wasn't executed because hw.setPinMode() fails to fetch mux mode.so I had to make a slight modification to fix the issue temporarily. May 28 11:27:24 jkridner[m]: sure, I will do it. May 28 12:03:23 *busy week* May 28 12:04:29 ZeekHuge: What do you think about Wormo's comments from last week about the use of SWIG? May 28 12:07:18 abhishek_: Yeah. I think `SWIG` it is then .. May 28 12:10:26 muneeb17: So, for that I would suggest to first create *ALL* the bindings for one language first, including debug bindings, and sending message etc (maybe everything other than DMA for a while so as to not make it overly complicated) and then let the mentors know that these "main" bindings are done, while you create others using `SWIG`, so that we are able to look into the structure... May 28 12:10:54 abhishek_: ^ makes sense ? Sleep deprived :P so not very sure. May 28 12:14:52 zeekhuge: I have generated bindings using c++ for python, perl, nodejs and lua, and theyre working fine. So, should the `pypruss` bindings be discontinued? May 28 12:20:49 abhishek_: ^ what do you think ? May 28 13:25:08 Let me come back in some time. May 28 13:44:12 muneeb17: Has the code been pushed to the repo? May 28 14:05:08 abhishek_: yes. https://github.com/MuneebMohammed/PRUSS-Bindings/tree/master/swig May 28 14:11:22 abhishek_: zeekhuge : should i create a separate branch and include the generated modules as well? May 28 14:56:23 I'd like to see them, but they shouldn't be a part of the repo May 28 14:57:16 muneeb17: Also since this is a library, there shouldn't be exit() and printf calls in there May 28 14:58:06 I mean any kind of I/O to the console May 28 15:01:23 abhishek_: Ok. So, how should i go for error reporting? May 28 16:02:17 muneeb17: Ideally, language to language specific error handling May 28 16:02:28 Through try-catch for example May 28 16:02:48 But error codes could be a better way May 28 17:07:22 abhishek_: zeekhuge : What should I include in my progress report now? May 28 17:07:54 I mean the next week's plan May 28 17:54:23 ds2 Have some doubts regarding the decoder...as mentioned previously it is not able to recognize some characters at all. For some others I could increase the accuracy a little bit by updating the dictionary...based on the hypothesis files generated for each character...but still it falls short for other audio files...Can u give any suggestions on how to deal with this...should I go on with the idea of updating the May 28 17:54:24 language model after each decoding operation...or go with some other method? May 28 19:50:56 muneeb17: In the report, you can just mention that we are having discussion and further add thoughts we have on it. You can add "Next week's plan" once we get one. **** ENDING LOGGING AT Tue May 29 03:00:04 2018