Editing User:Enricobertino
Jump to navigation
Jump to search
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 11: | Line 11: | ||
*:It is an interesting project, followed by competent mentors and supported by a great organization. I can not ask for more for entering the open-source world :) | *:It is an interesting project, followed by competent mentors and supported by a great organization. I can not ask for more for entering the open-source world :) | ||
** Please also describe your previous experience with the GSoC, if any. | ** Please also describe your previous experience with the GSoC, if any. | ||
**: | **:First time | ||
* Why are you choosing Octave? | * Why are you choosing Octave? | ||
*:I am quite a fan of open source projects, open innovation and expertise sharing. In recent months I have been working on a Python framework for natural language processing and I want to open it asap. I like this same spirit under the Octave project. | *:I am quite a fan of open source projects, open innovation and expertise sharing. In recent months I have been working on a Python framework for natural language processing and I want to open it asap. I like this same spirit under the Octave project. | ||
== C: Contact == | == C: Contact == | ||
Line 19: | Line 19: | ||
*:nick: '''enricobertino''' | *:nick: '''enricobertino''' | ||
* 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? | ||
*:UTC+1, | *:UTC+1, it will not change | ||
* 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 code in the time span | *:I usually code in the time span 8.00 - 19.00 (UTC+0) | ||
== E: Coding experience == | == E: Coding experience == | ||
Line 30: | Line 30: | ||
*:I’m very familiar with Python and R, the two most common languages for statisticians. I have also some experience in Java and PHP. | *:I’m very familiar with Python and R, the two most common languages for statisticians. I have also some experience in Java and PHP. | ||
* Please describe your experience with being in a development team. | * Please describe your experience with being in a development team. | ||
*: | *:I’m currently working in a tech startup and I have to collaborate with other 5 developers. We have structured the code from scratch and the process can be likened to a package development. | ||
* 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. | * 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. | ||
* | *:When I was at INRIA in France, I implemented a Godunov’s scheme to resolve stochastic conservation laws in modeling highway traffic. In the application of the algorithm I also had to deal with computing infrastructures and data integration problems. | ||
* Please state the commits and patches you already contributed to Octave. | * Please state the commits and patches you already contributed to Octave. | ||
*: | *:A patch for nnet package. I’m currently working on some Pytave bugs. | ||
== F: Feeling fine == | == F: Feeling fine == | ||
Line 44: | Line 41: | ||
**:I am starting to discover the Octave “ecosystem” and to be comfortable using the mailing list and IRC | **:I am starting to discover the Octave “ecosystem” and to be comfortable using the mailing list and IRC | ||
** Mercurial or other source code management systems | ** Mercurial or other source code management systems | ||
**:I’m very familiar with Git | **:I’m very familiar with Git, just started with Mercurial | ||
** Mediawiki or other wiki software | ** Mediawiki or other wiki software | ||
**: | **:Kind of | ||
** make, gcc, gdb or other development tools | ** make, gcc, gdb or other development tools | ||
**: | **:Familiar with make and gcc, less with gdb | ||
* What will make you actively stay in our community after this GSoC is over? | * What will make you actively stay in our community after this GSoC is over? | ||
*: | *:Keeping on with research in university | ||
== O: Only out of interest == | == O: Only out of interest == | ||
* Did you ever hear about Octave before? | * Did you ever hear about Octave before? | ||
*:Of course | *:Of course | ||
** If so, when and where? How far have you been involved already? | ** If so, when and where? How far have you been involved already? | ||
**:Until three years ago I | **:Until three years ago I just used Matlab since it was the common choice at the university. After that I heard about Octave when I was in a researcher lab and I start working mostly on it. | ||
* 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? | ||
*:As | *:As normal user, I do not remember a question that was difficult to answer. | ||
== P: Prerequisites == | == P: Prerequisites == | ||
Line 67: | Line 64: | ||
* Please estimate an average time per day you will be able to access | * Please estimate an average time per day you will be able to access | ||
** an internet connection | ** an internet connection | ||
**: 24 | **: 24 | ||
** a computer | ** a computer | ||
**: 24 | **: 24 | ||
** a computer with your progressing work on | ** a computer with your progressing work on | ||
**:24 | **:24 | ||
* Please describe the degree to which you can install new software on computers you have access to. | * Please describe the degree to which you can install new software on computers you have access to. | ||
*:Full permissions | *:Full permissions | ||
== S: Self-assessment == | == S: Self-assessment == | ||
* Please describe how useful criticism looks from your point of view as committing student. | * Please describe how useful criticism looks from your point of view as committing student. | ||
*: | *:Indispensable! | ||
* How autonomous are you when developing: | * 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 discuss changes intensively and not start coding until you know what you want to do? | ||
Line 90: | Line 87: | ||
* Please provide a rough estimated timeline for your work on the task. | * Please provide a rough estimated timeline for your work on the task. | ||
*: '''05/05 - 30/05''' (community bonding period) | *: '''05/05 - 30/05''' (community bonding period) | ||
*:: | *:: '''Week 1''' | ||
*::: - Begin to stay in contact and familiarize with the community, using both the mailing list and the IRC channel. | *::: - Begin to stay in contact and familiarize with the community, using both the mailing list and the IRC channel. | ||
*::: - Improve expertise with tools like Mercurial and autotools | *::: - Improve expertise with tools like Mercurial and autotools | ||
*::: - Read Matlab doc of Neural Network Toolbox classes and basic functions, with a focus on the deep learning part about CNNs | *::: - Read Matlab doc of Neural Network Toolbox classes and basic functions, with a focus on the deep learning part about CNNs | ||
*:: | *:: '''Week 2''' | ||
*::: - Deeply analyze both Python and C++ Tensorflow APIs in order to figure out the best path to follow | *::: - Deeply analyze both Python and C++ Tensorflow APIs in order to figure out the best path to follow | ||
*::: - Install and run Pytave. Read the doc if provided or exchange with the maintainers | *::: - Install and run Pytave. Read the doc if provided or exchange with the maintainers | ||
*:: | *:: '''Week 3''' | ||
*::: - Test Pytave and figure out there is some bug or missing feature of the specific part that we need. | *::: - Test Pytave and figure out there is some bug or missing feature of the specific part that we need. | ||
*::: - Fix potential bugs or submit new patches | *::: - Fix potential bugs or submit new patches | ||
*::: - Figure out if we need some object programming in Octave (like classdef) and test it | *::: - Figure out if we need some object programming in Octave (like classdef) and test it | ||
*: '''30/05 - 30/06''' (Phase 1) | *: '''30/05 - 30/06''' (Phase 1) | ||
*:: | *:: '''Week 4,5''' | ||
*::: - Work on the makefile in order to link TF in either Python or C++ and test | *::: - Work on the makefile in order to link TF in either Python or C++ and test soma basic nets with TF | ||
*:: | *:: '''Week 6,7''' | ||
*::: - Write all the Octave classes for every layer and use corresponding TF functions. Because of the focus on Matlab Nnet Toolbox, we will start to define the fundamental layers used for CNNs : Convolutional layer, ReLU layer, Normalization layer, Average pooling layer object, Max pooling layer, Fully connected layer, Dropout layer, Softmax layer, Classification output layer, Regression output layer | *::: - Write all the Octave classes for every layer and use corresponding TF functions. Because of the focus on Matlab Nnet Toolbox, we will start to define the fundamental layers used for CNNs : Convolutional layer, ReLU layer, Normalization layer, Average pooling layer object, Max pooling layer, Fully connected layer, Dropout layer, Softmax layer, Classification output layer, Regression output layer | ||
*:: | *:: '''Week 8''' | ||
*::: - Implement a draft of the training functions (seriesNetwork object, trainNetwork, trainingOptions) without all options and parameters | *::: - Implement a draft of the training functions (seriesNetwork object, trainNetwork, trainingOptions) without all options and parameters | ||
*: '''01/07 - 28/07''' (Phase 2) | *: '''01/07 - 28/07''' (Phase 2) | ||
*:: | *:: '''Week 9-10-11-12''' | ||
*::: - Implement a complete working version of the training functions. | |||
*::: - Implement a complete working version of | |||
*: '''28/07 - 25/08''' (Final phase) | *: '''28/07 - 25/08''' (Final phase) | ||
*:: | *:: '''Week 13''' | ||
*::: - Able the parallelization and analyze CUDA integration | *::: - Able the parallelization and analyze CUDA integration | ||
*:: | *:: '''Week 14-15''' | ||
*::: - Implementation of a cool application like deepDreamImage and (if some time is left) more advanced nets like (AlexNet, vgg16, vgg19) | *::: - Implementation of a cool application like deepDreamImage and (if some time is left) more advanced nets like (AlexNet, vgg16, vgg19) | ||
*:: | *:: '''Week 16''' | ||
*::: - As a bonus if some time is left, try to implement ImageDatastore in order to manage seamless the image import | *::: - As a bonus if some time is left, try to implement ImageDatastore in order to manage seamless the image import | ||
*: All tests and documentation will be written during the whole period, simultaneously with every function. Both BIST tests and doc tests will be written, along with Python unit tests. | *: All tests and documentation will be written during the whole period, simultaneously with every function. Both BIST tests and doc tests will be written, along with Python unit tests. |