Editing User:Vishnuparammal

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 publish the changes below to finish undoing the edit.

Latest revision Your text
Line 35: Line 35:
* '''Java:''' Part of the college curriculum. Intermediate experience.
* '''Java:''' Part of the college curriculum. Intermediate experience.
**'''Trace_It:''' A software capable of plotting graph of any polynomial. Cross-platform implementation for Windows, Linux and Android. Used JavaFX for GUI.[https://github.com/Vishnuparammal/Trace_it]
**'''Trace_It:''' A software capable of plotting graph of any polynomial. Cross-platform implementation for Windows, Linux and Android. Used JavaFX for GUI.[https://github.com/Vishnuparammal/Trace_it]
* '''PostgreSQL:''' I have experience using PostgreSQL for database management.
* My best experience being in a development team was for my Java project, Trace_It. Earlier, I liked to 'code' my projects single-handedly (thinking it was better-off alone), but then working with a team gave me some new insights. I understood the importance of why and how tasks should be defined and divided among the team. I also got the gist of time and resource management and the inevitably important role they play in a team project. I learnt to use git with collaboration. We faced many merge conflicts. Even had to delete the repository and start over. There were suggestion, revisions, conflict of ideas, differences in coding style, but we worked through it all. I learnt many skills like coordination, communication, feedback, trust, focus and a sense of respect for opinions different than mine. After weeks of early-morning and late-night efforts, we completed the project. The feeling itself was rewarding for me.
* My best experience being in a development team was for my Java project, Trace_It. Earlier, I liked to 'code' my projects single-handedly (thinking it was better-off alone), but then working with a team gave me some new insights. I understood the importance of why and how tasks should be defined and divided among the team. I also got the gist of time and resource management and the inevitably important role they play in a team project. I learnt to use git with collaboration. We faced many merge conflicts. Even had to delete the repository and start over. There were suggestion, revisions, conflict of ideas, differences in coding style, but we worked through it all. I learnt many skills like coordination, communication, feedback, trust, focus and a sense of respect for opinions different than mine. After weeks of early-morning and late-night efforts, we completed the project. The feeling itself was rewarding for me.
*The biggest project I have done so far is the JavaScript-based Simulighter. It is a simple ray optics simulation software. I started it as a small project which was easy to code and maintain. But as more features got added, it became difficult to track code flow, debug errors, and understanding parts of code later on. The need for code organization and documentation dawned upon me. I had to refactor the code from scratch. I split up the HTML, CSS and JavaScript files, created functions, used classes and made a hierarchical folder structure, documented them, adopted the official coding style and made sure anybody who works on the code abides by them. Having worked on such a complex project has taught me that taking small corrective measures is important, or else it will be very difficult to manage later on. My role in the project:
*The biggest project I have done so far is the JavaScript-based Simulighter. It is a simple ray optics simulation software. I started it as a small project which was easy to code and maintain. But as more features got added, it became difficult to track code flow, debug errors, and understanding parts of code later on. The need for code organization and documentation dawned upon me. I had to refactor the code from scratch. I split up the HTML, CSS and JavaScript files, created functions, used classes and made a hierarchical folder structure, documented them, adopted the official coding style and made sure anybody who works on the code abides by them. Having worked on such a complex project has taught me that taking small corrective measures is important, or else it will be very difficult to manage later on. My role in the project:
Line 41: Line 42:
** Collision detection between light rays and objects
** Collision detection between light rays and objects
** Mathematical modelling and algorithm development for reflection
** Mathematical modelling and algorithm development for reflection
* Bugs
* Patches
** Submitted patches for Octave bug ( #57774 ). Now working on improving efficiency.[https://savannah.gnu.org/bugs/?57774]
**I have submitted a patch for the octave bug (#57774)[https://savannah.gnu.org/bugs/?57774].
** Submitted patch on Pythonic issue #44[https://gitlab.com/mtmiller/octave-pythonic/-/issues/44]
** Submitted patch on Pythonic issue #65[https://gitlab.com/mtmiller/octave-pythonic/-/issues/65]
** Reported Octave bug ( #58071 )[https://savannah.gnu.org/bugs/?58071]
** Reported Pythonic issue #71[https://gitlab.com/mtmiller/octave-pythonic/-/issues/71]
** Reported Pythonic issue #72[https://gitlab.com/mtmiller/octave-pythonic/-/issues/72]
** Reported Pythonic issue #73[https://gitlab.com/mtmiller/octave-pythonic/-/issues/73]
** Reported Pythonic issue #74[https://gitlab.com/mtmiller/octave-pythonic/-/issues/74]
** Reported Pythonic issue #75[https://gitlab.com/mtmiller/octave-pythonic/-/issues/75]
** Reported Pythonic issue #76[https://gitlab.com/mtmiller/octave-pythonic/-/issues/76]


== F: Feeling fine ==
== F: Feeling fine ==
Line 67: Line 59:
* I have a Windows 10 home with an Ubuntu 16.04 LTS VM and WSL.  
* I have a Windows 10 home with an Ubuntu 16.04 LTS VM and WSL.  
* I have my own laptop and a good internet connection at home.
* I have my own laptop and a good internet connection at home.
* I can access internet connection at any time.  
* I can access internet connection any time.  
* I can access my computer with my progressing work at any time.
* I can access my computer with my progressing work any time.
* This is my machine, I can access it anytime I want and install any software.
* This is my machine, I can access it anytime I want and install any software.


Line 77: Line 69:


== Y: Your task ==
== Y: Your task ==
I have chosen to work on the octave-pythonic package. The elaborated project proposal can be found here[https://docs.google.com/document/d/1Pe0nJOLzVgBc-Ui3Q3sm2lJapKI2GVURQapiOFD6QbQ/edit?usp=sharing]
* Did you select a task from our list of proposals and ideas?
 
** If yes, what task did you choose? Please describe what part of it you especially want to focus on if you can already provide this information. ''Please also wiki-link the page for your elaborated proposal here.''
* Timeline
* 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"). If possible, include two or three milestones you expect.''
**04 May - 31 May: Build User Guide and FAQ sections during the community bonding. Try to solve Octave bugs necessary for improving Pythonic. Discuss implementation details of  ideas and finalize it
** 01 June - 20 June: Implement pyenv to change default environment of the Python interpreter
** 21 June - 25 June: Documentation, writing tests and refining the code through community feedback
** 26 June - 15 July: Improve slicing and indexing of Python objects
** 16 July - 20 July: Documentation, writing tests and refining the code through community feedback
** 21 July - 05 August: Manage Python -  Octave  type conversion
** 06 August - 10 August: Documentation, writing tests and refining the code through community feedback
** 11 August - 20 August: Add test scripts that exercise various Python libraries
** 21 August - 31 August: Clean up, final documentation and submission
 
* Milestones:
** Create a User Guide with examples.
** Implement pyenv() function
** Improve slicing and indexing of Python objects and make it MATLAB compatible
** Solve  issues with Octave - Python type conversions
** Build test scripts for Python libraries
 
[[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)