{"id":81,"date":"2023-02-19T04:32:50","date_gmt":"2023-02-19T04:32:50","guid":{"rendered":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/?p=81"},"modified":"2023-02-20T15:24:12","modified_gmt":"2023-02-20T15:24:12","slug":"parths-status-report-2-18","status":"publish","type":"post","link":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/2023\/02\/19\/parths-status-report-2-18\/","title":{"rendered":"Parth’s Status Report (2\/18)"},"content":{"rendered":"

Parth\u2019s Status Report for Feb 18<\/span><\/h1>\n

Personal Accomplishments<\/span><\/h2>\n

Most of my work this week was aimed towards consolidating the data for the UI and implementing a MVC design that is compatible with the inputs and outputs for each subsystem. This week involved a lot of work as a team, wherein, we made some significant design decisions that were backed with proof of concepts and metrics. To that end, my first objective was to find a way to remove our dependency on the QLC+ API because of latency issues. We tried using PyDMXControl to directly interface with the lights using Python, however, we ran into backend issues. To resolve this, I found another python library DmxPy, using which, we were able to control the lights directly, as shown in the media under the team\u2019s status update.\u00a0<\/span><\/p>\n

 <\/p>\n

I was able to make significant progress in the Lights OOP and how it would scale to allow for the integration of multiple lights. I also contributed to the development of criteria for the signal decomposition. We determined 8 characteristics and features we will be using to divide and process the audio. Further, I made design decisions about combining the outputs from the signal processor and the genre classifier to adjust the lighting logic. Finally, a major part of my efforts were directed towards creating the design proposal slide deck and consolidating our development plans.<\/span><\/p>\n

On Track?<\/span><\/h2>\n

According to the team schedule my only goal for this week was to get started on the UI, but I ended up accomplishing a lot more. I started working on a basic web application that will be done by the end of next week. Further, as a team, we made progress on multiple subsystems, giving us a better understanding of everything that needs to be accomplished. As mentioned in the previous status report, I was able to accomplish the goals I had set out for myself earlier. I was able to bypass the QLC requirement without the use of a RaspberryPi as I had initially hypothesized.\u00a0<\/span><\/p>\n

 <\/p>\n

Overall, I was able to maintain my headstart from last week, finishing tasks that we anticipated would not get done for a while. I want to continue developing my subsystems in a way that are consistent with the rest of the systems, so that we can shave time off for integration. Further, I want to develop in a manner that provides flexibility for change and accommodates the team\u2019s needs.<\/span><\/p>\n

Goals for Next Week<\/span><\/h2>\n

My critical goal for next week is to finish the development of a UI that allows the user to enter audio and then communicate with the other subsystems. If I am able to take in inputs from the subsystems and create outputs as hypothesized in our design, I will move on to integrating it with the light engine so that we are able to produce a deliverable that can be tested on. Further, I will be helping Abhishek with the lighting engine, taking the UI outputs to determine the lighting logic and queue.<\/span><\/p>\n

 <\/p>\n

Classes that helped:<\/p>\n

17-437 Webapps – Used this to create the MVC design for the interface and deploy the UI
\n18-213\/18-290 – Used these courses to define the metrics for the software and the signal decomposition
\n15-112 – Used this to design the light sets using OOP<\/p>\n","protected":false},"excerpt":{"rendered":"

Parth\u2019s Status Report for Feb 18 Personal Accomplishments Most of my work this week was aimed towards consolidating the data for the UI and implementing a MVC design that is compatible with the inputs and outputs for each subsystem. This week involved a lot of work as a team, wherein, we made some significant design […]<\/p>\n","protected":false},"author":653,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[6,3],"tags":[],"_links":{"self":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/posts\/81"}],"collection":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/users\/653"}],"replies":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/comments?post=81"}],"version-history":[{"count":2,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/posts\/81\/revisions"}],"predecessor-version":[{"id":90,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/posts\/81\/revisions\/90"}],"wp:attachment":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/media?parent=81"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/categories?post=81"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd4\/wp-json\/wp\/v2\/tags?post=81"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}