Page 1 of 1

update DDB output whenever possible

Posted: Fri Jul 06, 2012 12:49 pm
by jzwanzig
Hi,

currently during a response function run, the DDB file appears to be written only at the end; thus if say three perturbations are computed, the DDB contains all three but is not written until all three are done. Would it be possible to change this behavior such that it is updated every time a perturbation is completed, or, maybe better, a separate DDB file is written for each perturbation, say with the usual ipert numbering scheme appended, as we do for 1WF and 1DEN and so forth? In big systems you end up using mrgddb on lots of DDB files anyway, and that takes negligible time. It would save us (me, this morning, for example) for losing work when a computer glitch or disk quota issue occurs and kills a calculation that has lasted a few days and for which some but not all of the iperts were already finished, but the DDB still hasn't been written.

thanks,
Joe

Re: update DDB output whenever possible

Posted: Fri Sep 13, 2013 2:13 pm
by mverstra
Hear Hear!!

I have requested this a while ago as well. The trouble is that the non-self-consistent DDB elements you get are not trivially augmented when you have 1 pert then another - you can get a number of symmetric ones from the both which are not accessible separately, depending on the symops in your system. The main culprits are rotations where the reduced x goes to y or x+/-y depending, e.g. with 3-fold axes.

At any rate partial information should be output to DDB1 DDB2 etc... as the calculation goes along, I agree. It's not just an issue of calling the output routine, though, but propagating down the non-stationary completion of other perturbations, instead of doing that only at the end of the full dataset. So: doable but not trivial.

cheers

Matthieu