From a7fcc1eb66843c307a901752e1220f2d4396184d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?F=C3=A9lix=20Girard?= Date: Tue, 7 Nov 2017 16:45:30 -0500 Subject: [PATCH] Update ### TODO ###.txt --- ### TODO ###.txt | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/### TODO ###.txt b/### TODO ###.txt index 289650f..c3cfda5 100644 --- a/### TODO ###.txt +++ b/### TODO ###.txt @@ -1,3 +1,16 @@ +As of November 07 2017... + +- Covar_ui is pretty completed. Still, some extensive tests need to be done to ensure that all is working properly. +- Inversion is started. However, just a basic functionality is implemented. At least the basics are there. + +Still to do : + - Complete the inversion module + - Think about how we want to handle changes in the database + - Discuss the possibility of implementing unit tests from now on + - Still, there is alot of #TODO in the code. Normally when modifying one module you should clear all the todos. + - Implement 3D version for all the modules. The only problem was a lack of good visualisation in 3D. Probably Bernard know a solution. + + As of June 30th 2017... Covar_ui is close to done: @@ -42,4 +55,4 @@ as 'print('a', 'b', 'c')'. The code is fully PEP 8 compatible, exception made for the extra spaces before and after operators and for lines too long, which are ignored for the purpose of readability. (Full list of ignored errors: E202, E221, E241, E501, E722, E741) -Finally, one should refer to the TODO annotations for specific tasks. Those may require a better understanding of BhTomoPy, though. \ No newline at end of file +Finally, one should refer to the TODO annotations for specific tasks. Those may require a better understanding of BhTomoPy, though.