Author: akoganti

Ashika’s Status Update for May 2

Ashika’s Status Update for May 2

At the start of the week, apart from presenting on Monday, I finished getting the story cohesion data and adding them to the final presentation and final report: Variable Random Input Stories User Generated Stories Original Stories Logical Sense 1.6 4.0 8.4 Theme 5.0 6.13 

Ashika’s Status Update for April 25

Ashika’s Status Update for April 25

This week, I worked on testing all the storytelling components of KATbot to see if they meet our metrics. For the part of speech testing, I created a python testing script to check the accuracy, with both correct and incorrect inputs, of the part of 

Team Status Update for April 25

Team Status Update for April 25

This week, Jade and Ashika focused on testing the audio and storytelling components respectively. They also cleaned up minor bugs in the software as they went. Abha continued to work on assembling the robot. Everyone worked on creating the final presentation for next week.

There are no new risks and no design changes. Everything is still on schedule and performing well.

Ashika’s Status Update for April 18

Ashika’s Status Update for April 18

This week, I mainly focused on tying up loose ends and helping the others with integration. As mentioned in the team status report, I modified the program to output the entire story once it is finished with all the new words bolded so users can 

Team Status Update for April 18

Team Status Update for April 18

This week, all three of us worked on integration and improving our system to prepare for the demo next week. Ashika and Abha worked on improving the display, and Jade worked on improving the pi to laptop socket communication. Abha also continued to work on 

Team Status Update for April 11

Team Status Update for April 11

This week, Jade created a server/client program for laptop to raspberry pi communication, primarily for the audio input/output. Abha worked on installing all the necessary packages and tools, both on her laptop and the raspberry pi, to run the storytelling algorithm and the audio components. Ashika helped both Jade and Abha, and she finished grammar correction and made some new templates.

There were no design changes. One of the obstacles we are facing is getting the display code working on the pi. This will require some more research on what tools to install. If it does not work, we will have to rewrite the display code using a different package.

Ashika’s Status Update for April 11

Ashika’s Status Update for April 11

This week, for the storytelling component alone, I finally finished grammar correction for nouns and I worked on creating a few more templates. I changed the format slightly to improve sentence tokenization, which makes it easier to send the story sentence by sentence to the 

Ashika’s Status Update for April 4

Ashika’s Status Update for April 4

This week I started integration with Abha for the text display. On my end, I created a display window (shown above) in Python that runs on a separate thread from the main program. This window is the same size as the pi and displays the 

Ashika’s Status Update for Mar 28

Ashika’s Status Update for Mar 28

This week I accomplished the following tasks:

  1. Grammar correction for verbs. I still need to do this for singular vs plural nouns, but it is working very well for verbs.
  2. User response processing for non-story states. All user responses are supported, including timeouts and words that cannot be identified. The full user flow chart has now been implemented.
  3. Integration with audio input/output. I worked with Jade for this part. There were no major obstacles, besides making sure that we both had all the python packages installed to run the code. The main KATbot python program that I wrote is run, and whenever it needs to speak or receive input, it calls one of the audio functions that Jade created.
  4. Random FitBERT inputs. To add variety to the stories, some of the blanks are randomly (but still according to sentence context) filled in by FitBERT. To do this step I gathered a list of 1000+ vocabulary words, from preK to 3rd grade, and fed this list into FitBERT along with the template sentence and the part of speech needed. It is working really well for the one example template I have been using, but I will have to create more templates to see if I want to tweak this feature at all.

At this point, I have finished all the components of the storytelling algorithm. I just need to do some more error handling, and if I have time, improve certain features (like antonym generation). I think it is ready for the first demo day, so I am very much on track.

Next week, I will first work on cleaning up the code and writing documentation, just so that it is easier for my teammates to understand what the programs do as we integrate. I will also finish grammar correction for nouns. After this, I will finally make some templates, as well as document how to make templates. If Abha is ready, I can start integrating my part with the text displays.

Team Status Update for March 28

Team Status Update for March 28

What we did Jade and Ashika worked on integrating the storytelling program with the audio input/output on laptops. Abha started building a cardboard prototype of the robot frame and started working on the eye displays. Risk Management As we mentioned in our statement of work,