https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3ATianwei37%2FReport_%26_Blog%2FWeek_3 2026-10-25T22:59:30Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Tianwei37/Report_%26_Blog/Week_3&diff=151679&oldid=prev 2018-06-28T21:17:24Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 21:17時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:Tianwei37/Report_%26_Blog/Week_3&diff=151678&oldid=prev 2016-06-11T11:52:58Z

<p>‎<span dir="auto"><span class="autocomment">What I did</span></span></p> <p><b>新規ページ</b></p><div>== What I did ==<br /> * refine correspondence data structure according to Sergey’s suggestion<br /> * revise BKE_tracking_correspondence_add accordingly<br /> * add BKE_tracking_multiview_reconstruction_check which checks conditions for multi-view reconstruction<br /> * 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.<br /> * Refine data structures for multi-view reconstruction<br /> * Extend my report into a documentation about multi view reconstruction at here: https://wiki.blender.org/index.php/User:Tianwei37/Report_%26_Blog/Multi-view_Reconstruction_Documentation<br /> * manage BKE_tracking_multiview_reconstruction_context_free as several data structures have been changed to arrays.<br /> * convert the simple_pipeline code to autotrack code. Basically the entire reconstruction pipeline should now be based on the new autotrack pipeline. <br /> <br /> == What I will do next week ==<br /> 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.<br /> <br /> == Questions ==<br /> <br /> 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?<br /> <br /> 2. Does anyone know how to delete a wiki page? I accidentally create one more and want it deleted.</div>

wiki>Tianwei37