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_5 2026-09-04T04:56:44Z このウィキのこのページに関する変更履歴 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_5&diff=151827&oldid=prev 2018-06-28T21:17:36Z

<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_5&diff=151826&oldid=prev 2016-06-25T16:46:20Z

<p>Created page with &quot;== Week Progress: == The first draft pipeline of multi-view camera is about to finish. I have basically migrated necessary components from libmv/simple_pipeline to libmv/autotrac...&quot;</p> <p><b>新規ページ</b></p><div>== Week Progress: ==<br /> The first draft pipeline of multi-view camera is about to finish. I have basically migrated necessary components from libmv/simple_pipeline to libmv/autotrack to do the multi-view reconstruction. Specifically, here is what I did this week:<br /> <br /> * Convert correspondence track indexes into a set of global indexes, according to my mentor (Sergey)’s suggestion. The global track index is constructed by first indexing all tracks linearly, and then turn the second track index of a correspondence into the first track index of the correspondence. In this way, we can go over correspondence list only once. The global index would be passed to libmv.<br /> <br /> * Working on the multi-view pipeline. The workflow is similar to that of the single camera case, cause my goal is to first make multi-view stuff work before refining it. I rewrote some key gradients, such as track intersection and camera resection, based on the new mv::Reconstruction and mv::Tracks. <br /> <br /> == What I will do next week: ==<br /> <br /> Unfortunately, I still have some bugs in the multi-view camera resection to solve. For example, the track intersection and camera resection is not working correctly as I expected it. So there will be heavy debug work next week. My goal is to get a successful multi-view reconstruction and pass back the results to blender, by the end of next week, which is in accord with my project proposal. <br /> <br /> I haven’t thought about how object solver will fit into the multi-view pipeline, by which I mean the modal solver. Projective bundle is also not considered since it seems that it is not used in the current reconstruction pipeline, right? The multi-view pipeline still relys on some of the gradients in simple_pipeline, like libmv::CameraIntrinsics, which might be moved to autotrack if we are going to abandon simple_pipeline.</div>

wiki>Tianwei37