That is why it is a proposal :) It's also the plant the idea so that
as you fix problems in the specific_analyses.relax_disp package due to
your changes, I hope to open your eyes to the simplicity that your
design will bring. And it's there for the future - sometimes it is
years after a proposal is made that it'll be implemented by a future
developer.
Regards,
Edward
On 17 June 2014 10:01, Troels Emtekær Linnet <tlinnet@xxxxxxxxxxxxx> wrote:
That would have to go for next version.
I am aiming straight for cleaning the API, so I can wrap this up, and get it
into
trunk.
And get on with my data analysis.
Best
Troels
2014-06-17 9:50 GMT+02:00 Edward d'Auvergne <edward@xxxxxxxxxxxxx>:
Hi Troels,
Now that your array structures are well defined and all within one
clear block in the target function __init__() method, I thought that
maybe it would be a good time to reconsider the data assembly
functions and design in the specific_analyses.relax_disp package.
What I mean is that your new numpy structures could replace all of my
list of lists structures throughout the entire dispersion code base.
These data structures are primarily used for optimisation, and then
used a little in maybe 3-4 other places, so your numpy array
construction in the target function __init__() method could be
directly moved into
specific_analyses.relax_disp.data.return_r2eff_arrays() function (as
well as a few of the other return_*() functions). My old list of
lists idea is now fully redundant and I would be happy if your numpy
construction replaces it completely :)
Regards,
Edward
_______________________________________________
relax (http://www.nmr-relax.com)
This is the relax-devel mailing list
relax-devel@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: A proposal for simplifying all relaxation dispersion data structures.