Kylee Status Report 4/25/20

  • Fixed bugs for demo
    • Projected vehicles from other track onto current track in order to prevent intersection collisions
    • Defined a max acceleration based on velocity difference and distance between current vehicle and next vehicle
  • Prepared results and analyzed in Excel
  • Made slides for final presentation
  • Added test cases for more extensive results
  • Wrote simulation testing program that removed graphics so tests could run much faster
    • Internal program time was decoupled from system time

Kylee Status Report 4/18/20

  • Fix bug in car following chain model
  • Fix bug for vehicles in both tracks in the intersection
  • Refine testing code for final demo
    • start/stop, display detection radius in testing mode, etc.
  • Determine what measurements would be good to display/record
  • Run tests to get results and compare measurements
  • Experiment with different sized cars

Kylee Status Report 4/11/20

  • Refine car following model for cooperative approach
  • Implement input and output files to codebase for ease of testing
  • Refactored the existing code to include running the inputted testbench and saving the outputs
  • Created test cases and ran tests to analyze results
  • Fixed some bugs in the planning and Intelligent Driver Model code
  • Help to identify and fix timing with simulation graphics
    • Use time elapsed between function calls to determine distance traveled by vehicles (distance = rate * time) to standardize the movement of cars
    • Makes the movement independent of what other tasks the CPU is running or how fast the CPU can execute the code

Kylee Status Report 4/4/20

  • Fine tuned real world parameters for Intelligent Driver Model
  • Modified Intelligent Driver Model code to include the intersection as an “obstacle” if vehicle does not have the right of way
  • Cleaned up codebase in all files
  • Integrated with path planning code
  • Refine graphics and planning to get the code demo-ready
  • TODO: Work on lane changing model for two lane implementation
    • Reason for implementing two lanes included in team status report

Kylee Status Report 3/28/20

  • Decided on reasonable real world parameters based on papers read
  • Implemented the Intelligent Driver Model using these parameters
  • Analyzed the graphics and created a scale to convert pixels to meters
  • Cleaned up, modularized, and corrected graphics and vehicle code in existing codebase
  • Integrated the planning code with the graphics and vehicle code and tested
  • Worked on Risk Management Plan and updated Gantt Chart

Kylee Status Report 3/21

  • Planned for added complexities for our repurposed project
  • Wrote the Statement of Work
  • Participated in 3 meetings with the group to discuss project
  • Helped design the graphics code (ie. modularize, integrate with path planning, etc.)
  • Continued to research non-cooperative path planning
    • Ie. Trying to relate the purely simulated data such as pixels and angles with the equations that use real world measurements like meters per second.
  • TODO next week:
    • Start to implement simple planning code that stops when obstacle is sensed.

Kylee Status Report 2/29/20

  • Progress
    • Prepared design presentation slides
    • Tested metrics for vehicles, detection latencies, communication latencies, and some computation latencies
    • Practiced design presentation slides, presentation, potential questions
    • Started codebase for detection and path planning integration
    • Created classes for vehicle and track info
    • Worked on design report
  • TODO
    • Implement scheduling algorithm to ensure fairness
      • Just going to be keeping a counter for how long car is waiting without progress. System will choose the vehicle that has been waiting the longest to pass through the center lane
    • Test vehicles to correlate numerical values that we use to program the motors with actual speeds in cm/sec

Kylee Status Update for 2/22

  • Collaborated with team to find alternatives and solutions for NodeMCU struggles. Settled on buying the boards from another manufacturer and that seemed to work.
  • Created a metrics document for the driver model
    • This related the vehicle speeds and the various distances the vehicle would travel in case it needed to come to a stop
  • Used the metrics to determine the size of our track
    • # of cars * (Total following distance between cars + Length of cars) = Circumference of one track
  • Performed tests with the vehicles in order to determine max vehicle speed and also a stopping distance
  • Worked on design review presentation slides
  • Slightly behind schedule with regards to the path planning algorithms. The major roadblock with the NodeMCUs and the construction of our vehicles was necessary to overcome in lieu of the design presentation (needed numbers for our presentation)
  • TODOs:
    • Need to do more research and start the codebase for the path planning
    • Non-cooperative case does not seem too challenging, but need to find a good solution for the cooperative case.

Kylee Status Update for 2/15/20

  • Continued research on Intelligent Driving models
  • Refined demo idea from two lane circle to figure 8
  • Did calculations to determine sizes of track and lanes as well as the speed of vehicles.
  • Created and filled out design decision document
  • Wrote basic Arduino code to control the robotic cars through WiFi using the ESP8266