Week #4

Week #4 #

Testing and QA #

We have tests that check:
Signal availability between receiver and control panel
The control device of the robot at the moment
The speed of the wheel motors and steering angle

Evidence of test execution #

Signal availability Code, Screenshot
Control device of the robot Code
Wheel motors and steering angle Code, Screenshot

CI/CD #

Ready CI/CD for all python code in the project, tests are checked based on the requirements of the Pylit library. All tests passed and the code is written perfectly. Also added a test to check the loading of the model: the test loads the model and also checks the output of the model on test data.

CI/CD pipeline

Vibe Check #

The team conducted a short health check to reflect on progress and coordination. Overall motivation remains high, and all members are aligned on the current goals. There was a need identified to improve coordination and task visibility across the team.

Action Items:

  • Improve communication on task ownership and current blockers.
  • Introduce regular short sync meetings to track progress and address issues early.

Weekly commitments #

Individual contribution of each participant #

Valeria:

  • Working with platform:
    Soldering wiring, making connectors for connection and security Photo
    Connecting all the wiring elements and testing the soldering correctness using an oscilloscope
    Thinking over the mat model of the machine, taking into account the frame for the correct distribution of the center of mass Photo
    Connecting pins for emergency stop of the machine Photo (blue wire)
  • Testing and optimizing the arduino code

Nikolay:

  • Modeling of components for mounting equipment on a RC car Link
  • Printing simulated components on a 3D printer and mounting them on a car
  • Making new datasets

Lidia:

  • Preprocessing of updated datasets
    Link
    Link
    Link
  • Soldering and crimping wires to create a reliable connection between the IMU and Arduino
    Photo

Ilyas:

Andrey:

  • Compiling tests to check the operability of robot elements
  • Writting CI/CD for all python code in the project
  • Сompiling a weekly report

Plan for Next Week #

  • Defactoring code
  • Solving problems with robot’s wiring
  • Testing MVP v2

Confirmation of the code’s operability #

We confirm that the code in the main branch:

  • [✅] In working condition.
  • [✅] Run via docker-compose (or another alternative described in the README.md).