Posted on

ruizhezh’s Status Report for 02/19

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). 

The week is mostly comprised of prototyping work to help with the design doc;

I want to ensure that the basic design is feasible, and have tested multiple modules in simulated circumstances to ensure that they will work as expected; 

  • Raspberry Pi Configuration; 
    • Installed operating system (resolved multiple issues); 
    • Configured system applications, python, OCR framework, openCV, etc; 
    • Configured testing framework for openCV license plate recognition; 
    • => Handed over to Xu Ke for openCV workloads; 
  • Went to CMU parking garage to further specify design with field information;
    • Filmed a test run clip to test openCV recognition; 
  • Initial deployment of AWS Restful API framework for the project; 
    • Wrote RESTFUL API prototype (placeholders); 
    • Deployed on AWS ec2 instance and tested with Postman client; 

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

I am ahead of schedule for this week due to the AWS API initial deployment taking less time than expected; 

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

I am expecting to finish: 

  • constructing a fully usable Raspberry Pi portable testing station (with screens, keyboard, etc); 
  • finish AWS configuration and most parts of the API specification (design) and some implementation;

I am planning to test: 

  • request sending on Raspberry PI to AWS server and test round-trip-time; 

 

Gathering test videos for license plate recognition in east parking garage

[image-failed-to-process]

Testing AWS Restful API prototype

[image-failed-to-process]

[image-failed-to-process]

Posted on

Team Status Report for 02/12

What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?

  • Due to multiple significant changes in our proposal and abstract, we are already behind schedule for a whole week. We are working longer hours to compensate for the lost time. No contingency plans is necessary.
  • Our initial designs and implementation plans overran the $600 budget rather significantly, requiring multiple raspberry Pis (at least 3 with additional needed for each intersection); We are thinking about paying for the project out of pocket, or/and borrowing equipment from friends for the duration of the course;

 

Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc)? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?

We have changed our project idea twice in the last week due to failure to satisfy the course faculty, with the final project idea finally getting approved; The changes caused a significantly delayed schedule and all work being diverted to coming up with a new project idea instead of working on designing the current project.

Since the project idea is now approved, we should not see this kind of issue going forward.

 

Provide an updated schedule if changes have occurred.

Due to the recent changes in the project, we are still coming up with a new schedule for the current project. A update will be posted soon.

Timeline

  • Presented our initial proposal of “Attacking STOP signs with OpenCV and ML adversary model”;
  • Proposal refused by Professor Kim and Professor Tamal due to ambiguities in idea and execution;
  • Tried to come up with revisions to the “Attacking STOP signs with OpenCV and ML adversary model”, with no progress made in several hours;
  • Discussed and tried to come up with a more adequately defined and scoped new proposal — “Smart Parking System with Monitoring and Metering”;
  • Wrote new abstract and presentation slides for the new proposal;
  • Presented idea to Professor Kim again;
  • Took advice from Professor and revised proposal to include new features (“automated parking guidance”);
  • Presented idea to Professor Kim again;
  • Proposal approved;
  • Started to work on design details and implementations of the proposal;
  • Pending work on schedule and work division (blocked on implementation detail discussion);

 

 

Posted on

ruizhezh’s Status Report for 02/12

My progress for this week comprises presenting our initial idea of “Attacking STOP signs with OpenCV and ML adversary model” with group C5, meeting with Professor Kim multiple times to discuss and finalize the direction and scope of the project, meeting with the team multiple times to brainstorm new project ideas, and taking part in writing and revising the abstract and proposal presentation; 

I and our team is behind schedule due to the recent and complete change of our project, which necessitated a lot of discussions between teammates and with faculty, rewriting the abstract and proposal slides, and reworking the schedule; I and my team are already working very long hours (way exceed 12 hours) to try to catch up with the schedule again;

I am hoping to complete the new project schedule, design details of the “automated parking guidance” systems, and a list of needed items in the next week.

The timeline of events include: 

  • Presented our initial proposal of “Attacking STOP signs with OpenCV and ML adversary model” with group C5;
  • Proposal refused by Professor Kim and Tamal due to ambiguities in idea and execution;
  • Tried to come up with revisions to the “Attacking STOP signs with OpenCV and ML adversary model” with Ke and Grace, with no progress made in several hours;
  • Discussed with teammates and tried to come up with a more adequately defined and scoped new proposal — “Smart Parking System with Monitoring and Metering”;
  • Wrote new abstract and presentation slides for the new proposal;
  • Presented idea to Professor Kim again;
  • Took advice from Professor and revised proposal to include new features (“automated parking guidance”);
  • Presented idea to Professor Kim again;
  • Proposal approved;
  • Started to work on design details and implementations of the proposal;