update DDB output whenever possible
Posted: Fri Jul 06, 2012 12:49 pm
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
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