Posted on

Sherry’s status report for 12/09

This week we wrapped up the final presentation and our integration with different components of the system. the integration went relatively smoothly for my software component with the raspberry pi part. The entire system seems to able to come together and function properly.

We still need to do more testing with playing the keys on the keyboard and monitoring the final sheet music generated on my end, which we have yet to complete.

After contacting Tom Sullivan, we made some pivot in my part to transition into generate the sheet music at the end instead of real time, as there is no point in trying to generate the score as someone is playing something they already have in mind. I am doing some connections between my original code with the new interface that we decided to use.

I also realized that my original implementation of the algorithm does not take into account of the fact that there could be rests in music. This is quite important as notes are not necessarily continuously out in a piece, and there is inevitable some rests in the music. So I am modifying my algorithm to take that into account.

Posted on

Olek’s Status Report for 12/2

This week I made a lot of progress with the Raspberry Pi communicating with the PCB. Now that we have all the project components, the Pi is able to communicate very well with the PCB, and able to access all the sensor channels very quickly. What I plan on doing this week is incorporating a PWM output signal from the Pi to the buzzer on the PCB to give the user auditory feedback on the metronome tempo. Apart from that, I plan on helping my teammates with their tasks to make sure we finish the final project on time for the demo.

Posted on

Olek’s Status Report for 11/25

I’m not sure if a report is due for this week. I wanted to post one to make up for the ones I missed while I was away. This week I spent working on the raspberry pi code. I am still waiting on the PCB, so I fully fleshed out the code needed to talk with the local software on the computer. All that we need now is the PCB to correctly converse with my i2c code, and my project portion of the mvp should be met.

Posted on

Team Status report for 11/18

This week we made progress around the board towards our MVP. The PCB has been ordered and should arrive sometime early next week. Furthermore, the raspberry pi/pcb interface has been modeled using an Arduino in order to support further development while the pcb is being delivered. This allowed us to find that the i2c libraries available on the raspberry pi won’t meet the standard that we need to communicate with the PCB, so a standalone library is being written. Lastly,  we found where we needed to inject code into the Muscore library in order to visualize the notes, progress should be made this week.

Posted on

Team Status Report for 11/11

This week, we reached a crucial milestone by conducting and presenting our interim demo sessions on both Tuesday and Thursday. These demonstrations provided an opportunity to showcase our progress, receive constructive feedback, and refine our project’s direction. We are actively fostering collaboration through our regular group meetings, where we discuss collective project goals and address any challenges. Simultaneously, team members are dedicating focused efforts towards individual tasks, ensuring a comprehensive approach to our objectives.

Our primary focus remains aligned with our original design objectives, driving us to achieve a functional minimum viable product within the set timeline for the upcoming showcase. This overarching goal guides our daily endeavors, emphasizing the importance of meeting our milestones to ensure a successful presentation at the showcase. Overall, the team is committed to maintaining a steady rhythm of group discussions and individual work, keeping us on track to meet our project goals in a timely and efficient manner.