I thought this problem is fixed. Could you please try the version from:
www.ysbl.york.ac.uk/refmac/latest_refmac.html
Problem was that when refmac starts twinning analysis it uses generous
tolerance and then filters out unlikely twin operators.
When large deformation is needed merohedral twinning to occur then
resolution of twin mates may be different.
In the version you are working refmac forgets to recalculate
resolution. In the version from above web site it should be corrected.
regards
Garib
On 20 Jan 2010, at 17:22, Christian Strube wrote:
> Hi,
>
> I just found out, that this effect just occurs when I push the "twin
> refine" button. I have 4 slightly twinned datasets, and so far the
> twin refine worked very well...but this should not happen, I think.
> Any explanations or advise?
>
> greetings,
>
> Christian
>
>
> Hi ccp4bb,
>
> I have a big problem concerning refmac_5.5.0088. I refined a couple
> of structures. Now after refining I realized that refmac sets wrong
> resolution limits for my data. Scaling was done with scala. I cut
> the data at 1.8 A. Then I used molrep; respectively difference
> fourier. Later in refmac I set 1.8A as resolution limit as well. But
> in the logfile and in the output-pdb-file there is 1.64A written as
> resolution limit. In addition the completeness is 80% instead of 98.
> With my other datasets refmac behaves similar (1.87 instead of
> 2.1, ...). What do I have to do that refmac applies and doesn?t
> change my settings?
>
> Thanks in advance for any advise,
>
> Christian
|