Editing User:Gouzouni

== A: An introduction ==

* ''' Please describe yourself in three sentences, one of them regarding your current studies. '''
* '''  Which languages do you speak? '''
* '''  What's your overall background? '''
** My name is ''' Georgios Ouzounis '''. I am a fourth year undergraduate student in the School of Electrical and Computer Engineering in Aristotle University of Thessaloniki, Greece [http://ee.auth.gr/en/ link ] (engineering bachelor includes 5 years of studies in my country). I love computer programming, mathematics and engineering and I hope to be able to stay involved with them through my whole life. My native language is Greek and I can also use English very well. As the title of my School indicates, my current field of study is Electrical and Computer Engineering involving subjects related to electrical and electronic circuits and also subjects related to computers and engineering such as control theory, analog and digital signal processing, computer networks etc...

* ''' Why do you want to participate in the Summer of Code? What do you hope to gain by doing so? '''
** ''' Please also describe your previous experience with the SoC, if any. '''
** My application for the Google Summer of Code 2014 on GNU Octave was rejected so applying on SOCIS is my second attempt on a program like this. Applying for participation in the Summer of Code in Space(SOCIS) is my first step towards real world software development. Until now I have been programming mainly for university projects so what I hope to gain from SOCIS is experience and knowledge on how to create software to be used by others.

* ''' Why are you choosing Octave? '''
** The past two years I had to deal with many university projects that required the use of software like Matlab or Octave. Using both of them I came
to realize the power of such tools. That is the main reason why I chose Octave. I have actually wanted to contribute to Octave long before finding SOCIS but never found the nerve to try it until now.

== C: Contact ==

* ''' Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. We really want unique nicks.

* ''' Which time zone do you live in? Will that change over SOCIS duration?'''

* ''' Please state the timeframe (in UTC+0) when you feel most comfortable working during SOCIS. Where are your time buffers?'''
My nick in IRC, wiki.octave.org and the patch tracker is '''gouzouni''' ('''Gouzouni''' on the wiki). The time zone in my country is UTC+3
(Eastern European Time Zone) and this is not going to change during the whole SOCIS period. I usually code around 5.00 to 11.00 but time is not
really a matter. Evenings are good as well!

Other contact informations are my e-mail '''geoconstructor625@gmail.com''' and my Facebook account [https://www.facebook.com/georgios.ouzounis.3?ref=tn_tnmn Georgios Ouzounis]. You can also find me in Skype under the name " '''Georgios Ouzounis''' ".

== E: Coding experience ==

* ''' Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.'''
I have been writing code in C and C++ for the last 4 years both for university projects and personal use. I have a very good understanding of these languages. I am well aware of the object oriented programming concept and I can use debuggers such as GDB well. As far as Octave m-scripts are concerned, I have been writing such code for the past 2 years mostly for university projects. I have written scripts for a wide spectrum of subjects such as optimization, image and signal processing, system recognition, control systems, machine learning and mathematics. I have very good knowledge of mathematics which helps in many ways such as writing vectorized code which is much faster than using loops. I have no experience using OpenGL or Qt.

*''' Please describe your experience with other programming languages.'''
Other programming languages that I use frequently and I am comfortable with are Java and Assembly. I have also used Python for some time. I am comfortable with using PThreads, Cuda and MPI and I am comfortable with parallel computing in languages such as Java, C++ and Matlab/Octave. 

* ''' Please describe your experience with being in a development team. ''Do you have experience working with open source or free projects?'''''
I have no experience working with open source or free projects. I have good experience with being in a development team but only for small projects at the university, nothing as large as Octave. 

*''' Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time.'''
The biggest project I have written code for is an Android application, a calculator, I developed last summer. It is about 2500-3000 lines of code. What I have mainly learned from that is if the small parts are well developed and documented then the big ones can be done quite easily. On the other hand, not being cautious in the first steps is going to be a big trouble on the later stages of a project. I was the only one working on that project so I had no specific role.

* ''' Please state the commits and patches you already contributed to Octave.'''
Until now I have committed the patches [https://savannah.gnu.org/patch/?8379 #8379], [https://savannah.gnu.org/patch/?8383 #8383] and [https://savannah.gnu.org/patch/?8384 #8384]. The first one includes the uencode and udecode functions of the signal package, the second one includes the peak2peak function of the signal package and the third one includes the shiftdata and unshiftdata functions of the signal package.

== F: Feeling fine ==
* I am new to IRC but I have been using mailing lists for a while. I am also new to Mercurial and generally source code management systems. I have been using wiki sites before ( wikipedia and other ) but this is the first time I am modifying one. I am comfortable with make, gcc and gdb but I wouldn't say I am a master of the last one. 

* I intent to stay in Octave's community after SOCIS is over no matter if I get picked to participate or not. I like programming and Octave's nature (mathematics, digital and analog signals etc...) is what I am comfortable working on. I would love to continue contributing.

== O: Only out of interest ==
* My access to Matlab was(and still is) limited only inside the university campus so if I wanted to work my projects at home and not stay until late in the campus I had to use other software. That is how I found out about Octave two years ago. I have been using it for the last two years and another 
reason why I want to contribute to it, is to help make it bigger. What gave me a hard time was the lack of a fullest symbolic package, that is why I want
to work on it sometime after SOCIS.

* A thing that I had a little trouble finding an answer to how to contribute to Octave's development but I guess that was due to the fact that I had no idea what a source code management system is.

== P: Prerequisites ==
* For the past year I have been using Ubuntu 13.10(13.04 before) and before that I used windows 8. I have both these operating systems installed
on my laptop and I have root access to both of them.

* I have a 24/7 access on an Internet connection, a computer and a computer with my progressing work on.

* I am free to install any new software on my laptop.

== S: Self-assessment ==

*''' Please describe how useful criticism looks from your point of view as committing student.'''
After realizing that I was not born a good programmer (that was a long time ago :P ) I begun to appreciate any criticism. It's not that I like to be
told that I am wrong, but if I am, I try my best to correct my mistakes.

*''' How autonomous are you when developing?'''
When I get a project on my hands I usually have a good deal of questions at first. Mostly clarification questions. After a while and when I get to
understand what is actually needed I can say I am pretty autonomous both in working on the project and solving the new questions coming up. What I
like though, is a frequent feedback on whether I am on the right course or not. I hate what some of my university professors do, giving me a project
and meeting me again a month after to check on what level I am. I like a frequent, say every 3 or 4 days, communication with other members on the project
or the mentor in order to check if everything is ok. It's the more frequent the contact is the better the outcome will be.

*''' Do you like to discuss changes intensively and not start coding until you know what you want to do?'''
My answer is yes, I do like to discuss changes intensively and not start coding until I know what I want to do. I don't expect to have everything figured out from the beginning but I like to have a decent schedule before starting writing code.

* ''' 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?'''
Yes I do. I like to try many different ways of doing something in order to find the best. Since how will it turn out is not clear at the beginning,
throwing work away, even if it is a week's work, is a risk I am willing to take.

== Y: Your task ==
* The task I have chosen is the implementation of [http://wiki.octave.org/Summer_of_Code_Project_Ideas#High_Precision_Arithmetic_Computation "High Precision Arithmetic Computation"]. The part that I would like to focus on would be the completion and test of the multi-precision class along with the implementation of several linear algebra algorithms which will support the use of multi-precision inputs.

* A rough estimated timeline for my work on the task would be :

'''Beginning until the end of first month ( June 1st - June 30th )'''

Include support for array and complex numbers on the already existent version of the multi-precision package.

Implement upclassing on operations involving objects of the multi-precision class.

Milestone 1 : End of first month : The goal at this moment will be to have a fully functioning multi-precision class, including array, complex number support and upclassing. 

All deliverables will be tested and debugged during this period.

''' (July 1st - July 4th) '''

Testing, documentation, further debugging.

''' (July 5th - July 15th)

Break. As stated below, my examination period starts at June 10th and end at July 4th, so I would like to have a 10 days break in order to rest
and clear up my mind. 

'''( July 16th - August 15th )'''

Continue with the algorithms' development. Given the four days per algorithm estimation, about 7 - 8 different algorithms should be created during this period.

Milestone 2 : The goal for the end of this period will be to have a fully functioning multi-precision class ( or new basic numerical type ) and also a big enough arsenal of algorithms upon it.

''' (August 16th - August 31st) '''

Wrapping up the project. Finish what is left to be done. Documentation, debugging and testing.

A list of algorithms that will be implemented ( not necessary in this order ) to support multi-precision objects is given below :

Singular Value Decomposition ( SVD ), 
QR factorization,
Cholesky factorization ( chol ), 
Inverse matrix computation, 
Eigenvalues and eigenvectors calculation, 
Solving linear systems, 
Root of non-linear function finder ( fzero ), 
Minimum value finder ( fmins ). 

''' Development methodology '''

A rough schedule that will be followed ( not necessarily in this order ) while developing the above algorithms will be :

Step 1 : Check if there is some library based on GMP or MPFR implementing any of those algorithms and if this can be embedded on Octave.

Step 2 : Study Octave's already implemented for double precision algorithms and see if they can be re-formed in order to support multiple precision.

Step 3 : Check if there is any Fortran code implementing any of the required algorithms and if it can be used to add support for multiple precision.

Step 4 : Implementing the algorithm from the scratch. This will be the final choice, and will be done only if there is no other way to implement an algorithm.

Imponderables like illness, bad days, Internet going down globally and such stuff are considered by the above schedule, this is why a precise estimation of days per algorithm is not given.

The only commitment I have for the summer is my university exam period which starts at June 10th and ends at July 4th. Despite that, I will keep coding during these days for about 5 - 6 hours everyday as stated above. Studying for the exams will be done the other hours of the day.

== N: News ==

I studied Octave's code for matrices and arrays and created the skeleton for adding matrix functionality on the [http://hg.code.sf.net/p/octave/multi-precision multi-precision] package. The skeleton was uploaded as a patch here [https://savannah.gnu.org/patch/?8429 8429].

The matrix support for the [http://hg.code.sf.net/p/octave/multi-precision multi-precision]  package is planned to be implemented by 2 classes. 

1) MpvNDArray class, subclass of MArray<octave_mp>, implementing N-dimentional arrays of multiple precision objects ( octave_mp objects ). 

2) octave_mpv_matrix class, subclass of octave_base_matrix<MpvNDArray>, implementing matrices of multiple precision objects.

The goal is to imitate the implementation of [http://octave.sourceforge.net/doxygen/html/dd/d24/classFloatNDArray.html FloatNDArray]  and [http://octave.sourceforge.net/doxygen/html/df/d1e/classoctave__float__matrix.html octave_float_matrix] classes, and adjust it to work on multiple precision objects.

== P: Private application submitted on SOCIS website ==

* '''First Name (mandatory):'''
Georgios
* '''Last Name (mandatory) :'''
Ouzounis
* '''Email contact (mandatory) :'''
geoconstructor625@gmail.com
* '''Personal website :'''
* '''Date of birth (mandatory) :'''
12/09/1992
* '''Nationality or nationalities (mandatory) :'''
Hellenic
* '''Institution (mandatory) :'''
School of Electrical and Computer Engineering Aristotle University of Thessaloniki
* '''Institution location (mandatory) :'''
Greece
* '''Mentoring organization (mandatory) :'''
GNU Octave
* '''Project proposal (mandatory) :'''

* ''' A: An introduction '''

My name is Georgios Ouzounis. I am 21 years old and I am a fourth year undergraduate student at the School of Electrical and Computer Engineering at Aristotle University of Thessaloniki, Greece ( http://ee.auth.gr/en/ ).

** Previous Experience :
Summer of Code in Space (SOCIS) is my second attempt to participate in a program like that after my application getting rejected at the Google Summer of Code 2014. I have been using Octave for the last two years and I have written many scripts for university projects on fields like signal processing, system identification, numerical analysis, electronic circuits etc... As far as my experience on C / C++ is concerned, I have been using these languages for the last four years, writing programs for university projects and personal use.

** A time frame :
I usually code around 5:00 to 11:00 ( UTC+0 ) and I plan on spending about 5 - 6 hours daily working on SOCIS project including Saturdays and Sundays. I will also be able to join the IRC channel during my coding hours.

The only commitment I have for the summer is my university exam period which starts at June 10th and ends at July 4th. Despite that, I will keep coding during these days for about 5 - 6 hours everyday as stated above. Studying for the exams will be done the other hours of the day. I also plan
to have a 10 days break right after the end of my examination period (5th - 15th of July) to clear up my mind and rest.

** Describing my English :
I can use English very well both in writing and speaking, so there will not be any problems regarding communication with other community members. I have a C1 level certificate for the English language.

* ''' C: Contact '''

My nick in IRC and the patch tracker is gouzouni and my nick on wiki.octave.org is Gouzouni.

My e-mail address is geoconstructor625@gmail.com .

My country's time zone is UTC+3 ( Eastern European Time Zone ), and that is not going to change over SOCIS duration.

The instant message networks I daily use are Skype (name Georgios Ouzounis) and Facebook (name Georgios Ouzounis). I have no particular preference on the way the communication is done. E-mails are good for me, so do Facebook and Skype. Whatever suits the other side.

In case of inability to connect on the internet, my mobile's phone number is +30 6972173897.


* ''' S: Self-assessment '''

From my university experience and my fellow students comments I would say that I can give constructive advice. Many of my fellow students come to me for advice when they are having a problem with a project they are working on. I guess I could say that I can also receive advice, even though I support my opinion unless there are strong arguments that I am mistaken.

As far as sorting useful criticisms from useless ones is concerned, I would say that I can generally sort useful information from useless so I am good at picking what is needed and leaving the rest.


* ''' Y: Your task '''

The project I would like to work on is "High Precision Arithmetic Computation".

** Addressing the problem :
There are numerous real world examples where double precision numbers, used by Octave, are not enough. Modelling exponential behaviours as found in semiconductor materials and electrical circuits (diodes and transistors) is an example. All of them, end up to solving linear systems of equations where the corresponding matrices are mathematically invertible but numerically not, due to large ratio between their first and last singular values.

** Proposing a solution :
A solution of the above problem would be the creation of an interface numerical over GNU MPFR (http://www.mpfr.org/) which is (quoting the site) "a C library for multiple-precision floating-point computations with correct rounding". This interface will give the ability to the user to use numbers with arbitrary precision, limited of course by the machine's internal memory. After having that interface (or numerical type) created to support matrices and complex numbers the next step would be the implementation of certain algorithms to work with those arbitrary precision numbers. Some examples of such algorithms would be computing inverse Matrix, Solving linear systems, calculating eigenvalues etc...

** Expected output :
The amplification of the already existent multi-precision package on the Mercurial repository (http://hg.code.sf.net/p/octave/multi-precision) in order to support matrix and complex number computations ('+', '-', '/', '*', 'determinant' and 'subsref') and also support the algorithms stated above.

The existence of this package for Octave can be a useful tool for it's users and for its developers too. More users will be using Octave for their computational needs and so Octave's community will grow. The outcome of this project could be combined with packages like the Electronic Circuit Simulator and the Signal package to make them more powerful. Prompted by my experience in my university, I can say it could be also useful in robotics where high precision is needed.

** Why choose me :
The first answer would be, because I really want to. This is not enough on its own but it's a good start. My programming experience is described at the beginning of this application under the label "Previous Experience" and also on my public application at wiki.octave.org/user:Gouzouni . Moreover, I have a very strong mathematical background including but not limited to linear algebra and numerical analysis. This background gives me the ability to translate a problem written in words to a mathematical problem and then use a computer to solve it. I can also easily understand any linear algebra algorithm or concept.

What I hope to gain from this project is experience. It would be my first time to join an open source community and I know there are a lot to learn. In addition, I hope to get a very good idea of how things are done on a project of that scale.

** A rough schedule of my work :

A rough estimated timeline for my work on the task would be :

'''Beginning until the end of first month ( June 1st - June 30th )'''

Include support for array and complex numbers on the already existent version of the multi-precision package.

Implement upclassing on operations involving objects of the multi-precision class.

Milestone 1 : End of first month : The goal at this moment will be to have a fully functioning multi-precision class, including array, complex number support and upclassing.

All deliverables will be tested and debugged during this period.

'''(July 1st - July 4th)'''

Testing, documentation, further debugging.

'''(July 5th - July 15th)'''

Break. As stated above, my examination period starts at June 10th and ends at July 4th, so I would like to have a 10 days break in order to rest and clear up my mind.

'''( July 16th - August 15th )'''

Continue with the algorithms' development. Given the four days per algorithm estimation, about 7 - 8 different algorithms should be created during this period.

Milestone 2 : The goal for the end of this period will be to have a fully functioning multi-precision class ( or new basic numerical type ) and also a big enough arsenal of algorithms upon it.

'''(August 16th - August 31st)'''

Wrapping up the project. Finish what is left to be done. Documentation, debugging and testing.

A list of algorithms that will be implemented ( not necessary in this order ) to support multi-precision objects is given below :

Singular Value Decomposition ( SVD ), QR factorization, Cholesky factorization ( chol ), Inverse matrix computation, Eigenvalues and eigenvectors calculation, Solving linear systems, Root of non-linear function finder ( fzero ), Minimum value finder ( fmins ).

Development methodology

A rough schedule that will be followed ( not necessarily in this order ) while developing the above algorithms will be :

Step 1 : Check if there is some library based on GMP or MPFR implementing any of those algorithms and if this can be embedded on Octave.

Step 2 : Study Octave's already implemented for double precision algorithms and see if they can be re-formed in order to support multiple precision.

Step 3 : Check if there is any Fortran code implementing any of the required algorithms and if it can be used to add support for multiple precision.

Step 4 : Implementing the algorithm from the scratch. This will be the final choice, and will be done only if there is no other way to implement an algorithm.

Imponderables like illness, bad days, Internet going down globally and such stuff are considered by the above schedule, this is why a precise estimation of days per algorithm is not given.

'''Additional notes : '''