This week, I mostly worked on getting the socket.io library to work with the webapp and preparing for the Design Review. While the sockets are not completely functional at the moment, I am hoping to get it working by early next week, and then working on SerialPort for the remainder of the week.
Group status update for 10/10
Current risks:
- Unforeseen delays due to the state of the world right now (re:pandemic) and due to us all being apart from each other have caused some shifts in the order we tackle the tasks we scheduled out, and there may be other delays to come that we cannot predict. We’re managing this by making better efforts to stay coordinated and in-sync as a team, so that if something happens to one of us, we can quickly adjust the project in response.
Changes:
- We’ve switched from the actuator we initially were going to procure to a cheaper one. This one does not come assembled, so that is added time spent on the project, but it should be simple to build and saves us around $200. This actuator, however, has a smaller travel distance, and will result in a smaller board. As a result, the pieces will have to be made smaller than usual chess pieces, but having normal-sized pieces was a preference we had, not a strict requirement. We chose to have more freedom and flexibility in our budget over having bigger pieces.
Brandon’s Status Update for 10/10
This week, I learned how to use node js and express, including using libraries with them. I was able to use chessjs and chessboardjs to make a working chess game which also prints information about the game’s status as shown at the bottom, so I am on track of schedule. I hope to get the game working with sockets for next week.
Group Status Report for 10/3
Current risks:
- The current risk is we have taken a bit long to acquire parts, and are now a bit behind schedule. We are managing this by doing the things we can do without those parts ahead of time, this way we’ll still be on schedule.
Changes:
- We have had to change the specific actuators we were planning on using because of the costs, although it has taken time away from us in the form of extra research. Going forward we’ll keep this lesson and mind and research something thoroughly before deciding on it.
No changes to the schedule have been necessary.
Brandon’s Status Update for 10/3
This week, I worked on creating design documents ( Object Diagram, Class Diagram) and delved deeper into which web app framework to use: node.js express. By next week, I hope to have a local web app where the user can play a game of chess (controlling both colors).