Eleanor’s Status Report for 12/07/2024

Personal Accomplishment

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

This week, I focused on debugging the integration system, assembling all electronic components onto the vest, and advancing work on the final report, poster, videos, and demo. For the integration system, the two subsystems functioned well when running separately or synchronously, but running them in parallel caused the audio output to malfunction. Initially, we suspected an issue with the audio hat wiring, but we later identified the problem as signal interference during integration. To address this, I replaced threading with subprocesses, allowing the two subsystems to run in isolated sandboxes. This change improved overall performance. Additionally, we modified the system to start functioning as soon as the button is pressed, which represents reboot, eliminating the need for laptop operation.

We also conducted extensive testing, including integration tests and overall system tests of the vest. By following tests expected and shown in the design report, we completed the unit tests for each components, the integration tests for two subsystems and the whole large system, and the overall test by wearing assembling the physical vest (see results in group report).

Schedule

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 has been slightly behind schedule due to some unexpected minor issues. However, with the final deadline approaching next week, we plan to dedicate more time and effort to the project in the coming days to catch up and ensure everything is completed on time.

Upcoming Deliverables

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

  • Double check functionalities and ensure stubborns
  • Finalize and deliver the final video, poster,  demo, and report

Team Status Report for 11/30/2024

Risk and Plans

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? 

Risks and Plans: One of the most significant risks to the project is the inconsistency of audio alerts, where the playback sometimes misaligns with what it should be or produces random, unexpected noise. This issue could hinder the reliability and usability of the system, particularly for the intended users who rely on accurate and timely alerts.

Risk Management: We are currently investigating the root cause of the issue, especially on the audio port configuration and playback synchronization. Multiple tests are being conducted under different conditions to isolate the problem.

Contingency Plans: As a backup, we will test alternative audio output methods, such as the smart phone’s speaker.

Change in Design

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?

Change in Design: A change was made to the audio hat configuration to ensure it consistently identifies the correct port for audio output.

Costs IncurredTime: Additional time was spent troubleshooting and reconfiguring the audio hat. Testing Overhead: Additional testing was done to confirm the new configuration works reliably across various conditions.

Mitigation Going Forward: Further tests are being conducted to validate long-term reliability, and as a backup plan, we are exploring alternatives, such as directly configuring multiple ports to ensure at least one of them could work.

Schedule Updates

Provide an updated schedule if changes have occurred.

Despite the technical challenges, our project remains on schedule. The hardware and software components have been tested individually, and integration work is beginning as planned. Next week, we will focus on:

    • Testing GPS and Phone-Based Geolocation: Evaluate the feasibility of GPS and phone-based geolocation for indoor positioning, and use in locations beyond Hamerschlag Hall.
    • Integration Testing: Conduct comprehensive testing of the fully integrated system to ensure all components work seamlessly together.
    • User Feedback Interviews: Interview individuals with visual impairments to gather feedback, refine our design, and identify improvements to go beyond the MVP.
    • Component Integration with Vest: Finalize the integration of all components into the wearable vest, ensuring usability and practicality.

Eleanor’s Status Report for 11/30/2024

Personal Accomplishment

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

This and last week, I focused on multiple aspects of the project, including preparing videos for GPS usage, preparing the interim project demo, adjusting the audio port, and developing the final presentation slides. Since our GPS system only functions outdoors, we recorded demonstration videos in front of Hamerschlag Hall to showcase its capabilities for the interim demo. I also worked on the interim project slides and demo presentation to show our technical progress, task distribution, and system integration. To address sound playback issues, I adjusted the audio port to ensure it functioned correctly when we tested them by ourselves. However, during the demo, the port behavior was still inconsistent, appearing to change randomly, and sometimes the audio did not align with the original file. After the demo, we re-adjusted the audio configuration to improve reliability. Additionally, I dedicated time for the final presentation slides to show our progress and outcomes.

Schedule

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 currently on schedule with the project. All planned tasks for this phase have been completed on time, and I am progressing as expected. If any unforeseen delays arise, I will prioritize major tasks and collaborate with teammates to ensure we stay on track.

Upcoming Deliverables

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

  • Resolve the issue of audio playback misalignment with the original files.
  • Integrate all  components into the vest.
  • Interview visually impaired people to gather feedback and suggestions for improving our product.

Eleanor’s Status Report for 11/16/2024

Personal Accomplishment

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

This week, I focused on integrating radar detection with sound alerts, addressing multiple technical challenges. I began by resolving an audio output issue on the audio hat, testing various ports until identifying hw:3,0 as the correct configuration. Next, I adjusted the alert frequency and timing period to ensure the playback that aligns with the original audio file’s rate. I implemented conditional logic to play alerts only when relevant scenario changes are detected, avoiding repetitive notifications and improving usability. I also assisted teammates with detecting and reading data from the accelerometer; we initially worked to convert the C code to Python for consistency with the rest of the project but ultimately decided to continue using C. In preparation for next week’s demo, I refined the presentation of my work to be more intuitive and accessible.

Schedule

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

My tasks are currently on schedule. However, improving the accuracy of both radar and accelerometer detection may require additional time and effort for fine-tuning and testing. It’s also important to address a specific use-case where a high-speed object passes the user; in such scenarios, the audio alert might only have time to announce the object at 5 meters, even if it has already closed in to 1 meter by the time the alert sounds. To ensure reliability in these rapid proximity changes, I plan to explore adjustments to alert timing and prioritization.

Upcoming Deliverables

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

  • Fine-tune radar and accelerometer
  • Readjust logic of sound alert to make it more fir in use-case
  • Test and record video for GPS outdoor

 

Eleanor’s Status Report for 11/09/2024

Personal Accomplishment

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

GPS Testing: Since we know our chosen GPS device only functions outdoors, we tested it outside in front of Hamerschlag Hall. The GPS successfully picked up the correct coordinates, and when these were fed into the Google Maps API, it returned the accurate physical address. To ensure a smooth demo, we tried placing the GPS indoors near a window, but it still couldn’t receive a signal. Therefore, our plan for the GPS demo will be to record a video of its operation in advance.

Radar Tuning and Testing: I also worked on optimizing the radar by adjusting key parameters, including the minimum and maximum detection angles, the movement speed range, and the detection distance. To better visualize the radar’s detection limits, I implemented a real-time tracking graph with the x-axis showing angles from -90° to 90° and the y-axis representing distances from 0 to 7 meters. This graph dynamically displays detection results for both distance and direction (a screenshot is included in the group report). For initial testing, we divided radar tests into nine scenarios (distances of 1m, 3m, and 5m, with obstacles on the left, center, and right). We observed that the radar’s accuracy was higher at shorter distances. Additionally, it performed better when detecting obstacles moving away from it rather than approaching. For instance, at a 3-meter distance in the center, the radar consistently detected obstacles only as they moved away, not as they came closer.

Schedule

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 on schedule. We made significant strides this week, completing the first round of testing for both the GPS and radar, and they are functioning well overall. While there are some minor performance concerns, I plan to focus on tuning and optimization next week to address these issues and ensure everything is fully aligned with our project timeline.

Upcoming Deliverables

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

  • Connect the radar output to the audio hat and implement corresponding audio alerts.
  • Fine-tune the radar settings and conduct more detailed testing with improved test cases.
  • Test the accelerometer and design an algorithm to recognize specific movements (falling down vs normal movement).

Eleanor’s Status Report for 11/02/2024

Personal Accomplishment

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

This week, I focused on integrating and setting up GPS component on the RPi OS with my teammates. We began by installing Minicom to detect GPS connectivity through the RPI interface. After configuring the GPS on the OS, we successfully accessed and displayed GPS data in the terminal. Based on this, I expanded a function to convert terminal GPS data into JSON format as {"lat": latitude, "lon": longitude, "time": timestamp, "addr": address}. Additionally, I modified a function to store this data in a JSON file, allowing us to log and track GPS data for testing purposes. For future usage, I set up a feature that retrieves only the latest coordinate data upon request, improving real-time data access. To provide real-world addresses for the coordinates, I integrated the Google Maps Geocoding API, enabling conversion of latitude and longitude into readable addresses.

We also identified an issue with the button component: it was too small, making it difficult for users to locate and press it quickly to cancel an email alert. I researched alternative options, discussed them with the team, and submitted a new order form for a larger, more user-friendly button.

Schedule

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

My individual work is currently on schedule, aligning with the project’s planned timeline. As mentioned earlier, I am in the mid-to-late phase of my assigned work. So far, we have made good progress in integrating and configuring key components, which has provided the foundation I need to proceed with my own tasks. The team’s progress has allowed me to begin work on specific functionalities. If any delays arise, I plan to collaborate more closely with teammates to identify any bottlenecks and redistribute tasks if necessary

Upcoming Deliverables

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

  • Assisting teammates set up and test radar: involves mounting, configuring, and validating the radar’s accuracy in detecting objects at various distances and angles (same as last week).
  • Once the accelerometer arrives, I will begin setting it up and developing algorithms to distinguish between actual falls and normal body movements, a critical feature for our project.
  • After completing the GPS setup, we confirmed that it functions only in outdoor environments, so we plan to conduct further testing to assess GPS performance outdoor and explore connectivity options for integrating GPS data with our website.

Team Status Report for 10/26/2024

Risk and Plans

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? 

One risk to our project is the limited compatibility of Python packages with the Raspberry Pi 4 (RPi4) operating system, largely because pip, the package installer, is not available or functional on the RPi4. This limitation impacts our workflow; while we can develop and test code locally, some libraries that work seamlessly on our local machines are incompatible with the RPi4 environment, requiring us to find alternatives or workarounds. For example, we initially used the pyttsx3 library for AI-driven audio generation to create spoken alerts. Although it performed well in local tests, pyttsx3 cannot be installed or used on the RPi4, hindering our ability to generate audio dynamically in real-time on the device.

To manage this risk, we’ve developed a contingency plan to pre-generate multiple audio files on our local machines, categorizing them based on obstacle distance and direction, and then transferring these files to the RPi4. This approach allows us to use pre-recorded audio cues rather than generating audio directly on the RPi4, maintaining essential functionality while bypassing package compatibility issues. On the contingency planning side, we are also proactively researching compatible packages and frequently testing setup code directly on the RPi4 before full implementation. Hope by doing so, we can identify and resolve compatibility issues early in the process, and then minimize disruptions and making smooth integration.

Change in Design

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?

This week, we focused on a potential adjustment to our system’s design related to GPS integration with the RPi4. Our main goal was to assess the feasibility of connecting the GPS module directly to the RPi4. However, if stable integration cannot be achieved due to protocol limitations, our backup plan is to use the user’s smartphone GPS for location tracking. This change would require minor software updates to process location data from the smartphone, ensuring functionality remains seamless without additional hardware.

No design changes have been implemented at this stage. However, if the smartphone GPS becomes necessary, we will update the block diagram and system specifications to reflect this alternative approach. This contingency plan effectively manages the GPS integration risk while maintaining our project timeline.

Schedule Updates

Provide an updated schedule if changes have occurred.

Our schedule remains on track with no significant changes at this time. In the coming week, we plan to accelerate system integration across all components. With the audio hat integration successfully completed, our next priority is the radar component, which we aim to finish by the end of next week. If the newly ordered accelerometer arrives as expected, we also plan to initiate GPS integration.

Eleanor’s Status Report for 10/26/2024

Personal Accomplishment

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

This week, I focused on setting up the Raspberry Pi with teammates, completing various configurations, syncing our remote servers with local setups, and integrating an audio hat for audio output. After successfully installing and testing the audio hat, I delved into sample codes provided in tutorials to understand how the Raspberry Pi OS interacts with these components. Following the tutorials, I adjusted the audio volume to around 40 decibels, which aligns with our research on maintaining an audible yet non-intrusive sound level. Additionally, I wrote a Python script that leverages an AI package to automatically generate audio outputs. These outputs provide information about the distance and direction of obstacles, an essential feature for enhancing accessibility. The progress included understanding component integration, code testing, and balancing audio settings.

Alongside my technical work, I completed an ethics assignment. This involved engaging with readings, watching relevant videos, and reflecting on ethical considerations within our project.

Schedule

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

This week, I made solid progress on my individual tasks, keeping the project on schedule. Last week, I set specific goals: to support my teammates with system integration and to begin working on the audio hat. We achieved a good portion of the integration tasks. For the audio hat, I managed not only to complete the initial installation but also to fine-tune it, adjusting settings and exploring its functionality within our project constraints. The audio hat is now integrated, performing well in initial tests, and prepared for further development stages. Overall, each of these accomplishments contributes to our overarching goals.

Upcoming Deliverables

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

  • Assisting teammates set up and test radar: involves mounting, configuring, and validating the radar’s accuracy in detecting objects at various distances and angles.
  • Learning if the GPS component can be integrated to Raspberry Pi: if feasible, I’ll support teammates in setup and testing; if direct integration isn’t possible, I’ll help shift to exploring GPS via smartphones, ensuring accurate, synchronized location tracking with the Raspberry Pi for navigation support.

Eleanor’s Status Report for 10/20/2024

Personal Accomplishment

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 completed design report’s Use-Case Requirement, Technical Requirements, and Testing&Metrics sections in the last past week. To be more specific, in Use-Case Requirement, I detailed the needs of both direct and indirect users. For direct users, I outlined requirements such as the need for real-time audio alerts that enable visually impaired individuals to react to obstacles. This includes specifying alert parameters, like detection ranges and acceptable false negative and false positive rates, to ensure user safety. I also addressed battery life and wearability, emphasizing the need for a lightweight and long-lasting device. For indirect users, such as caregivers, I defined requirements around emergency alerts and GPS accuracy to ensure they can quickly locate and assist users in emergencies. In Technical requirements, I focused on translating these use-case needs into concrete design goals according to the implementation architecture. This included setting benchmarks for the radar’s detection range, accuracy, and response time for audio alerts. I defined power consumption targets to ensure that the device can operate for at least 3 hours on a single charge, addressing efficiency needs without compromising performance. I also specified technical parameters for the fall detection system, including sensitivity thresholds and the maximum acceptable time for emergency alerts to be sent. In Testing&Metrics, I developed a comprehensive plan for verifying the device’s functionality. This involves unit testing individual components like the radar’s accuracy, audio response time, and power consumption. I outlined specific test procedures, such as simulating falls to evaluate the accuracy of the fall detection system and ensuring that GPS coordinates provided in alerts are accurate within a 10-meter range. Additionally, I planned integration tests that simulate real-world use, with volunteers using the device to evaluate its performance in obstacle detection and fall detection scenarios.

Schedule

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

My own progress is on schedule so far, but due to the delay in the progress of each component’s integration, there is a risk that the overall project timeline may be affected. To address this, I plan to allocate extra time for helping in integration tasks in the upcoming week and will collaborate closely with team members responsible for each component to ensure smooth and timely integration. Additionally, I will assist in troubleshooting any issues that arise during the integration phase to prevent further delays. This proactive approach should help bring the project back on track.

Upcoming Deliverables

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

My goal next week is to support my teammates in system integration and unit tests for each component. While they focus on fully connecting the radar, speaker, and accelerometer with the RPi4 and conducting initial tests to ensure stable operation, I will assist with troubleshooting any integration challenges that arise. Additionally, I will help verify the interaction between components, particularly focusing on validating sensor accuracy and ensuring smooth communication between the devices and the Raspberry Pi. I will also contribute to the unit testing of each component, including checking the radar’s obstacle detection and the accelerometer’s fall detection performance, and I will assist in testing the audio system’s response time.

Eleanor’s Status Report 10/05/2024

Personal Accomplishment

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 began working on the design report, taking responsibility in the Use Case Requirements, Design Requirements, partial Design Trade Studies, and the Test & Validation sections. Especially, in the use sase requirements, I identified and documented the various scenarios in which our design would be utilized, and for the design requirements, I outlined the features and specifications that our system need to meet to ensure optimal performance and achieve the use case requirements (both requirements are also listed concisely in the presentation slide).
  • I recorded audios for the sound alert system. I categorized these audio files based on direction and distance. They are divided into three directional categories: left, front, and right, and cover five distance ranges: 1m, 2m, 3m, 4m, and 5m, which resulted in a total of 15 distinct audio files. Each alert conveys the message: “Detecting obstacles in your {direction} about {distance} away from you. Please be careful to avoid it.” To facilitate the playback of these audio alerts, I researched and watched several YouTube tutorials on connecting our audio hat to the  raspberry pi and then transmit and play the audio files during operation.
  • I picked up and returned components which we agreed to relinquish.

Schedule

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

Since my tasks are typically focused on the middle or later stages of the project, the delay in receiving those components does not  impact my individual progress very much. However, I recognize the need to prepare for a potential reduction in my work time in the future and to assist my teammates more, as the delay affects the overall progress, especially the first stage, of our project.

Upcoming Deliverables

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

  • Set up the audio hat as soon as it arrives, and then mock different radar detecting results to test the audio message playback to ensure the files display correctly.
  • Assist teammates with setting up the radar and accelerometer, and support data collection during the initial stage. My primary work will begin in the next phase, once the initial setup is complete.

(due to the components arriving delay, similar upcoming deliverables as last week)