User:Sudeepam: Difference between revisions
Jump to navigation
Jump to search
| Line 185: | Line 185: | ||
*'''Please provide a rough estimated timeline for your work on the task.''' | *'''Please provide a rough estimated timeline for your work on the task.''' | ||
:'''Preparations for the project (pre-community bonding)''' | :'''Preparations for the project (pre-community bonding)''' | ||
::While this application is being reviewed, I have started working on a m-script which will be used for the extraction of the most common spelling errors. (I’m assuming that I’ll be working on the third kind of classifier neural network). This script will catch the most common typographical errors that the users make. This list of errors could then be... | ::While this application is being reviewed, I have started working on a m-script which will be used for the extraction of the most common spelling errors. (I’m assuming that I’ll be working on the third kind of classifier neural network). This script will catch the most common typographical errors that the users make. This list of errors could then be... | ||
:::-Uploaded to a secure server directly. | |||
:::-Stored as a text file and we can ask the users to share this file with us. | |||
::I’d like to mention here that the data we receive would essentially be a list misspelled functions only. If there is no user meta data attached to it, we don’t really need to hide it from anyone, all we would need is that no unauthorized person could modify/delete it. Nonetheless, how exactly we receive the data collected from the users would need some discussions with the community. | ::I’d like to mention here that the data we receive would essentially be a list misspelled functions only. If there is no user meta data attached to it, we don’t really need to hide it from anyone, all we would need is that no unauthorized person could modify/delete it. Nonetheless, how exactly we receive the data collected from the users would need some discussions with the community. | ||
| Line 198: | Line 199: | ||
::I will use the community bonding period to... | ::I will use the community bonding period to... | ||
:::-Persuade the community to use our data extraction script and help us collect training data. This can be done by discussing the benefits of a command line suggestion feature and sharing my current implementation of this feature [https://github.com/Sudeepam97/Did_You_Mean]. | |||
:::-Ask the community to report issues with the m-script containing the current implementation. I’ll shift the current implementation to mercurial if required. | |||
:::-Discuss how we should receive the data generated by the users, work on the approach, and start the collection of data. | |||
:::-Organize the data as it is received and divide it to create proper, training, cross-validation, and test sets for the Neural Network. | |||
:'''May, 14 – June, 10 (4 weeks)''' | :'''May, 14 – June, 10 (4 weeks)''' | ||
| Line 213: | Line 214: | ||
::'''Phase 1 evaluations goal:''' A set of working neural network m-scripts, which could suggest corrections for typographic errors. | ::'''Phase 1 evaluations goal:''' A set of working neural network m-scripts, which could suggest corrections for typographic errors. | ||
June, 11 – July, 8 (4 weeks) | |||
Week 5 (June, 11 – June, 17): I’d like to take this week to work in close connection with the community and perform tests on the newly created m-scripts. Essentially, I’ll be asking the community to try out our m-scripts and see how they work for them. I will work on the issues pointed out by the community and by the mentors as they are reported and would try to make the m-scripts perfect in this week itself. | :'''June, 11 – July, 8 (4 weeks)''' | ||
Week 6 (June, 17 – June, 24): I’ll fix any remaining issues and proceed to discuss and understand how our Neural Network should be integrated with Octave. I’ll start working on integrating the network as soon as the approach is decided. It is worth mentioning here that we will merge a trained network with Octave and therefore the chances of our code being slow are eliminated. | |||
Week 7 – Week 8 (June, 25 – June, 8): I will integrate our neural network with Octave as discussed, and write, and perform tests to make sure that everything works the way it should. If this task gets completed earlier than expected, I’ll automatically move on to the next task. | ::'''Week 5 (June, 11 – June, 17):''' I’d like to take this week to work in close connection with the community and perform tests on the newly created m-scripts. Essentially, I’ll be asking the community to try out our m-scripts and see how they work for them. I will work on the issues pointed out by the community and by the mentors as they are reported and would try to make the m-scripts perfect in this week itself. | ||
Phase 2 evaluations goal: A development version of Octave which has a command line suggestion feature (currently there will be no mechanism available to easily select the corrections suggested and easily enable/disable this feature). | ::'''Week 6 (June, 17 – June, 24):''' I’ll fix any remaining issues and proceed to discuss and understand how our Neural Network should be integrated with Octave. I’ll start working on integrating the network as soon as the approach is decided. It is worth mentioning here that we will merge a trained network with Octave and therefore the chances of our code being slow are eliminated. | ||
July, 9 – August, 5 (4 weeks): | ::'''Week 7 – Week 8 (June, 25 – June, 8):''' I will integrate our neural network with Octave as discussed, and write, and perform tests to make sure that everything works the way it should. If this task gets completed earlier than expected, I’ll automatically move on to the next task. | ||
Week 9 (July, 9 – July, 15): The development version of Octave, with an inbuilt suggestion feature will be open for error reports. I’ll work on the issues as they are reported and also discuss what an easy enable/disable mechanism and the mechanism to easily select the corrections suggested should be like. | |||
Week 10 (July, 16 – July, 22): I’ll create the required mechanisms as discussed, write and perform tests, and push a development version with a complete command line suggestion feature. | :'''Phase 2 evaluations goal:''' A development version of Octave which has a command line suggestion feature (currently there will be no mechanism available to easily select the corrections suggested and easily enable/disable this feature). | ||
Week, 11 – Week, 12 (July, 23 – August, 5): I’ll work in close connection with the community, fix the issues that are reported, and ask for further suggestions on how the command line suggestion feature could be made better. | |||
Phase 3 evaluations goal: A development version of Octave with a complete and working command line suggestion feature, open to feedback and criticisms | :'''July, 9 – August, 5 (4 weeks):''' | ||
::'''Week 9 (July, 9 – July, 15):''' The development version of Octave, with an inbuilt suggestion feature will be open for error reports. I’ll work on the issues as they are reported and also discuss what an easy enable/disable mechanism and the mechanism to easily select the corrections suggested should be like. | |||
::'''Week 10 (July, 16 – July, 22):''' I’ll create the required mechanisms as discussed, write and perform tests, and push a development version with a complete command line suggestion feature. | |||
::'''Week, 11 – Week, 12 (July, 23 – August, 5):''' I’ll work in close connection with the community, fix the issues that are reported, and ask for further suggestions on how the command line suggestion feature could be made better. | |||
:'''Phase 3 evaluations goal:''' A development version of Octave with a complete and working command line suggestion feature, open to feedback and criticisms | |||