Dear Petr,
Yes, please do send the log files, MTZ file and anything else needed to run the
job that shows the problem, so we can track it down. It's probably best to
send them off-line.
We couldn't reproduce Alexander's problem, but he tells me that it only occurs
when the script is started from a mono application (and I confess that I
don't really know yet what that means). Once the problem he ran into has been
defined a bit better, we can look into whether it's something we can fix on our
end.
Regards,
Randy Read
On 6 Sep 2011, at 08:25, Petr Leiman wrote:
Dear Randy and the Phaser team,
Phaser 2.3.0 brought us several enhancement, but similar to Alexander
Schiffer's experience, Phaser has failed several times now with a floating
point exception error at different stages of automated MR: it has stopped in
the beginning of RF and then in a new run it stopped in the middle of TF. The
remedy is to explicitly lower the resolution of the input data (that was a
1.2 A resolution data with a smallish unit cell).
I can provide the log files and the mtz file if necessary.
Sincerely,
Petr
---
Petr Leiman
EPFL
IPSB-LBBS
BSP-415
CH-1015 Lausanne, Suisse
http://lbbs.epfl.ch
--
Randy J. Read
Department of Haematology, University of Cambridge
Cambridge Institute for Medical Research Tel: + 44 1223 336500
Wellcome Trust/MRC Building Fax: + 44 1223 336827
Hills RoadE-mail: rj...@cam.ac.uk
Cambridge CB2 0XY, U.K. www-structmed.cimr.cam.ac.uk
