GSoC 2013 - OpenCV DevZone

1

h1. GSoC2013OpenCVApplication

2

1

3

1

h3. Org ID?

4

1

5

1

OpenCV

6

1

7

1

h3. Org name?

8

1

9

1

Open Source Computer Vision Library (OpenCV)

10

1

11

1

h3. Description?

12

1

16

1

17

1

h3. URL?

18

1

19

1

http://opencv.willowgarage.com/wiki

20

1

21

1

h3. License?

22

1

23

1

New and Simplified BSD

24

1

25

1

h3. Backup Admin?

26

1

27

1

Vadim.Pisarevsky

28

1

29

1

h3. Ideas Page?

30

1

31

1

http://code.opencv.org/projects/gsoc2013/wiki/Gsoc2013

32

1

33

1

h3. IRC channel?

34

1

35

1

<pre>

36

1

#opencv on freenode

37

1

</pre>

38

1

39

1

h3. Mailing list?

40

1

41

1

http://tech.groups.yahoo.com/group/OpenCV/

42

1

43

1

h3. Why participate?

44

1

45

1

OpenCV has several full time contractors working on robotic applications and another paid group working on CUDA. However, the scope of the library is much larger and GSoC interns were invaluable last year in addressing other critical areas:

46

1

47

1

* getting a solid port of OpenCV to iOS,

48

1

* developing a QT based graphical interface, the old GUI was decidedly limited and stale

49

1

* creating an automatic interface to PASCAL VOC http://pascallin.ecs.soton.ac.uk/challenges/VOC/ (the main computer vision object recognition challenge)

50

1

* coding up a long time winning classifier in PASCAL VOC: Latent SVM

51

1

* features and support for feature tracking

52

1

* A set of tutorials

53

1

* A set of python examples

54

1

55

1

All the above things were out of scope of the paid work and had substantial impact on OpenCV, especially making it work with Mobile. In addition, 3 of the interns are now regular contributors. 2 more are occasional contributors.

56

1

57

1

Thus, why we are applying: We want to bring in a new generation of contributors and also to fill out areas where to don't have active development. We hope to gain pretty much a repeat of last year: Filling out new areas, perhaps co-authoring new papers and getting new regular contributors.

58

1

59

1

h3. Past summer of code, If so, challenges?

60

1

61

1

We participated in 2010 and 2011.

62

1

63

1

There were 12 interns total, 8 worked out. As a side note, I have now permanently hired 2 of the interns from the 2 past years of GSoC.

64

1

65

1

I mentored 2 interns developing working tutorials to vision functionality.  This started slowly since we had to decide on, set up an learn a new infrastructure. We ended up using a sphinx and then coding and explanation started. It worked out well and gave us a basic coverage of tutorials to get started with different aspects of the library, computer vision being a large field: http://opencv.itseez.com/doc/tutorials/tutorials.html .

66

1

67

1

Since we have a good supported port of OpenCV to Android from 2010, we went on to iOS in 2011.  This resulted in a complete port which we have been testing and refining. This is planned for official release in April. We will be giving a tutorial turned course ware on this at the Computer Vision and Pattern Recognition Conference in June http://www.cvpr2012.org/program-details/tutorials and we were extended an invitation to give this again at the European Conference on Computer Vision in October http://eccv2012.unifi.it/

68

1

69

1

We had someone working on developing samples for our Python port and this was very successful resulting in a large suite of example code under @.../opencv/samples/python2@. We did this to popularize the existence of this interface but I just started a company, Industrial Perception Inc, adding the eyes and brains to industrial robots and find myself making extensive use of these examples.

70

1

71

1

We had a failure with a student who was implementing OpenCL optimization for OpenCV. The student just wouldn't do much work, was not very responsive and was terminated at midterm. Ironically, other developers saw this start of this work and we now have a whole group developing OpenCL ports.

72

1

73

1

We had a student doing Structure from Motion. Again, this was a failure because, despite what looked like solid background, the student just wasn't up to the task. On the other hand, it got us in touch with 2 people at Google who have been developing libmv and they may contribute this.  We will put an intern on this effort this year if we get accepted.

74

1

75

1

We had students working on tracking which resulted in new methods of dense optical flow (Farnback optical flow). This has already been used by others for robotic visual odometry work.

76

1

77

1

What we learned is that anything near "state of the art" is best done only by top students who are doing current research in that area. We've done this a couple of time and those are some of the interns I ended up hiring. But, infrastructure type work (pascal samples, tutorials, code ports etc work well for the general student.

78

1

79

1

h3. Application Template?

80

1

81

1

We have a page at http://code.opencv.org/projects/gsoc2012/wiki/GSoCApplicationTemplate

82

1

83

1

+*Summary:*+

84

1

85

1

*Contact info:*

86

1

* Please provide:

87

1

** Your name

88

1

** A phone number

89

1

** An email address where we can reach you for daily communication.

90

1

*** If you have a website that discusses your research, work and/or coding, let us know.

91

1

92

1

*Requirements:*

93

1

94

1

* We are looking for people who have strong programming backgrounds, there is no time to "learn on the job".

95

1

** Most of the positions will require advanced ability and experience in *C++* and/or *Python*.

96

1

*** Exception might be for help working on the website itself

97

1

** Most of the projects require knowledge of computer vision techniques. If so, your application will not be accepted if you don't have such experience. These will be stated on the projects ideas page.

98

1

99

1

Again, you must meet the requirements -- it is not enough to "want" to work on computer vision, we have limited time and so we need people who already have the necessary background. If you lack this background, spend the next year getting the background and apply then, we intend to be back for GSoC 2013.

100

1

101

1

Students will be expected to ''meet'' with their mentors by email, skype or google chat once a week and to twitter at least 2x/day on their current coding activities

102

1

103

1

*Sample Code:*

104

1

105

1

** With your application: *Please send in some sample code that you are proud of and are prepared to answer questions on.*

106

1

** If you have other useful skills such as experience with code optimization, or knowledge of SSE, MMX, CUDA or especially development experience on Android or iPhone let us know.

107

1

108

1

*Courses Taken:*

109

1

110

1

List the courses that you have taken in:

111

1

** Math

112

1

** Computer programming, especially:

113

1

** Programming languages

114

1

** Data structures

115

1

** Web programming

116

1

** Data base

117

1

** Computer vision

118

1

** Engineering

119

1

h2. Work Experience

120

1

121

1

* List any work experience that you've had in

122

1

** software development and/or in

123

1

** computer vision.

124

1

125

1

*Open Source Experience:*

126

1

127

1

* If you have already contributed to other open source projects, please tell us what it was and when you did this.

128

1

129

1

*Which project you are interested in and and why you want to do it:*

130

1

131

1

* Please tell us which of the project ideas you are interested and why you want to work on that one.

132

1

* If you have your __own idea__, please describe it clearly and provide a timeline of progress towards that goal.

133

1

134

1

*References:*

135

1

136

1

* Please list 2 or 3 academic or programming work references.

137

1

138

1

h3. Mentor selection criterion?

139

1

140

1

# All mentors but one are known developers of OpenCV. The one who is not is a Professor of Computer Vision.

141

1

# All mentors have extensive computer vision and coding background.

142

1

# All mentors are people who have interns or students to manage every year, either in companies, academic settings or research groups.

143

1

144

1

h3. Disappearing students?

145

1

146

1

* We will try to prevent this by having mentors keep regular contact via skype meetings 1/week, twitter and email, but if it happens:

147

1

* We will post the orphaned project to our user group and offer a some of the mentor compensation (~$200) to someone who completes the project.

148

1

149

1

h3. What is your plan for dealing with disappearing mentors?

150

1

151

1

* First, this isn't expected since we only use mentors well known and trusted by the admin.

152

1

* We have 2 backup mentors who are on call to step in.

153

1

* Worst case, the admins will pick up the slack.

154

1

155

1

h3. Steps for interaction?

156

1

157

1

These techniques were used in 2010, 2011 and 2012 and worked well, so we'll use them again:

158

1

159

1

* Before the project, we will encourage them to post a detailed project plan to the user group (also socially committing them to complete).

160

1

* We will set up a 2x daily twitter feed for all the summer's development projects.

161

1

* Project results will go up on a youtube channel that will be posted to the large user group. This should provide a large amount of feedback.

162

1

* We hope to set up projects with 3 goals: Quick and turn around (within a few weeks they should have a baseline accomplishment), this will be followed by the main, reasonable summer goal, but there will also be a more comprehensive "stretch goal" that we will encourage them to complete, getting feedback and feature requests from the community.

163

1

* For the more advanced projects, we may write a paper with the students (we have an ICCV submission with one GSoC student from last year)

164

1

The best students may become interns at mentor's work places (which has happened 4 times now).

165

1

166

1

h3. New organization with someone to vouch for us?

167

1

168

1

No, we're an established org, 2010 and 2011.  Still, talk to Jean-Yves Bouguet "Jean-Yves Bouguet" <jyb atthat google>,  in the streetview group for a view.  Or talk to Sebastian Thrun "Sebastian Thrun" <thrun atthat google>, head of GoogleX who knows me (Gary Bradski) well.

169

1

170

1

h3. Vouch for younger orgs?

171

1

172

1

None that I know of. We make extensive use of Eigen, ffmpeg, and numpy.

173

1

----

174

1

[[Gsoc2013|Back]]

Login	Password