About

• Name: Pablo Lozano
• Studies: (BSc) Industrial Engineering (esp. Electronics) at Universidad Carlos III de Madrid. (MSc) Mathematical Engineering (Applied Mathematics) at Universidad Carlos III de Madrid. (BSc, only two years) Mathematics at Universidad Nacional de Educación a Distancia.
• Languages: Spanish (native), English (C1-C2), French (B2), German (A1), Russian (<A1).
• Platforms: Windows, Linux, MacOS, (~)BSD.
• Member of GISC.

Experience

I have experience in Python. I did my BSc thesis in socioeconmical networks modelling using Python, and I have been improving that working for the past year. I use Python for personal projects, too. I have also coded in C, and (very little) in C++. For the past year I have been using R a lot, for data analysis; and on my own, learning MATLAB for numerical computations. I am used to confront problems in which I do not have any expertise, so learning fast is very easy to me. Right now, I am very interested in the numerical approach of problems, so my goal will be developing algorithms for the Low-thrust Maneuvers and Mission objects

Proposal

For these three months in summer I want to develop algorithms for the three body problem. This issue has been open for 4 years, (and as it is marked as difficult) I think it will be a (fun) challenge for me. I have also worked with horrible code that had no user-friendly API, so I think it would be a great idea to develop one. I have no problem in working with plotting libraries for improving them, the documentation, as well as the visualization tools for other kinds of

Timeline

• Week 1: Revise the MSc Thesis, and refresh knowledge in Astrophysics.
• Weeks 2 to 3: Study of the mathematics behind the problem. Bibliography. Develop a plan for implementation of the algorithms and the API. Looking for possible ways of improving the algorithms in the MSc thesis.
• Weeks 4 to 8: Coding. Half time for API and the other half for algorithms would be ideal.
• Weeks 9 to 10: Unexpected problems appeared during past weeks! Time for fixing.
• Weeks 10 to 12: Testing with real examples. Final checking. Last minute improvements.

Sidenote: (One or two days a week are booked for writing/improving the documentation)

Extra information

I finish the second week of June, so I will available since then. The second and third weeks of August I will not be at home, but I will bring my laptop with me to continue programming. That means I will be working, but maybe I will delaying in replying to emails and messages.