Team Status Report for 2/26

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?

The most significant risks currently are ensuring that the images can be vectorized efficiently since the latencies have not currently  been tested although it looks promising since the algorithm Vtracer uses also includes line simplification which would reduce the number of point per primitives. If Vtracer is not fast enough then we will also consider PoTrace or and reverting back to vectorizing with Computer Vision using a temporal approach

System Design Changes:

This week we pivoted our design to do our vectorization on the software side with the help of Vtracer, a Python .PNG to .SVG converter. We considered using other .SVG converting packages like PoTrace but decided to go with a Vtracer due to it’s support for colored images in case we do want to extend for our stretch goals of adding colored diagrams and it also maintains better fidelity of the original image when compared to PoTrace. This change in decision does not incur any additional costs to our project. We are also looking into methods to remove having the user need to agree to receive a message from a peer in order to make the user interaction smoother. This is still currently being researched but should not cause any major changes to the system.

The schedule has not changed. Currently our message passing is successful and within our latency bounds and our CV is able to detect roughly straight lines without much difficulty.

Leave a Reply

Your email address will not be published. Required fields are marked *