Editing User:Jacopo

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 14: Line 14:
 
IRC nick: '''jacopo''' ('''Jacopo''' on the wiki)
 
IRC nick: '''jacopo''' ('''Jacopo''' on the wiki)
 
; Which time zone do you live in? Will that change over GSoC duration?
 
; Which time zone do you live in? Will that change over GSoC duration?
Time zone: UTC+1. It won't change during SoCiS.
+
Time zone: UTC+2. 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?
 
; 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.
 
I usually prefer programming in the morning, but this is not a strict preference.
Line 30: Line 30:
 
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.
 
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.
 
; Please state the commits and patches you already contributed to Octave.
I collaborated to the NURBS toolbox, mainly by developing the 'kntremove' function.
+
kntremove function in the NURBS toolbox
  
 
== F: Feeling fine ==
 
== F: Feeling fine ==
Line 51: Line 51:
 
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.
 
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?
 
; 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 ==
 
== P: Prerequisites ==
Line 73: Line 72:
 
; Did you select a task from our list of proposals and ideas?
 
; 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 (http://wiki.octave.org/Summer_of_Code_Project_Ideas). I think it would be of interest for a wide variety of users and, more personally, I could find it useful for my PhD.
 
I would like to take care of the ODE solvers in Octave core (http://wiki.octave.org/Summer_of_Code_Project_Ideas). 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.
+
; Please provide a rough estimated timeline for your work on the task. ''This should include the GSoC midterms and personal commitments like exams or vacation ("non-coding time"). Optionally include two or three milestones you expect.''
My rough outline of the project is as follws:
 
 
# Asses the current state of the code after the latest modifications (http://geointegratorssocis.blogspot.de/). 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.
 
# Asses the current state of the code after the latest modifications (http://geointegratorssocis.blogspot.de/). 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 "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 "ode15i" solver for implicit differential equations and "decic" function to compute consistent initial conditions.
 
# Add "deval" function.
 
# Add "deval" function.
 
# Tests for the new code and documentation.
 
# 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]]
 
[[Category: Summer of Code]]

Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)