On 5/15/07, Edward d'Auvergne <edward.dauvergne@xxxxxxxxx> wrote:
Yikes, that is a lot of added docstrings!!! Very impressive.
ah, but (more importantly), does it make sense to you ;-)
Have
you tried compiling the API documentation to see how these comments
will look?
no I haven't tried compiling yet, I intend to get to the end of processor.py and give it a try. is it fairly easy?
my current schedule is
1.
complete docs for prcoessor.py (this is partially so Neil can read it,
he ios having atry at parallelising func, dfunc amd d2func for case
all in mf.py as a bit of a journeyman project, it doesn't really matter
how far he gets and if it works well in python [though it might])
2. fix neils bug in the multi branch (he sees non returned from some minimisation which causes a crash)
3. go through the detail on the older e-mail you sent to me
4. complete docs
2 and 3 may swap depending on mood
It's definitely worth checking to make sure that these
automatically compiled docs make sense for understanding the structure
of your code.
Cheers,
Edward
P.S. As you can see I have now cleared the back log of relax emails
that had built up while I transitioned from Oz to Germany.
excellent
[snip]
regards
gary
Re: r3295 - in /branches/multi_processor: multi/multi_processor.py multi/processor.py specific_fns/model_free.py