The if condition is only there to speed up the code. As the data structures which are evaluated will be the same for all residues (they are the global structures), the eval() statements only need to be done once to read in a results file. I should have explained its purpose in the comment line. The change, however, will have no noticeable effect. Would you like to have a go at merging your fix into the 1.1 line. It's probably easiest to check out that line and manually change the file. Otherwise, I'll just incorporate it (unless you would prefer having 'macraild' next to the file). The merge is important as any changes made to the 1.0 line will disappear in future versions of relax if they are not merged into the highest numbered branch. I've almost completed the relaxation curve fitting code, the reason for creating the 1.1 branch, so once I stabilise a few things, I'll create a new stable branch from it called 1.2. You might even find the 1.2 branch next time you look (therefore the merge should go there instead). There are a lot of internal changes which would be invisible to the user and the release packages will be different. Installation of the program has also changed. Instead of typing the commands, making symlinks, etc as in the 1.0 line, you type 'make install' and it will do all that for you. Not quite sure how this will work on a Windows computer though? Oh, the manual has had a few fixes and has expanded a bit as well. It's now well over 200 pages long. On 12 Jan 2006 14:57:47 +0000, Chris MacRaild <c.a.macraild@xxxxxxxxxxx> wrote: > Opps, Should have spotted the noe_r1_table issue. I've shifted the new > code as you suggest. The other change that somehow escaped my last > commit is the deletion of the if condition in the function > read_columnar_relax_data() at line 3221 in specific_fns/model_free.py > The test for consistency that follows is then redundant. > > > On Thu, 2006-01-12 at 04:39, Edward d'Auvergne wrote: > > Oh, for readability it might be worth having an empty line before each > > comment and subsequent block of code. It makes it easier to read and > > understand the code. As for the mailing list, a 'reply to all' option > > should CC the email to the relax-devel list as well as the person > > you're responding to. > > > > > > On 12/01/06, Edward d'Auvergne <edward.dauvergne@xxxxxxxxx> wrote: > > > Chris, > > > > > > Good idea to pop the empty data out after the fact. It's a nice and > > > simple fix. There will, however, probably be a problem with the > > > residue specific data structure 'noe_r1_table[]'. As the pop commands > > > are run, the indexes in 'noe_r1_table' will need to be changed to a > > > different integer or to None. This structure is essential for > > > minimisation. > > > > > > It may be easier to shift your code into the file > > > 'specific_fns/relax_data.py' and into the bizarrely named function > > > 'add_residue()', probably around line 90 but before the 'num_ri' and > > > 'num_frq' assignment. The the 'noe_r1_table' structure will then be > > > correctly constructed and you won't need an algorithm to fix the > > > structure post construction. What do you think? > > > > > > > _______________________________________________ > > Relax-devel mailing list > > Relax-devel@xxxxxxx > > https://mail.gna.org/listinfo/relax-devel > > > > > _______________________________________________ > Relax-devel mailing list > Relax-devel@xxxxxxx > https://mail.gna.org/listinfo/relax-devel >