Hi Pat,
I believe they suggest using target weight optimization in this case. It can be specified on the command line as below:
optimize_xyz_weight=true optimize_adp_weight=true
I've found for a couple structures I had to use this or else the geometry was much worse. They also recommend to use this in the last round of refinement.
Cheers,
Nick
________________________________
From: [email protected]
On 4 May 2017, at 12:20 PM, Pavel Afonine
wrote: Hi Patrick,
I am finishing a refinement at 2.5 Å, using the Phenix GUI. I performed a three-macrocycle refinement, and saw that the geometry (RMS bonds/angles) and R/Rfree all got better in the first macrocycle, and then worsened in the subsequent two macrocycles.
it's hard to comment on this one because I don't know how you define "worse". For example, I'd call the same "R/Rfree = 0.208/0.236" and "R/Rfree = 0.209/0.240" but some may think they are different.
OK, fine. So I repeated the refinement, except I performed only a single macrocycle (starting from the exact same input coordinates). However, the statistics after this one-macrocycle job did not match the stats seen after 1 macrocycle in the 3-macrocycle job (?!). This doesn’t make sense to me; if you’re starting from the exact same coordinates, shouldn’t the first macrocycle always wind up at the same place, regardless of whether or not the program goes on to do additional macrocycles of refinement?
phenix.refine may change internal strategies based on specified number of macro-cycles. So your observation is not too unexpected to me.
Pavel
_______________________________________________ phenixbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/phenixbb Unsubscribe: [email protected]