Jump to navigation Jump to search


1,371 bytes removed, 11:51, 18 March 2014
** 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?(NO)
== Y: Your task ==
* I have selected two tasks the following task from GSoC projectspage[].** Implementation of Geometric integrators for Hamiltonian Systems. I have good experience in m-file scripting and can read mathematics papers comfortably. These Geometric integrators are essentially used for Discrete element methods and a number of Physics computation methods. I am studying the methods listed on the projects page and will come up with a list of tasks once I get familiarized with them. ** I would like to contribute to the mapping package, specifically the implementations of functions missing in Coordinates, Geodesy, Projections and Data AnalysisStandard I/O. The list of functions in the map toolbox for Matlab are listed here[]. I have already contributed the 3D coordinate functions to this package[].I will prefer to work on mapping package if a mentor is interested in it and is available.
* '''Rough time estimates:'''
* For Mapping Package:
** Week 10 to Week 12 (July 30 to August 18): Write tests and Documentation. Code clean up and finalization. End of GSOC.
** After GSOC: Maintenance of Mapping Package in Octave Forge.
 * For Implementation of Geometric Integrators for Hamiltonian Systems:** Week 0, Week 1 (May 19 to June 2): To work with mentor on selecting the list of methods that need to be implemented and to study the mathematics of these methods in depth, Browsing through the Octave code to learn more. ** Week 2 to Week 4 (June 3 to June 23): Start working on the essential methods and to finish the first half of the to do list that I will be creating during the community bonding period.** Week 5 to Week 8 (June 24 to July 22): Complete work on all the remaining methods. Finish the basic m-file scripts for all the methods intended to be implemented by end of week 7. ** Week 9 (July 23 to July 29): Fixing bugs, code clean up and Making the entire code Matlab compatible. ** Week 10 to Week 12 (July 30 to August 18): Write tests and Documentation. Code clean up and finalization.
I have planned a 25 to 30 hour work schedule for every week.


Navigation menu