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
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
Hi,
Could you send me some representative logfiles (probably off-list)? This might
give a hint. It must be something unusual, because we have a fairly wide range
of test cases and none of them have any problems.
Thanks and best wishes,
Randy Read
On 1 Sep 2011, at 14:58, alexander.schif...@
Dear all,
We just upgraded to ccp4 6.2.0 and with that upgrade switched from Phaser 2.1.4
to 2.3.0. During testing we ran into the problem that for some of our datasets
phaser stops with a floating point exception . As it is not the case for all
datasets I asume it must be linked to the input m