Month: April 2019

This week, I was a bit thrown off by losing Sunday night and all of Monday to a surprise ER trip.  Thankfully, nothing serious came of it, and I spent time making more of the squares I need to make for the game board.  It is a purely time intensive process, so I have been working on clearing out schedule time and suspending non-essential activities to make sure I can make enough to have the board up by the end of the week.  In addition, I have begun working on the code for the lights, and spent some time working with a smaller led strip I already owned after the booth opened during carnival. I am thankfully done with all my non-capstone obligations for the semester, and will be working much more this upcoming week to catch up.

See https://github.com/dhanna11/capstone.

Currently there’s not much to be done on my end.
I have the GUI and basic single player working, with multiplayer simply being a subset of the single player code.

At this point, we need to integrate our code with our hardware. It doesn’t make sense for me to add anymore complexity to our code until we have a basic board up and running.

I’ll see how I can help with making the board in the upcoming week. In the meantime, I’ve been reviewing my UML, and will be documenting our code for the final report.

 

This week, I helped Chris with getting the mux logic working and started making squares for the chess board.  After some initial error, I figured out an effective system for making the squares and settled in and cranked out a couple.  My speed in making them has increased pretty quickly over the course of the ones I’ve made, and I’m optimistic I can keep cranking them out at a good pace over the course of next week and especially the week after, when I won’t be building booth as well.  Separately, I have been reading the Colwell readings and will have the section finished and summarized by tomorrow night.

My work is currently located at git@github.com:dhanna11/capstone.git.

Currently I have a skeleton gui running that repsonds to a selected move, run’s a stockfish analysis and responds with a move.

See commit messages and readme for more. I’ll post a more extensive update tomorrow morning.

Risks

The biggest risk is the software. David is a little more behind schedule than we thought, and it will take time for him to translate his ideas into code. Chris has been helping David prioritize his tasks so that we can have some tasks accomplished by the end of the weekend. These include finishing a basic gui, and getting the basic game logic as move validation working. We are working hard to make sure that the software gets completed on time, but the lack of progress on the software side is definitely the main risk to the project.

Changes to System

None.

Changes to Schedule

We are behind schedule mostly due to software. We were supposed to begin testing of the software this week, but that will have to be pushed back.

Personal Progress

I was able to get the pi to sweep across several sensors with a mux for the demo. Professor Mai asked us to figure out how fast the pi can sweep through the sensors so I will work on that next week. We did encounter some inconsistency in how the mux worked during testing before the demo. Sometimes it would work and other times it would just read garbage from the sensor. I will try to solve this problem by figuring out how fast the pi can read from the sensors and make sure that we are giving the system enough time to switch between inputs and read correct values so that we don’t run into this issue in the future.

We ordered the 7 segment display and a new pi, so I will also being working on the smart clock and connecting the other pi for remote play as well.

Schedule

I was hoping to start looking at connecting the two pi’s right now but as long as I start next week, we will be able to stay on track.

Deliverable

I hope to have the time measurements for reading from the sensor done by next week. I also hope to have the code from reading from the full array of sensors done because I only wrote code for the smaller array of sensors for the demo. I will also start looking at the smart clock and connecting the two pi’s.