11/06/2024 Wednesday Meeting Notes #81
himanshunaidu
started this conversation in
Meeting Notes
Replies: 1 comment
-
|
Next Immediate Steps:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The following notes are the progress and next steps for each sub-task.
Assigned to Himanshu.
Will be picking up the frame control in the coming weekend. I anticipate taking care of a few other issues as noted here.
#21
#80
Assigned to Ihor and Dmytro.
a. Object Tracking
Ihor is looking through the OASIS code for object tracking. The OASIS code utilized a version of ORB tracking. Implementing this on Swift will take time.
While homography transformation can be done, a brute force approach with smoothing could work.
Having a region boundary and the centroid for an object, across frames can help with an initial version of object tracking.
IMU sensors can be utilized. Thanks to the presence of IMU sensors, we do not have to estimate change, a task which ends up involving rigid affine transformation. With IMU sensors, we have r-vectors as well as angular movement.
IMU sensors in iPhones can also give us confidence intervals (need to check which ones do).
IMU drift. While frame-to-frame, this will not be an issue, we are currently capturing frames through manual user interaction. This will add significant error.
Other keywords: Kalman filter, SLAM
Conclusion: Try a brute force approach first, and then identify if we need fancier methods.
The following are the pending tasks:
b. Union of Masks
Dmytro is still working on this.
GoInfoGame currently uses the Overpass request manager, and OSM-based web auth.
We import data from OSM as well as TDEI. But we focus on sidewalks, and we want to update in bulk, so we just push to TDEI.
Another reason for using our own workspace is the issue with ID updates. Whenever someone updates an object in OSM, the ID of that object changes, which is not favorable. TDEI avoids that.
Currently, the GoInfoGame developers have updated documentation, so we will be going through the updated documentation, and come back with any possible questions we come up with.
We do not have access to upload databases to TDEI workspaces, so we are supposed to get access from Professor.
Mariana does not have access to some of the documents, so we will have to work on getting her access to the relevant documents listed in the following issue:
#61 (comment)
This work is currently contingent upon the work of Segmentation Mask Post-Processing and API Transmission.
It hasn't been assigned yet, but Himanshu or Mariana will most likely be dealing with it.
Beta Was this translation helpful? Give feedback.
All reactions