Annotatrix/Work plan
< Annotatrix
Jump to navigation
Jump to search
Revision as of 08:52, 18 July 2013 by Tuxskar (talk | contribs) (→Week 5 First deliverable and Training)
Contents
Workflow
Week 5 First deliverable and Training
From 12th to 18th of July
- Implement the second interface (Training view)
- TDD tests for Training view Done
- Made up again the training model Working here
- Made up a test to test the prob generated
- Implement the train method for a tagged_corpus method to generate the prob file with the path as argument
- Test for urls in training django, tests for views passing the correct data
- Show the tagged_corpus in a correct textarea
- Key recorder for tag alternative selection
- Create the view URL and connect "go to tagger" button with it
- Get keyboard keys from JavaScript
- Connect keys to tag alternative selection
- Document the first view Done
- Document for developers Done
- Document for users Done
You can find the first deliverable here
- Implement the system's modules Done
- Implement controller to use apertium-dbus Done
- Implement external models for Tags Done
- Managing users authentication
- Django-registration package
- Getting history of user's trained
- Fusion same analysis output in the same analysis file (Francis improvement idea about automorf.bin file)
Week 4 Insert corpus view
From 5th to 11th of July
- Implement a index annonatrix view to access to the different apps Done
- Implement all links to see details and insert corpora Done
- Testing the first view (by TestCases) Done
- Learn how to test with TestCases in Django Done
- Implement test for the first view Done
- Implement the first view (Insert file view) Done
- First basics views Done
- Managing files Done
- Upload files Done
- Select corpus language Done
- Upload Corpus model with language field Done
- Add title field to the view Done
- Go to tagger button Done
- modelforms Done
- understanding-the-managementform Done
- Validate "go to tagger" forms Done
- Friendly interface
- HTML tutorial w3schools.com Done
- CSS Tutorial w3schools.com Done
- Implement the system's modules
- Implement controller to use apertium-dbus Some Part
- Implement external models for Tags
- Implement internal models for trainings Done
- Implement Django administration site Done
Week 3 Django warm-up
From 28th of June to 4th of July
- Design a system directly to web Done
- Design controller to use apertium-dbus Done
- Design external models for Tags Done
- Design internal models for trainings Done
- Design structure for annotatrix project Done
- annotatrix as project and 4 different applications (tagger, GCManager, TSX-managaer and Prob measurer)
- Do toy web app using Django Done
- Django official tutorial Part 1 Done
- Django official tutorial Part 2 Done
- Django official tutorial Part 3 Done
- Django official tutorial Part 4 Done
- Django official tutorial Part 5 Done
- Django official tutorial Part 6 Done
- Advanced tutorial: How to write reusable apps Done
Week 2 Kick-off
From 27th to 27th of June
- Resolve python2 or python3 discussion Python3
- Learn differences python3 from python2 Done
- Learn differences gtk2 and gtk3 using python3 Deprecated
- Remake up the mock-ups UI using gtk3 Deprecated
- Port launcher in python2 to python3 Deprecated
- Made up a system design approaching implement a web app or a desktop one Updated
- Design a system directly to web
- Install Django and python3 Done
Week 1 Pre-Kick-off
- Know how to use launch lt-proc to tag corpus Done
- Install apertium-tolk and check the code Done
- Finish the exams Done
System design
There are just one Django project but 4 different applications
There are 2 kind of packages, the Django ones and the external ones The Django packages are provided by Django as views, models, urls, etc The external packages are extra for this projects
Internal Django models package
Corpus
Training
External Controller package
tagger-ctrl
Working plan
Week | Dates | Tasks |
---|---|---|
0 | 21/05—16/06 | Bonding and designing firsts internals GUIs |
1 | 17/06—23/06 | I'm still with final exams |
2 | 24/06—30/06 | Input File UI coding 30h, Tagger Corpus UI coding 5/60h |
3 | 01/07—07/07 | Tagger Corpus UI coding 35/60h |
Deliverable 1 | ||
4 | 08/07—14/07 | Tagger Corpus UI coding 20/60h + TDD 15/40h |
5 | 15/07—21/07 | Tagger Corpus UI TDD 25/40h, TSX file manager UI coding 10/40h |
Deliverable 2 | ||
6 | 22/07—28/07 | TSX file manager UI coding 30/40h + TDD 5/20h |
7 | 29/07—04/08 | TSX file manager UI TDD 15/20h, Constraint Grammar UI coding 20/50h |
Deliverable 3 and Mid-term evaluations deadline August 2sd | ||
8 | 05/08—11/08 | Constraint Grammar UI coding 30/50h + TDD 5/30 |
9 | 12/08—18/08 | Constraint Grammar UI TDD 25/30h, Performance measure .prob UI coding 10/70h |
Deliverable 4 | ||
10 | 19/08—25/08 | Performance measure .prob UI coding 35/70h |
11 | 26/08—01/09 | Performance measure .prob UI coding 25/70h + TDD 10/40h |
12 | 02/09—08/09 | Performance measure .prob UI TDD 30/40h, Final documentation 5h |
Deliverable 5 | ||
13 | 09/09—15/09 | Final documentation and finalitation |
Final evaluation deadline September 27th |