User:Nvs-abhilash

From Octave
Revision as of 21:52, 19 March 2017 by Nvs-abhilash (talk | contribs) (→‎O: Only out of interest: completed only out of interest ection)
Jump to navigation Jump to search

Public application

A: An introduction

  • Please describe yourself in three sentences, one of them regarding your current studies.
    I am NVS Abhilash, I love mathematics and code.
    I have a deep interest in Machine Learning and A.I. and currently, I am studying Computer Science and Engineering, specializing in Big Data and ML.
    • Which languages do you speak?
      I can speak and communicate well in English and Hindi.
    • What's your overall background?
      I am currently an undergraduate in Computer Science and Engineering (Third year / Junior).
      My area of specialization is Big Data and Machine Learning.
      Some of the courses in my current semester include Information Retrieval, Internet of Things and Digital Image Processing.
  • Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
    I think Google Summer of Code is a great opportunity for me to jumpstart my presence in the open source community.
    I hope to gain knowledge and experience working in a professional working environment and meet new people in the process and gain some reputation in the open source community.
    For the <3 of < />
    • Please also describe your previous experience with the GSoC, if any.
      This is my first experience with GSoC.
  • Why are you choosing Octave?
    Octave tries to become the open source alternative for MATLAB, and I believe in this ideology. Maybe that's why I like using Octave.
    Also, Octave has a great community of developers. They are welcoming and motivating.

C: Contact

  • Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave.
    nick: nvs
  • Which time zone do you live in? Will that change over GSoC duration?
    I live in UTC+05:30.
    No, the time zone will not change over GSoC duration.
  • Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?
    I can work from 4:30 AM - 11:30 AM (in UTC+0) PM (in UTC+0)
    I am always ready to work more than the above time maybe also from 1:00 PM-4:00 PM(in UTC+0) if my project needs that.

E: Coding experience

This part is one of the more important ones in your application. You are allowed to be as verbose as you want, as long as you stay on topic ;-)

  • Please describe your experience with C++, Octave or Matlab m-scripts, OpenGL and Qt.
    C++
    • I have 5 years of coding experience in C & C++. I have a good idea of classes and Object Oriented Programming in C++.
    Octave or Matlab m-scripts
    OpenGL and Qt
    I have no prior experience with either of them. But I am willing to learn them if my project demands it.
  • Please describe your experience with other programming languages.
    Python
    • I have a fair idea of basic Python syntax. I have also learned to use some mathematical libraries like numpy and pandas.
    • I have started learning the syntax and features of sympy, as it is helpful for the GSoC project.
  • Please describe your experience with being in a development team.
    I am new to the open source community.
  • Please describe the biggest project you have written code for and what you learned by doing so. Also, describe your role in that project over time.
    • Algorithms for Graph-based trust models in Online Social Network: In this project, we had a large dataset of social users and we were expected to design and implement an Algorithm to tackle the scalability problem in recommender systems.
    • My contributions were to implement the graph partitioning algorithm in C++.
  • Please state the commits and patches you already contributed to Octave.
    I have contributed mostly to the Symbolic Package, I have also contributed to Pytave and Octave core:
    • Symbolic package contributions:
    1. sympref: add support to restore settings from a structure: [1], [2], [3]
    2. @sym/prevprime: added prevprime: [4], [5],[6]
    3. sympref: removed references to whichpython: [7]
    4. isequal: added isequal for @symfun class. (fixes #740): [8],[9], [10], [11], [12], [13], I got to learn a lot from this one, all thanks to Colin and Abhinav.
    5. @symfun/isequaln: implemented isequaln to support NaN's equality in @symfun: [14]
    • Pytave contributions:
    1. * @pyobject/methods.m: OPTION to view private methods added (fixes issue #22): [15]
    • Octave core contributions:
    1. * data.cc (Fisinteger): Add BIST tests: [16]

F: Feeling fine

  • Please describe (in short) your experience with the following tools:
    • IRC and mailing lists
      I am comfortable using the mailing list and IRC. These are my interactions in the mailing list: Posts
    • Mercurial or other source code management systems
      I am very comfortable using git. I have started learning Mercurial and do understand the basics of generating a patch in Octave.
    • Mediawiki or other wiki software
      I started using Mediawiki when I started writing this application. I am comfortable in writing wiki pages.
    • make, gcc, gdb or other development tools
      I am very comfortable in using make tool, gcc, and gdb. And I am always pumped up in learning new tools if my project demands for it (or even just out of curiosity ;P )
  • What will make you actively stay in our community after this GSoC is over?
    I see lots of places I can help. I am also interested in the Convolutional Neural Networks (CNNs) package. I would love to work upon that after my GSoC.

O: Only out of interest

  • Did you ever hear about Octave before?
    Yes, I have heard of GNU Octave before.
    • If so, when and where? How far have you been involved already?
      I started using Octave for my online Machine Learning Course by Andrew Ng in Coursera.
  • What was the first question concerning Octave you could not find an answer to rather quickly? Of course more than one question can be stated. We try to improve based on this each year! Includes learning how to use it, code, website, GSoC application, …
    I think complete steps to build Octave from source. The reason for that is that there is not much in the Octave docs. And there are more than one wiki describing the same things with different ways. It might be better to always update the Octave docs about the installation instruction. Here is what the octave docs shows now: link. Apart from this the Octave manual has been very helpful with useful examples to understand the concepts.

P: Prerequisites

  • Please state the operating system you work with.
    • If you have access to more than one, please state them and the conditions under which you are granted this access.
  • Please estimate an average time per day you will be able to access
    • an internet connection
    • a computer
    • a computer with your progressing work on
  • Please describe the degree to which you can install new software on computers you have access to.

S: Self-assessment

  • Please describe how useful criticism looks from your point of view as committing student.
  • How autonomous are you when developing:
    • Do you like to discuss changes intensively and not start coding until you know what you want to do?
    • 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?

Y: Your task

  • 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.
    • If you apply for a task you have added yourself instead, please describe this task, its scope and people you already talked to concerning it. What field of tasks did you miss on the list?
  • 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.