Difference between revisions of "Task ideas for Google Code-in"

From Apertium
Jump to navigation Jump to search
Line 643: Line 643:
 
|tags=javascript, html, apy
 
|tags=javascript, html, apy
 
}}
 
}}
  +
{{Taskidea
 
  +
|type=code
  +
|mentors=Anna
  +
|title=Train a new model for syntactic function labeller
  +
|description=Choose one of the languages Apertium uses in language pairs and prepare training data for the labeller from its UD-treebank: replace UD tags with Apertium tags, parse the treebank, create fastText embeddings. Then train a new model on this data and evaluate an accuracy.
  +
|tags=python, UD, embeddings, machine learning
  +
|multi=5
  +
}}
  +
{{Taskidea
  +
|type=code,quality
  +
|mentors=Anna
  +
|title=Tuning a learning rate for syntactic function labeller's RNN
  +
|description=Syntactic function labeller uses RNN for training and predicting syntactic functions of words. Current models can be improved by tuning training parameters, e.g. learning rate parameter.
  +
|tags=python, machine learning
  +
}}
 
</table>
 
</table>
   

Revision as of 10:50, 15 November 2017

Contents

This is the task ideas page for Google Code-in, here you can find ideas on interesting tasks that will improve your knowledge of Apertium and help you get into the world of open-source development.

The people column lists people who you should get in contact with to request further information. All tasks are 2 hours maximum estimated amount of time that would be spent on the task by an experienced developer, however:

  1. this does not include time taken to install / set up apertium (and relevant tools).
  2. this is the time expected to take by an experienced developer, you may find that you spend more time on the task because of the learning curve.

Categories:

  • code: Tasks related to writing or refactoring code
  • documentation: Tasks related to creating/editing documents and helping others learn more
  • research: Tasks related to community management, outreach/marketting, or studying problems and recommending solutions
  • quality: Tasks related to testing and ensuring code is of high quality.
  • interface: Tasks related to user experience research or user interface design and interaction

Clarification of "multiple task" types

  • multi = number of students who can do a given task
  • dup = number of times a student can do the same task

You can find descriptions of some of the mentors here.

Task ideas