| | 388 | |
| | 389 | === Week 04 === |
| | 390 | |
| | 391 | '''1) What did I complete this week?'''\\ |
| | 392 | |
| | 393 | * Implemented some changes from dev feedback (e.g. added a new flag to manage the two procedure separately and added the text file option to specify input bands) |
| | 394 | * Tested the modified python script and fixed bugs (e.g. solved a bug for -s flag) |
| | 395 | * Created a real complete GRASS GIS module that can be installed with g.extension |
| | 396 | * Finished implementing the GUI |
| | 397 | * Tested the GUI and fixed bugs |
| | 398 | * Cleaned up the code from the style point of view in order to make it more readable (followed PEP8 style guide and GRASS Python Scripting Library rules, converted python lists into dictionaries, added comments, messages and warnings, etc.) |
| | 399 | * Started writing the manual page |
| | 400 | * Solved a problem with g.extension thanks to dev community suggestions |
| | 401 | * Discussed future improvements with the dev community |
| | 402 | * Frequently added the new version of the code to my !GitHub repository |
| | 403 | * Shared progress with the community |
| | 404 | |
| | 405 | '''2) What am I going to achieve for next week?'''\\ |
| | 406 | |
| | 407 | * Implement any change from discussions and feedback |
| | 408 | * Test and fix bugs |
| | 409 | * Finish writing the manual page |
| | 410 | * Check the code with mentors |
| | 411 | * Prepare deliverable for the evaluation |
| | 412 | |
| | 413 | '''3) Is there any blocking issue?'''\\ |
| | 414 | No at the moment. |
