Posted on

Reva Poddar’s Status Report for 11/30

Progress Update:

This week, I focused on refining and implementing the data processing algorithms, including smoothing, moving averages, and pitch-based thresholding for footstrike detection. These algorithms are now functioning within the development environment, but further fine-tuning is needed to ensure they handle diverse gait patterns effectively. Initial testing highlighted areas for optimization in both noise reduction and threshold calibration.

Challenges Faced:

  1. Noise Filtering: Balancing the smoothing algorithms to reduce noise without removing key features necessary for accurate footstrike detection.
  2. Threshold Calibration: Determining the appropriate pitch threshold values to reliably identify footstrikes across different running styles and conditions.
  3. Integration: Ensuring the algorithms operate efficiently in the development environment without significant lag.

Next Steps:

  1. Complete fine-tuning of the data processing algorithms to improve accuracy and reliability.
  2. Test the system under varied gait patterns and terrains to identify additional areas for optimization.
  3. Begin integrating the refined algorithms into the main application for further testing and visualization development.
Posted on

Reva Poddar’s Status Report for 10/26

Progress This Week

  • This week, I focused on setting up the Bluetooth connection between the IMU device and the StrideSense mobile app in Flutter. I was able to integrate the Bluetooth package and detect the IMU device. However, I encountered an issue where the app struggled to retrieve consistent values from the IMU; specifically, the connection would intermittently drop before the sensor data could be fully received.

Schedule Status

  • Slightly Behind Schedule: The unexpected connectivity issue has delayed our initial goal of successfully retrieving sensor values in the app. This setback means I need additional time to stabilize the Bluetooth connection.
  • Plan to Catch Up: I will work on debugging the connection issue, focusing on modifying Bluetooth settings within the app and researching potential solutions for intermittent disconnections. My goal is to have a stable connection that can retrieve sensor values consistently by next week.

Goals for Next Week

  • Fix Bluetooth Connection Instability: Focus on resolving the connection issue to achieve reliable data retrieval from the IMU device.
  • Initial Data Handling in the App: Once values are consistently retrieved, begin implementing basic data handling to display these values in the app’s interface.
  • Conduct Further Testing: Run additional tests to troubleshoot connection stability across different distances and potential interference scenarios.
Posted on

Reva Poddar’s Status Report for 10/21

Accomplishments This Week:
This week, I focused on setting up the Bluetooth communication framework and managing data transfer. I made progress in preparing the Bluetooth package for Flutter to detect nearby devices and started evaluating different data handling techniques to ensure smooth real-time data transmission. I also looked at flutters existing graphical representation libraries.

Progress Status:
I am currently a bit behind schedule, and anticipate that I will encounter issues with maintaining a stable connection and organizing the data flow within the app, so I am planning to dedicate more time throughout the upcoming weeks to catch up. The delay primarily involves establishing the initial Bluetooth connection and finalizing the file system structure. I am confident that with a concentrated effort, I can get back on track and complete the planned milestones.

Deliverables for Next Week:

  1. Complete the initial Bluetooth connection setup to receive data on the app.
  2. Finalize the file system design for managing Bluetooth-transmitted data from ESP32.
  3. Begin integrating the data visualization features using data from the Bluetooth connection.

Updated Schedule:

  • By End of the Week: Continue working on making the initial Bluetooth connection and refining the file system for Bluetooth communication.
  • Upcoming Weeks: Dedicate extra effort to finalize the Bluetooth integration with Vansh and start implementing the graphical representation components.

The focus will be on managing any remaining connectivity or data flow issues and ensuring that progress aligns with the project goals.

Posted on

Reva Poddar’s Status Report for 10/5

This week, I made significant progress by developing a functioning prototype of our app based on the design presentation specifications. The app now has three key sections:

  • A main page that displays real-time statistics collected from the IMU, providing users with immediate feedback on their movement data.
  • A history and trends page that shows past performance, allowing users to review historical data and track improvements over time.
  • A settings page, where users can set customizable thresholds for specific metrics (e.g., speed or stride efficiency) and receive alerts if they fall below the set limits.

I faced some challenges setting up the iOS simulator for testing, mainly due to issues with dependencies in my development environment, which delayed the testing by a few days. Despite these challenges, I was able to get the prototype working on an IOS simulator however android testing will require a little bit more time to ensure the app runs smoothly on both platforms.

Next Steps:

Going forward, my focus will shift toward data integration:

  1. I plan to work closely with Vansh to receive the IMU data values via Bluetooth. This will involve using Flutter’s Bluetooth package to establish the connection and ensure smooth data transmission from the IMU to the app.
  2. Once I receive the data, I will begin integrating it into the app, developing a system to analyse + present the information graphically to users in real-time.
  3. I will also continue addressing the iOS simulator issues and aim to get the app running on both iOS and Android devices for a more robust testing process.
Posted on

Reva Poddar’s Status Report for 9/28

This week, I focused on the software architecture for our project’s app, carefully evaluating various software platforms in terms of usability, flexibility, and development efficiency. After considering the trade-offs between different technologies, I decided to use Flutter, a cross-platform framework, to build the app. This decision allows us to target both iOS and Android devices simultaneously, ensuring a wider user reach and optimizing the development process in terms of cost and time. Additionally, I laid out the structure of the app into three primary sections: one for viewing historical data and trends, another for displaying real-time data collected from the motion-sensing shoe sole, and a settings section for customizing user preferences. This architecture is designed to provide users with seamless access to essential features, improving their experience by offering an intuitive interface. With the software choice and structure finalized, I’m confident we are on schedule. My next step is to begin implementing the app in Flutter, setting up the basic layout and navigation between these sections.

No significant risks have been identified at this stage, but I will continue to monitor the development process for potential issues, particularly around cross-platform performance and ensuring the app remains intuitive and accessible to a broad audience.

Posted on

Reva Poddar’s Status Report for 9/21

This week, I helped Vansh rehearse for the project proposal presentation, which was successfully delivered. I also focused on the software architecture looking at how I can build an app to take data from our BLE module, and researching how to process IMU data for analyzing metrics like foot strike and stamina some of our use case metrics. The project proposal presentation was completed on time, and I’ve begun planning the software design for data processing. Next week, I will focus on data processing for the IMU sensor and begin initial test scripts, as well as support Vansh in selecting suitable hardware components. The main risk is ensuring the accuracy and frequency of IMU data. I plan to conduct testing and calibration to mitigate this.