{"id":143,"date":"2023-03-11T19:39:35","date_gmt":"2023-03-11T20:39:35","guid":{"rendered":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/?p=143"},"modified":"2023-03-11T19:41:24","modified_gmt":"2023-03-11T20:41:24","slug":"lisa-xiongs-status-report-for-3-11-2023","status":"publish","type":"post","link":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/2023\/03\/11\/lisa-xiongs-status-report-for-3-11-2023\/","title":{"rendered":"Lisa Xiong\u2019s Status Report For 3\/11\/2023"},"content":{"rendered":"
Personal Accomplishments<\/b><\/h5>\n

The problem in my NLP system I tried to solve since the last status report is the parsing of menu items with multiple words, as I realized that the dependency parser does not support parsing multiple words as a single token identity. The first solution I came up with was to add all menu items into a list of named entities, so that the NER pipeline can recognize them. However, the menu items could not be considered as named entities in spaCy even when I tried to capitalize the initial letters. Token matching could work, but a lot of flexibility will be compromised when handling varied sentence structures, since the token matcher needs more rigid rules than the dependency matcher. I solved the problem by defining a new set of dependency matching rules for menu items with multiple words. For example, for the menu items \u201cveggie burger\u201d and \u201cchicken burger\u201d, this pattern will use \u201cburger\u201d as the anchor token and find its immediate adjective dependent (either \u201cveggie\u201d or \u201cchicken\u201d) and the quantifier dependent (number or determiner).<\/span><\/p>\n

\"\"<\/p>\n

The following command line output shows the natural language processing system\u2019s input and output.<\/span><\/p>\n

\"\"<\/p>\n

For changing item entries, the current solution is to find a set of keywords indicating the change (\u201cremove\u201d, \u201cdelete\u201d, \u201cadd\u201d, \u201cchange\u201d), which should be the immediate head of the menu item token, and change the order information accordingly. The actual ordering situations will be more complex than this scenario, and we plan to fix it after having a functioning system that reaches MVP.<\/span><\/p>\n

Schedule<\/b><\/h5>\n

I have caught up with the schedule for NLP system programming: a MVP version of the algorithm can be completed by Monday March 13 the latest. Nina and I have not started integrating the database and the NLP system yet; the schedule change is mentioned in the team status report for this week. We did coordinate on what type of data structure the NLP system should return so that the information can feed directly into the database, and I believe the integration should not take long since we already have compatible data structures.<\/span><\/p>\n

Plans for Next Week<\/b><\/h5>\n

I plan to work with Nina to integrate my NLP system with the database next week. I will also start working on programming the speech recognition system.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Personal Accomplishments The problem in my NLP system I tried to solve since the last status report is the parsing of menu items with multiple words, as I realized that the dependency parser does not support parsing multiple words as a single token identity. The first solution I came up with was to add all … Continue reading “Lisa Xiong\u2019s Status Report For 3\/11\/2023”<\/span><\/a><\/p>\n","protected":false},"author":688,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[8],"tags":[],"_links":{"self":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/143"}],"collection":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/users\/688"}],"replies":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/comments?post=143"}],"version-history":[{"count":2,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/143\/revisions"}],"predecessor-version":[{"id":147,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/143\/revisions\/147"}],"wp:attachment":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/media?parent=143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/categories?post=143"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/tags?post=143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}