User:Daniel: Difference between revisions

Contributing to open-source is a great way to improve myself, and has always been my plan to get to know how the work in real life is done. Participating Google Summer Code is going to enable me get an in-depth understanding of Google's spirit and culture. Work and communication with other software engineers and scientific computing scientist in the open-source community in an corporative way will allow me grow up fast.

My current PhD thesis work is the my biggest project so far. It's written in C++. I got to learn to get source code organized and its design pattern, even just the documentations plays very important role in maintenance and debugging efficiency.

I consider this a very basic exercise to warm me up before the dive into my real work on Image IO GNU/Octave GSoC 2015 project.

I started using Linux twelve years ago. My desktop evolves from Redhat, Federo, Gentoo, Ubuntu, Archlinux, Mint, until now I have two laptops, one is for normal work on Ubuntu, the other has Archlinux just for fun.

** Do you like to discuss changes intensively and not start coding until you know what you want to do?

Yes, I tend to gather enough information. Sometimes, more than enough.

** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind?

An enhanced image IO will be implemented in this GNU/Octave GSoC project. Most of the popular scientific image file formats will be adapted. TIFF (Tagged Image File Format)[1] as the de factor standard for scientific images, in many areas including biomedical imaging, astronomy and industry application, will be used as the sample data during the initial implementation.

*Many of the scientific images are encoded of 32 or higher bit of depth, that need to compile GM specifying quantum option, priori to compiling Octave, which per se could be an obstacle for general user to apply to their research for production/research publication purposes. With thus compilation, the high bit depth memory allocation is a waste for other smaller bit-depth image processing task. Building GM with high quantum means that images of smaller bit-depth will take a lot more memory when reading, but building it too low will make it impossible to read images of higher bit-depth. It also means that the image needs to always be rescaled to the correct range.

This project would implement better image IO for scientific file formats while leaving GM handle the others. Since TIFF is the de facto standard for scientific images, this should be done first. Among the targets for the project given in a timeframe manner are described below.

         Based on what I learn and continue learning to implement the Tiff class which is a wrap around libtiff, using classdef. To avoid creating too many private __oct functions, this project could also create a C++ interface to declare new Octave classdef functions.

         Flexible. Depending on progress and performance, could add test modules for all previous work, fix bugs, or make significant changes and utilize new ideas if necessary.