Student Application Template

To fill this in, copy the source text. Please don't rename the template.

This is a suggestion for the kind of information we'll find useful from students in their submissions. Remember -- you're going to be committing to several months' work. The more information and planning you can provide up-front, the more we (and Google!) will have to go on when we're ranking your application. Do not forget adding your submission at SummerOfCode2015/StudentApplications

My name is Floris and I am 20 years old. Currently studying at the Computer Science department of the Ovidius University, I have been passionate about coding since high school and ever since, I have tried my hand at many and various projects. I had been jumping between coding games, web applications, multi-platform applications and other things, but a couple of years ago I was charmed by the Open Source community and finally found my focus. That focus that I found with Open Source helped me develop my current set of skills.

Last year I was a Debian GSoC student under the guidance of Sune Vuorela (svuorela) and Aleix Pol (apol). Even though I had previous experiences coding and sending patches, they taught me and helped me take things to the next level. Things that I later applied to my research. These last 2 years I have been learning about GPUs and general computing on them using CUDA and ?OpenCl. My research culminated this year by using my knowledge to make an extremely fast algorithm for estimating parameters of non-linear differential systems. As fun as that sounds, I would really like to use my knowledge in Computer Vision and Natural Motion Interfaces.

I chose this project because it aligns with my current skill set and what I want to learn and get into. I enjoy working with low-level interfaces and I believe I can make an important contribution to Debian!

I expect to be putting about 7-8 hours per day, 5 days a week; consider the mentions from the next point.

1. Community Bonding Period (until 25th of May):

2. Work Period 1 (Daemon synthesizing system in place, use PSMove example provided by Klee for testing):

3. Work Period 3 (Support for Hydra (two 6-axis controllers, operating in unison), start implementing support for input/output devices):

4. Work Period 4 (Finishing up):


Other things worth mentioning:
I will be using C++ with DBus for the daemons. Libevdev will be used to map the input events to normal mouse events, arbitrary interpretation for each plugin (device) will be used for the synthesizing of output of the virtual device ( accessible, for example, on /dev/PSMove ). Talking to Klee made me realise the need for standardization and for it to "just work", so I will try to keep the output for the virtual device as formatted to a chosen standard as possible (i.e. in order x/y/z/pitch/roll/yaw).

Some of my other experiences/projects: