「利用者:Sftrabbit/GSoC 2013」の版間の差分

提供: wiki
移動先: 案内検索
 
(1版 をインポートしました)
 
(相違点なし)

2018年6月29日 (金) 05:54時点における最新版

Google Summer of Code 2013

For Google Summer of Code 2013, I'm working on the motion tracking module. In particular, I'm aiming to implement multicamera reconstruction and support for varying focal length. Check out my proposal for more details. I'll soon be adding a more detailed design document and schedule.

Schedule

In weeks 3 and 4, while working on focal length constraints, I spoke to my mentor about what I should be aiming for. I was feeling a little overwhelmed with how much I had proposed, given that I had no previous knowledge of Blender development or motion tracking. We agreed that my proposal was overambitious and that I should focus on multiview reconstruction for my Summer of Code project. If I can fit it in, I can do some variable focal length solving at the end.

An approximate schedule for this project (with a bit of retconning) is as follows:

  • Weeks 1–2: Develop focal length constraint UI and libmv functionality.
  • Weeks 3–4: Complete focal length constraints, clean it up and do some testing.
  • Week 5: Commit focal length constraint. Start work on libmv side of multiview reconstruction.
  • Week 6: Implement libmv side of multiview reconstruction, including C API. Also, write some user documentation for focal length constraint.
  • Week 7: Submit midterm evaluation and continue implementation of libmv multiview reconstruction.
  • Week 8: Start making plans for the UI side of multiview reconstruction - pretty big changes are necessary. Week holiday begins during this week.
  • Week 9: Return from holiday. Finish plans for multiview reconstruction API.
  • Weeks 10–12: Implement UI for multiview reconstruction and kernel functionality to pass data to libmv.
  • Week 13: Tidy up solution for multiview reconstruction and do testing.
  • Week 14: Either continue improving multiview reconstruction or move on to do the beginnings of variable focal length reconstruction.
  • Week 15: Submit final evaluation.

Note that I changed how often I was committing during week 5. I had previously been submitting only code reviews, planning to commit to my branch when the code was ready. Since week 5, I have been committing as I go.

Documentation

Here's some important documentation that I have found useful for myself or that I think would be useful for others. Much of it has been transcribed from handwritten notes.

User documentation

Technical documentation

Development documentation

Wrap-up