| 1 | [[TOC(inline)]]
|
|---|
| 2 |
|
|---|
| 3 | The weekly breakdown for the GSoC project is:
|
|---|
| 4 |
|
|---|
| 5 | == Community Bonding Period: April 23 – May 13 ==
|
|---|
| 6 | ● Implement GLS-MPT
|
|---|
| 7 | ● Write unit tests, performance tests, documentation for GLS-MPT
|
|---|
| 8 | ● Write examples for diversification of search results
|
|---|
| 9 |
|
|---|
| 10 | == Coding Week 1: May 14–May 20 ==
|
|---|
| 11 | ● Buffer time for finishing any pending work
|
|---|
| 12 | ● Get work reviewed by mentors and make suitable corrections to get it to a stable and mergeable form
|
|---|
| 13 | ● Apply for hosted copy of TREC ClueWeb09 Category B
|
|---|
| 14 |
|
|---|
| 15 | == Coding Week 2: May 21–May 27 ==
|
|---|
| 16 | ● Modify K-Means clustering as required for implementation of C2-GLS
|
|---|
| 17 | ● Begin implementing C2-GLS
|
|---|
| 18 |
|
|---|
| 19 | == Coding Week 3: May 28–June 3 ==
|
|---|
| 20 | ● Finish implementation of C2-GLS
|
|---|
| 21 |
|
|---|
| 22 | == Coding Week 4: June 4–June 10 ==
|
|---|
| 23 | ● Write performance tests and documentation for C2-GLS
|
|---|
| 24 |
|
|---|
| 25 | == Coding Week 5: June 11–June 17 (evaluations: June 11-15) ==
|
|---|
| 26 | ● Implement - nDCG, which includes unit tests and documentation
|
|---|
| 27 |
|
|---|
| 28 | == Coding Week 6: June 18–June 24 ==
|
|---|
| 29 | ● Index the ClueWeb09 Category B dataset with Xapian so as to evaluate diversification
|
|---|
| 30 | ● Evaluate performance and efficiency of GLS-MPT and compare it with [2]
|
|---|
| 31 |
|
|---|
| 32 | == Coding Week 7: June 25–July 1 ==
|
|---|
| 33 | ● Evaluate performance of C2-GLS K-Means and compare it with [2]
|
|---|
| 34 | ● Buffer time for finishing any pending work
|
|---|
| 35 | ● Get work reviewed by mentors and make suitable corrections to get it to a stable and mergeable form
|
|---|
| 36 |
|
|---|
| 37 | == Coding Week 8: July 2–July 8 ==
|
|---|
| 38 | ● Implement LC clustering
|
|---|
| 39 | ● Write tests for LC clustering
|
|---|
| 40 |
|
|---|
| 41 | == Coding Week 9: July 9–July 15 (evaluations: July 9-13) ==
|
|---|
| 42 | ● Write examples and documentation for LC clustering
|
|---|
| 43 | ● Fix any bugs encountered up till this point
|
|---|
| 44 |
|
|---|
| 45 | == Coding Week 10: July 16–July 22 ==
|
|---|
| 46 | ● Discussing and working on stretch goals
|
|---|
| 47 |
|
|---|
| 48 | == Coding Week 11: July 23–July 29 ==
|
|---|
| 49 | ● Buffer time for finishing any pending work
|
|---|
| 50 | ● Get work reviewed by mentors and make suitable corrections to get it to a stable and mergeable form
|
|---|
| 51 |
|
|---|
| 52 | == Coding Week 12: July 30–August 5 ==
|
|---|
| 53 | ● Project write-up along with completing any pending work
|
|---|
| 54 | ● Get work reviewed and make suitable corrections to get it to a stable and mergeable form
|
|---|
| 55 |
|
|---|
| 56 | == Coding Week 13: August 6–August 12 (evaluations: August 6-14) ==
|
|---|
| 57 | ● Submission of code, project summaries and final evaluation
|
|---|
