Jump to navigation Jump to search


1,229 bytes added, 03:56, 14 May 2014
IRC nick: '''jacopo''' ('''Jacopo''' on the wiki)
; Which time zone do you live in? Will that change over GSoC duration?
Time zone: UTC+21. It won't change during SoCiS.
; Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
I usually prefer programming in the morning, but this is not a strict preference.
My biggest project so far was my Master thesis. I worked on the coding of a C++ library similar to GeoPDEs and then with GeoPDEs itself to solve electromechanical problems. I am continuing this work for my PhD.
; Please state the commits and patches you already contributed to Octave.
kntremove function in I collaborated to the NURBS toolbox, mainly by developing the 'kntremove' function.
== F: Feeling fine ==
I heard at the same time about Octave and Matlab around 2007 when I started university. However until a couple of years ago I just used Matlab since it was the common choice at Politecnico di Milano.
; What was the first question concerning Octave you could not find an answer to rather quickly?
I don't recall any particular question that I had problem in finding an answer to. I however am beginning to think that the best source of information is the community itself. I am not yet involved a lot, but I can see that for each problem asked there is always someone ready to give some help.
== P: Prerequisites ==
; Did you select a task from our list of proposals and ideas?
I would like to take care of the ODE solvers in Octave core ( I think it would be of interest for a wide variety of users and, more personally, I could find it useful for my PhD.
; Please provide a rough estimated timeline for your work on the task. ''This should include My rough outline of the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). Optionally include two or three milestones you expect.''project is as follws:
# Asses the current state of the code after the latest modifications ( Ensure that the functions "odeset", "odeget" and (at least) "ode45" are well tested and Matlab-compatible so that they can be added to Octave-core. If necessary add the missing options.
# Add "ode15s" solver for stiff differential equations and DAEs.
# Add "ode15i" solver for implicit differential equations and "decic" function to compute consistent initial conditions. The implementation of this two solver could probably exploit IDA form the sundials library.
# Add "deval" function.
# Tests for the new code and documentation.
Point 1 should not take too long: I checked part of the code and already added some of the missing tests. I believe it is of great importance that the code should maximize compatibility with proprietary software since they are such common functions. From here it will be possible to build the new solvers.
The coding of the solvers (point 2-3) will probably be the most challenging task and it will involve getting to know IDA and/or other already existing code.
The creation of function "deval", once again, goes in the direction of making the package as much compatible as possible with Matlab.
Point 5 is pretty straightforward, but really necessary since I already found a lot of discrepancies between the documentation and the current state of the code.
I don't have any particular restriction for the actual coding period. If the start and end of the project should shift it shouldn't be a problem for me.
[[Category: Summer of Code]]


Navigation menu