Changes between Initial Version and Version 1 of Other/Summer/2025/SASS


Ignore:
Timestamp:
Jul 16, 2025, 4:03:34 PM (4 months ago)
Author:
mprias
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Other/Summer/2025/SASS

    v1 v1  
     1====== SASS Project Weekly Progress ======
     2
     3The **Streetscape Application Services Stack (SASS)** project focuses on real-time data collection and synchronization from multiple urban sensors, including Reolink cameras, IMUs, and GoPros. Below is a week-by-week breakdown of progress.
     4
     5===== Week 1: Project Setup and Goals =====
     6  * Defined core objectives of the SASS system: synchronization, modularity, and smart city relevance.
     7  * Introducing ourselves, setting up the initial team structure, and responsibilities.
     8
     9[[https://docs.google.com/presentation/d/1p8nV1vZ17MS4CkrOK9NQw4-iRzlXZ5HGDOndV_pC5ZQ/edit?usp=sharing|SASS Week 1]]
     10
     11===== Week 2: Reading Papers about Multi-modal Fusion =====
     12  * Discussed with Professor Ortiz about making SASS identify a person in need more discreetly.
     13  * Read additional papers to check the feasibility of the proposed framework.
     14  * Read about multi-modal fusion.
     15
     16[[https://docs.google.com/presentation/d/1Ivg-oL52mO3MFFtkdgzWx8nqzrGvftfuh3TCct3HUws/edit?usp=sharing|SASS Week 2]]
     17
     18===== Week 3: System Design and Website Development =====
     19  * Began developing a website to present a portfolio about the project.
     20  * Set up a System Design Diagram for the data collecting phase.
     21  * Set up all the cameras we are going to use and look into the Sensorlogger App.
     22
     23[[https://sass.sitesforsights.com|SASS Website]]
     24
     25[[https://docs.google.com/presentation/d/1GZb9VYsYAKYFI62kDQaLID3A8Wms09LO4kZcm8KKHu0/edit?usp=sharing|SASS Week 3]]
     26
     27===== Week 4: Devices + IMU Merge Efforts =====
     28  * Installed Reolink, GoPro cameras, and the SensorLogger App, and basic data collection scripts for each of them.
     29  * Investigated frame-by-frame video analysis from Reolink and GoPro.
     30  * Began efforts to merge IMU and Reolink outputs into a unified logging format.
     31  * Same with the GoPro.
     32  * Integrated IMU sensors with custom Python-based `sensorlogger` script.
     33
     34[[https://docs.google.com/presentation/d/1fTfzNBAOt4M2juhcvxzE93u7bTileGKCyqfKYh1wMik/edit?usp=sharing|SASS Week 4]]
     35
     36===== Week 5: Synchronization Debugging =====
     37  * Analyzed misalignments in timestamps between sensor types.
     38  * Attempted to merge all Python files into one. As a result, the Reolink/SensorLogger file and the GoPro/SensorLogger file were used separately.
     39  * System Design Diagram was updated. (As shown in the Google slide).
     40
     41[[https://docs.google.com/presentation/d/1JiTKHyalNv-pw_bfK3cg0kzkMeXzqnVE0nZ_AtymJFA/edit?usp=sharing|SASS Week 5]]
     42
     43===== Week 7: Infrastructure and Database Discussions =====
     44  * Explored alternatives to flat CSV files; began shifting toward a structured database backend.
     45  * Discussed metadata tagging and retrieval use cases.
     46  * Updated diagrams to reflect router roles, LAN/IP separation, and new sensor locations.
     47  * Started experimenting with YOLOv5 object detection to help define the best camera angles for installations.
     48
     49===== Week 8: Unified Logger Development =====
     50  * Finalize camera alignment with YOLO results.
     51  * Started collecting data.
     52
     53----
     54
     55**Next Steps**
     56  * Still collecting data.
     57  * Test the unified data logger under full deployment.
     58
     59----
     60
     61Questions or contributions? Please contact us.