Sam Adams’s Status Report 4/18/20

What did you personally accomplish this week on the project?

My team and I worked on wrapping up the implementation of our simulation for our demo on Wednesday. We first worked by defining an API so we could each work separately and still make progress. I then finished up the UDP simulator.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

My progress is a little bit behind schedule. Even though I have the simulator finished for the demo on Wednesday I still need to add some meters in order to measure performance of the protocol. We also need to start thinking as a group how our presentation will be organized.

What deliverables do you hope to complete in the next week?

Next week we are going to wrap up the coding portion of this assignment for our demo on Wednesday. I also want to get started on the final presentation.

John Paul Harriman’s Status Report for 4/18/2020

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I rewrote a lot of the existing code I had to be more easily integratabtle into our current GUI solution with an Object oriented approach to create our Test Suite where we will be displaying the graphical information, the data being generated, and the functions working. I can show the packets that I’ve generated, but I’m still trying to figure out a good way to display the information to the viewer that isn’t just a million bits at a time. I’ve worked with the team to hammering out our system construction so all that’s left is just throwing more algorithms at our test suite, displaying information, and continual integration with the team.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Project seems to be on schedule for once, just need to stay on top of things before the demo.
What deliverables do you hope to complete in the next week?

More algorithms and proper benchmarkings, I know the number of packets generated in one second, which highly exceeds current expectations for timeouts, but want exact numbers.

Team Update 4/18/20

What are the most significant risks that could jeopardize the success of the project?
The most significant risks right now are not fully debugging the GUI, leading to an unexpected error; at the moment, the core error detection and correction algorithms are solidified, so the GUI may need to go through more rigorous testing.  Additionally, since the UDP protocol implementation is much different than the serial and bit streaming protocol implementation, a potential issue may be integrating the UDP protocol with the GUI taking longer than expected.
How are these risks being managed? What contingency plans are ready?
The risks are being managed by making the components between the GUI and algorithms as clean as possible; we’ve created an easy to use class that wraps around the protocols, making integration and debugging as simple as possible.  The contingency plan for not integrating protocols with the existing set up is creating a separate GUI/method of simulating those results.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)?
Nope- we’re still on track with the current design that we have and so far the implementations are working as expected.
Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

We were deciding between a dynamic approach like JP’s graph demo and a non-dynamic/on-click approach like Mia’s approach using a console to display data; we’ve decided to go with a dynamic approach, since it more accurately simulates the accuracy rate during serial data transmission and was easy to make the bit streaming algorithms dynamic.  Rather than simulating one transmission of data by clicking the button, clicking the button will only change the protocol currently being simulating, while the actual transmissions are continuously going + results are constantly being graphed and displayed.

Provide an updated schedule if changes have occurred.
The schedule has not changed.

Mia Han’s Status Report 4/18/20

What did you personally accomplish this week on the project?

We met a few times this week to discuss who would be responsible for the remaining tasks and how to begin integrating each other’s work.  I felt that it was best for me to integrate the graph with the GUI, while JP worked on writing a nice wrapper class to encapsulate the protocols and make calling each protocol from the GUI a lot easier and neater.

I integrated the line plot graph with the GUI; now, the results from each iteration of the protocol is plotted in the graph in real-time (thus, the graph from JP’s demo and the GUI from my demo are in one nice GUI!).  Additionally, I’ve finished implementing and integrating Reed Solomon simulation.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

I feel that our progress is on schedule; we spent a good amount of time ensuring that any protocol can be easily integrated with the GUI, and I’m satisfied with those results.  Additionally, since the integration is mostly completely, I feel that we can focus more on creating more types of encoding and decoding schemes.  I’m a little worried about the UDP integration with the GUI putting us behind schedule, since that is so different than the current serial/bit stream implementations that we’ve currently integrated.

What deliverables do you hope to complete in the next week?

I hope to (in order of priority):

  1. Ensure that there are no bugs in the GUI- right now, we are getting a few bugs every now and then.  Additionally, I would like to clean up the GUI by adding more console messages and figuring out if it is possible for the graph to be updated more quickly.
  2. Implement more error detection and correction protocols that we previously discussed in our project re-design.

John Paul Harriman’s Status Report for 4/11/20

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I worked more on getting the demo ready and then on the concerns post-demo. I was able to display the information in real time of the exact rate of successful packets recovered, but was suggested that I should also be able to see the data that is being fixed. I had some concerns about doing this since I am doing around 1000+ packets per second and could overwhelm the user, but I think I have thought of a way of displaying this information. My work now has been trying to show the fixed and unfixed packets side by side as a stream into a window clickable by the user. I also worked on further research on forward error correcting codes.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

In terms of my personal schedule I’m a little behind because I wanted more integration to be done, but will need cooperation with the entire team to accomplish that. Just in general I need to put in a lot more of these correcting algorithms since I’ve figured out the system construction.
What deliverables do you hope to complete in the next week?

Deliverables are integration of API into GUI, more algorithms, and benchmarking the algorithms that we do have. (Same as last week)

Team Update 4/11/2020

What are the most significant risks that could jeopardize the success of the project?
The most significant risks at the moment was the lack of communication between team members; right now, we’ve been working on our components individually, making integration a bigger task than it should have been.  Achieving cohesion by combing all of our implementations into a GUI is the biggest priority right now.
How are these risks being managed? What contingency plans are ready?
The risks are being managed by setting up a bunch of meetings to discuss how each other’s implementations of the protocol work to ensure quicker understanding of each other’s code.  Additionally, we are making sure that our code is clean and well-documented so that it’s easier for each other to understand how we’ve implemented the algorithms.
Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)?
Nope- we’re still on track with the current design that we have and so far the implementations are working as expected.
Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

We’ve not made any changes this week!

Provide an updated schedule if changes have occurred.
The schedule has not changed.

Mia Han’s Status Report for 4/11/20

What did you personally accomplish this week on the project?

I’ve been working on refining the prototype demo-ed on Wednesday by further testing my program and debugging it from minor issues.  Additionally, I’ve been working on implementing other algorithms like Reed-Solomon and integrating the Hamming Codes + graph and UDP protocols.  I also did my reading for next Wednesday’s discussion this week!

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

I feel that our progress is slightly behind; I would like to further along with the integration, but I feel that putting in a few more hours this week will put us in a good spot.

What deliverables do you hope to complete in the next week?

I hope to (in order of priority):

  1. Integrate the hamming codes implementation + UDP protocol with the GUI and integrate the graph feature
  2. Finish debugging and refining GUI

Sam Adams’s Status Report for 4/11/20

What did you personally accomplish this week on the project?

I finished up the code required for the demo of our project on Wednesday. I also worked with my team to discuss how we are going to integrate all of our protocols together along with the GUI.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Our progress seems to be on schedule with regard to the demo we gave on Wednesday. We still however have a lot to do in order to make sure that all of our parts of the project fit together in a deliverable form.

What deliverables do you hope to complete in the next week?

I hope to finish the integration of my protocol with the GUI. I also want to make myself available to work on other parts of the project if needed.

John Paul Harriman’s Status Report for 4/4/2020

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

I implemented most of the base calls for the API and implemented the algorithm for hamming encoding/decoding.

Here is a link to the current files of implementation: Here

These files aren’t up to production documentation, but that is more of back-burner problem right now.

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

I think that we are on schedule, but still have a lot of work to do. The main thing that will potentially bring us down is the ethics reading, demo, video, and final report. These are all projects that take significant amounts of time to get ready and can take away from what we are doing in terms of coding. This is why I will suggest that we crunch after the demo so that we can get everything in on time.
What deliverables do you hope to complete in the next week?

Deliverables are integration of API into GUI, more algorithms, and benchmarking the algorithms that we do have.

Sam Adams’s Status Report for 4/4/20

What did you personally accomplish this week on the project?

I worked on writing the code for the wifi simulator for our demo on Wednesday. My group also met a couple of times this week to discuss the APIs that we would be using in between the different protocols. This made it easier for us to integrate our code together after we finish writing our individual parts

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

Our progress seems to be on schedule as of now. We are in a very good place right now with the demo coming up in the next week.

What deliverables do you hope to complete in the next week?

I hope to finish up the coding for our demo on Wednesday. I also hope to start working on the integration and the analysis section of our project after the demo.