Author: ryg500

Ryan’s Status Report for 10/1/2022

While the majority of this week was spent drafting up slides for the design presentation, I was able to spend some time designing and testing the latency for notation.

Fortunately, since the legality checker is done in C++, that section’s latency requirements were easily satisfied. On the other hand, while python is a much slower, interpreted language, the latency requirements for uploading to the website are much more lax, and as a result, the python string parsing and upload times still fit within the 2 second window outlined at the beginning. The only latency left is the

Unfortunately, I have fallen a little behind with some of the basic website work and want to catch up next week. I spent much of this week sick with an unbearable sore throat and cough. I am only now getting better and should be able to attend class, participate in team meetings, and contribute more actively. My next week is much more free and will allow me to make significant progress catching up to the work that my teammates have done.

Next week, I want to finalize the frontend of the website, and be able to add new games, delete old games, and upload chess moves (notation to the website). I also will be communicating actively with Patrick to work out some of the interfaces that my code has with his legality checker.

Team Status Report for 9/24

Overall, the majority of this week was centered on creating, editing, and designing the proposal presentation. The remaining time this week centered on basic setup. Patrick and Vikram worked to create a smaller buy list from a variety of magnet options (and started looking into various PCB’s for the board itself). Ryan started some basic library and tooling work on the software side.

The biggest risk that our current project currently faces are potential issues with part supply. We are attempting to combat this by ordering from reputable vendors, ordering extra product (Ex. 70 magnets instead of 64 incase of broken or faulty magnets), and finally carefully placing the order (this is to ensure that our team is able to retrieve the correct magnets on the first order rather than having to wait for subsequent orders).

All in all, while our team might not have incurred substantive physical process, we were able to prepare ourselves to make more efficient project in the following weeks (library tooling, shopping list… etc.). Be prepared for more to come!

Ryan’s Status Report for 9/24

While the bulk of this week was spent working on project presentations, I was able to make some progress on creating object oriented classes to model the chess board. I was able to set up our Github and will work on integrating it with Vikram and Patrick as we move into the next week.

While it may feel that substantive work was not completed, we are still completely on schedule. Our schedule allotted time during the earlier weeks of the semester to account for the proposal and design presentations (and therefore had a lighter workload) as well as waiting for parts to ship, while delaying much of the heavier workload into the latter half of the semester so that progress could be accomplished more efficiently. That is to say that I, as well as our team, am still on schedule.

Furthermore, next week, I will focus on creating some baseline libraries that will streamline the process of determining whether Python is an optimal tool (in latency terms) for the website backend. This will help achieve the deliverable of creating object oriented classes (our first software deliverable) as well as accomplish small setup tasks that will help Patrick and I write better software to accompany Vikrams hardware. Next week we plan to discuss the best tasks for Vikram and Patrick as we wait for our parts to arrive.