Weekly Status Reports

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 

Abha’s Status Update for May 2

Abha’s Status Update for May 2

This week, I worked on collecting data for story cohesion and user satisfaction. I had my family members fill in templated stories and then gave them to Ashika, who used them to determine story cohesion relative to random stories and the original Aesop’s fables. I 

Team Status Update for May 2

Team Status Update for May 2

This week we worked on finalizing our presentation which Ashika presented on Monday.

In the middle of the week we all worked on updating our design report to reflect changes in the design and descriptions of our final project. At the end of the week we planned out what we wanted in our demo videos and we each recorded  segments about our portion of the design. Ashika will be combining our demo videos to create our final video.

There are no new significant risks this week and no changes made to the existing design.

For this upcoming week we plan on finishing our demo video and paper.

Jade’s Status Update for May 2

Jade’s Status Update for May 2

This week I worked on getting audio latency metrics for our presentation on Monday as well as working on updating our paper and recording segments for our final demo video. On Sunday I realized I had to remeasure system latency because I realized that because 

Abha’s Status Update for April 25

Abha’s Status Update for April 25

This week, I mostly worked on assembling the robot. I also helped Jade collect data for speech recognition accuracy. First, I assembled the head and body of the robot. I put all of the electronics inside them and made sure everything still worked. One minor 

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 speech tagging done on user inputs. The script also measures latency, so I can easily use it to show how the tradeoffs between different combinations of taggers and justify why I chose the one I did. I wrote a similar script for synonym fetching. With the new design, there is no longer a need to measure accuracy because my previous criteria for a synonym being accurate was whether the generated word showed up in the thesaurus. Now, I am fetching the words straight from a thesaurus. Checking for synonym accuracy against a global standard is a little tricky because it is hard to quantify how accurate a synonym is. However, there are subjective advantages to choosing one method over another, and a tradeoff with latency shown with my python script, which I included in the final presentation.

I also worked on measuring story cohesion. I got user generated stories from the family and friends of Jade and Abha and I asked my family to grade the generated stories, the original stories, and pseudorandom stories in a blind study. Besides who was is doing these tasks, this plan did not change from the design report. Apart from all this testing, I also fixed a few minor bugs and prepared and worked on the final presentation (since I will be presenting).

I am still on schedule. There is not much left to do now besides the final report, which I will work on all of next week.

Jade’s Status Report for Apr 25

Jade’s Status Report for Apr 25

On Monday I just tested our code before the demo we had and participated in the demo. On Wednesday I wrote testing code to measure speech recognition accuracy. The code pulled random words from the thousand most common English words and then prompted the user 

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 

Abha’s Status Update for April 18

Abha’s Status Update for April 18

On Monday, I set up the face display and got code working on it to draw shapes and lines. This was a precursor so that I could debug issues with drawing shapes on a canvas before creating the actual face.

On Wednesday, I worked with Jade and Ashika to integrate Jade’s socket code with the Pi and hardware on my side, and debug issues we had with integrating it with the hardware. The socket code is used to transmit information between my laptop and the Pi.

On Friday, I worked with Ashika to integrate her code to bold text that are generated by KATbot (and not the template), and debug hardware issues with it, such as markup issues and testing to determine which sizes of canvas and text are appropriate for our displays.

On Saturday, I returned to the face display and worked on drawing the face. This is time consuming because there is a lot of experimentation involved with figuring out the desired size and which pixels to use for them.

In the upcoming week, I plan to finish the face display and assemble everything into the physical robot to finish the MVP. If I have time after that, I will work on the robot showing sentiment, but since that is outside of the MVP, it is not a focus right now.

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