-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zernike refactor #42
Comments
Those are all good. I would add documentation of the code so that it will be easier to maintain in the future. |
Making incremental progress here, a few hours a day. Expect a push this week. |
Great! Cheers, On Mon, Apr 28, 2014 at 4:05 PM, brianthelion [email protected]:
|
Didn't get quite as much done as I had hoped last week. Picking it up again tomorrow and will update on progress then. Cheers! |
Great -- Looking forward to your update! Cheers, On Mon, May 5, 2014 at 12:54 PM, brianthelion [email protected]:
|
Documentation is still to-do. |
Good show, Brian! |
The Koehl implementation is covered in #45. There are still a few things to do to wrap this ticket, like pulling together the documentation. |
@binarybottle: I finally have some time to put on this cleanup task. Unfortunately I haven't tracked our priorities w.r.t tasks 1-5 listed above. Is documentation the only thing that remains to be done at this time? Cheers! |
I believe documentation was the only thing left to do, but after Satra found that a 2GB memory limit was exceeded by computing Zernike moments, this strikes me as extremely important to address! From Satra: |
Ok, see my comments on #52. |
@binarybottle Is there a particular documentation standard that you're sticking with on Mindboggle? |
If you take a look at any of the other scripts, you'll see that I use restructured text. I use Sphinx to create docs from the code. Does that answer your question? |
@binarybottle Yep! Thanks. |
@brianthelion -- If you are unable to devote any more time to documentation of the code, shall I close this issue? |
@binarybottle - was this fixed? |
Since the only lingering part of the discussion was the question of documentation, I didn't think it helpful to keep this issue open. |
Anything else?
The text was updated successfully, but these errors were encountered: