<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi everyone,<div class=""><br class=""></div><div class="">This is my week 3 report, a week that got me further into the multi-view reconstruction pipeline! You can also find this report at <a href="https://wiki.blender.org/index.php/User:Tianwei37/Report_&_Blog/Week_3" class="">https://wiki.blender.org/index.php/User:Tianwei37/Report_%26_Blog/Week_3</a>.</div><div class=""><br class=""></div><div class="">What I did:</div><div class=""><ul class="Apple-dash-list" style="font-family: HelveticaNeue;"><li class="">refine correspondence data structure according to Sergey’s suggestion</li><li class="">revise BKE_tracking_correspondence_add accordingly</li><li class="">add BKE_tracking_multiview_reconstruction_check which checks conditions for multi-view reconstruction</li></ul><div class=""><ul class="Apple-dash-list" style="font-family: HelveticaNeue;"><li class="">Clear up my mind about BLI_list, BLI_array, BLI_buffer. Stuck by a bug for a long time, then It turned out that the bug is caused by passing a data structure (MovieClip) without *next and *prev pointers into a blender_list.</li><li class="">Refine data structures for multi-view reconstruction</li><li class="">Extend my report into a documentation about multi view reconstruction at here: <a href="https://wiki.blender.org/index.php/User:Tianwei37/Report_&_Blog/Multi-view_Reconstruction_Documentation" class="">https://wiki.blender.org/index.php/User:Tianwei37/Report_%26_Blog/Multi-view_Reconstruction_Documentation</a></li><li class="">manage BKE_tracking_multiview_reconstruction_context_free as several data structures have been changed to arrays.</li><li class="">convert the simple_pipeline code to autotrack code. Basically the entire reconstruction pipeline should now be based on the new autotrack pipeline. </li></ul><div class=""><font face="HelveticaNeue" class="">What I will do next week:</font></div><div class=""><font face="HelveticaNeue" class="">Working towards the tentative goal of week4-6 in my GSoC proposal, Connect the front side UI with the back-side SfM engine. More specifically, I will continue to focus on the libmv autotrack pipeline next week. Currently libmv/autotrack is immature in that several header files are designed without the actual *.cc implementation. I will basically learn from libmv/simple_pipeline and migrate everything needed for multi-view reconstruction to libmv/autotrack.</font></div><div class=""><br class=""></div></div></div><div class="">Questions:</div><div class="">1. What is fundamental difference between autotrack and simple_pipeline? From my point of view, autotrack is based on mv::marker which knows what clip it comes from, while simple_pipeline is based on libmv::marker which is agnostic about the clip. Also autotrack has data structures that have more details than their counterparts in simple_pipeline, like libmv_Marker. It knows the marker source, like whether it is specified manually, or detected automatically, which can lead to fine-grained controls in the algorithm implementations. Is there anything else that I have missed and should attend to?</div><div class=""><br class=""></div><div class="">2. Does anyone know how to delete a wiki page? I accidentally create one more and want it deleted.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Tianwei</div></body></html>