Friday, January 13, 2017

Week 1

Jacky Chen


Current Week Objectives: Learn about IBM Watson services
Current Week Accomplishments/Hours Worked:


Day 1 - 1/9/17 | 8:30AM-2PM


The challenge for today is to fix a 3D Printer. The printer was missing a few parts and could not fully function.






Day 2 - 1/10/17 | 10:30AM-2PM

Followed Professor Joe to his 440W class and helped students with setting up Github accounts and made sure everyone in the class was in the right repository.


Day 3 - 1/11/17 | 9AM-2PM


Finished fixing the 3D Printer and made sure it was working before giving it back. Printed out a 3D spool holder for testing. Tested out IBM Bluemix applications, how their API works and tried to create an app. I am still learning how to use IBM Bluemix for future references since Joe’s class is going to be using it.


Day 4 - 1/12/17 | none


Day 5 - 1/13/17 | 9AM-3PM


Today I worked on IBM Watson Conversation and figured out how to create a conversation between the user and Watson. I had to create intents, entities, and a dialog in order for this to work. Intents is basically the purpose of the conversation and what you want it to talk about. Entities are like nouns that Watson can find in conversations and figure out what the user is asking. Dialog is where all the conversations happen. This is where I had to create the conversation and replies to the user and how it interacts. 



Week one total = 22 Hours


Next Week Objectives: I want to learn new kinds of database like mongoDB, Progress, Cassandra, and MySQL.  


Key Lessons Learned/New Skills Acquired: I learned how to replace/add parts to a 3D Printer, and learned some key features of IBM watson services. I have knowledge of IBM’s cloud services on watson. Some services I tried to work with are, text to speech, speech to text, and conversation.


Issues and Concerns: Some issues I had was with IBM cloud services. This was my first time using IBM services to build an app on the cloud server, so I did not understand how this was supposed to be done on IBM.

No comments:

Post a Comment