wxu scale in phenix.refine
Hi all, in the final stages of refining a structure, I would like to optimize the restraint weights for geometry and B factors. It seems to work fine for geometry by defining " refinement.target_weights.wxc_scale=1.0". However, when the respective definition for B-factors does not seem to have an impact at all. I tried both: "refinement.target_weights.wxu_scale=2.0" in the parameter file or "wxu_scale=2.0" in the command line. The main reason why I try to fiddle around with the B-weights is that coot gives me a whole bunch of red bars in the Temperature factor variance analysis... I am using phenix 1.3d (downloaded past Sunday), mac-intel-osx, osx-10.4.10 Any ideas? Cheers Jan
Hi Jan,
in the final stages of refining a structure, I would like to optimize the restraint weights for geometry and B factors.
Good idea! Although phenix.refine computes "optimal" weight automatically, the values vary from structure to structure.
It seems to work fine for geometry by defining "refinement.target_weights.wxc_scale=1.0".
Yes, I would try an array of values 0.25, 0.5, 1.0, 1.5, 2.0, 2.5.
However, when the respective definition for B-factors does not seem to have an impact at all.
This is very weird. We exercise this in out tests regularly, so it changing wxu_scale should have an impact. It may be that values range for you structure is somehow different... Can you try the extreme values: very big (wxu_scale=10) and very small (wxu_scale=0.1) and see if this makes a difference? Are you using TLS (if yes, then this behavior is explainable)?
The main reason why I try to fiddle around with the B-weights is that coot gives me a whole bunch of red bars in the Temperature factor variance analysis...
The variability of ADP depends on many factors: resolution, model used for global motion (TLS), how internal degrees of freedom modeled ... I do not know if Coot analysis takes this all into account. Otherwise I would use the "red bars" analysis with some care. Pavel.
Hi Pavel,
thanks a lot for your fast response!
Here some clarification:
- somehow, the adjustments of the B weights were not taken into account at
all. Ie. a "diff" on the pdb-files from jobs run with wxu_scale=0.5 and
wxu_scale=2.0 shows that they are identical. While the log file acknowledges
the "Command line parameter definitions" for wxu_scale=1 and wxc_scale=2,
during the refinement section it states that wxc_scale = 1.0 and wxu_scale=
2.16.
- yes, I included a TLS refinement. Are TLS refinement ans wxu_scale
mutually exclusive? How would one proceed in this situation?
Cheers
Jan
On 9/18/07, Pavel Afonine
Hi Jan,
in the final stages of refining a structure, I would like to optimize the restraint weights for geometry and B factors.
Good idea! Although phenix.refine computes "optimal" weight automatically, the values vary from structure to structure.
It seems to work fine for geometry by defining "refinement.target_weights.wxc_scale=1.0".
Yes, I would try an array of values 0.25, 0.5, 1.0, 1.5, 2.0, 2.5.
However, when the respective definition for B-factors does not seem to have an impact at all.
This is very weird. We exercise this in out tests regularly, so it changing wxu_scale should have an impact. It may be that values range for you structure is somehow different... Can you try the extreme values: very big (wxu_scale=10) and very small (wxu_scale=0.1) and see if this makes a difference? Are you using TLS (if yes, then this behavior is explainable)?
The main reason why I try to fiddle around with the B-weights is that coot gives me a whole bunch of red bars in the Temperature factor variance analysis...
The variability of ADP depends on many factors: resolution, model used for global motion (TLS), how internal degrees of freedom modeled ... I do not know if Coot analysis takes this all into account. Otherwise I would use the "red bars" analysis with some care.
Pavel.
_______________________________________________ phenixbb mailing list [email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
Yes, I'm copying the response for exactly the same question that I wrote a week ago or so... Part 1: Playing with wxu_scale is how you change the strength of ADP restraints in all cases except when you do combined "TLS+individual ADP" refinement. In order to make the TLS refinement very robust and efficient we re-refined ~350 TLS containing structures from PDB performing the grid search for wxu_scale parameter and we found some "optimal" values for wxu_scale as a function of resolution. We use these values in automatic adjustment that you are mentioning. So currently there is no way you can turn off this adjustment; however I realize that users may want to play with wxu_scale themselves and skip the adjustments so I will provide this option in future. Part 2: As a possible solution to keep going now you can try this two-step refinement: step 1: Refine your model with default strategy (strategy=individual_sites+individual_adp) making sure that the ADP restraints are tight enough (play with wxu_scale) to produce the B-factors distribution that you like. step 2: Refine the best model out of "step 1" with the strategy=individual_sites+group_adp+tls. This will preserve the distribution of B-factors in the model from "step 1" and will add TLS model on top of it. Please let me know if you have any questions/problems! Pavel. Jan Abendroth wrote:
Hi Pavel, thanks a lot for your fast response! Here some clarification: - somehow, the adjustments of the B weights were not taken into account at all. Ie. a "diff" on the pdb-files from jobs run with wxu_scale=0.5 and wxu_scale=2.0 shows that they are identical. While the log file acknowledges the "Command line parameter definitions" for wxu_scale=1 and wxc_scale=2, during the refinement section it states that wxc_scale = 1.0 and wxu_scale=2.16. - yes, I included a TLS refinement. Are TLS refinement ans wxu_scale mutually exclusive? How would one proceed in this situation?
Cheers Jan
On 9/18/07, *Pavel Afonine*
mailto:[email protected]> wrote: Hi Jan,
> in the final stages of refining a structure, I would like to optimize > the restraint weights for geometry and B factors.
Good idea! Although phenix.refine computes "optimal" weight automatically, the values vary from structure to structure.
> It seems to work fine for geometry by defining > "refinement.target_weights.wxc_scale=1.0 ".
Yes, I would try an array of values 0.25, 0.5, 1.0, 1.5, 2.0, 2.5.
> However, when the respective definition for B-factors does not seem to > have an impact at all.
This is very weird. We exercise this in out tests regularly, so it changing wxu_scale should have an impact. It may be that values range for you structure is somehow different... Can you try the extreme values: very big (wxu_scale=10) and very small (wxu_scale=0.1) and see if this makes a difference? Are you using TLS (if yes, then this behavior is explainable)?
> The main reason why I try to fiddle around with the B-weights is that > coot gives me a whole bunch of red bars in the Temperature factor > variance analysis...
The variability of ADP depends on many factors: resolution, model used for global motion (TLS), how internal degrees of freedom modeled ... I do not know if Coot analysis takes this all into account. Otherwise I would use the "red bars" analysis with some care.
Pavel.
_______________________________________________ phenixbb mailing list [email protected] mailto:[email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
------------------------------------------------------------------------
_______________________________________________ phenixbb mailing list [email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
I will chime in. Is it possible for phenix.refine to get the TLS parameters from a previous run? then we can change wxu_scale value during an individual_adp refinement in the presence of fixed TLS parameters. Jianghai On Tue, 2007-09-18 at 09:45 -0700, Pavel Afonine wrote:
Yes, I'm copying the response for exactly the same question that I wrote a week ago or so...
Part 1:
Playing with wxu_scale is how you change the strength of ADP restraints in all cases except when you do combined "TLS+individual ADP" refinement. In order to make the TLS refinement very robust and efficient we re-refined ~350 TLS containing structures from PDB performing the grid search for wxu_scale parameter and we found some "optimal" values for wxu_scale as a function of resolution. We use these values in automatic adjustment that you are mentioning. So currently there is no way you can turn off this adjustment; however I realize that users may want to play with wxu_scale themselves and skip the adjustments so I will provide this option in future.
Part 2:
As a possible solution to keep going now you can try this two-step refinement: step 1: Refine your model with default strategy (strategy=individual_sites+individual_adp) making sure that the ADP restraints are tight enough (play with wxu_scale) to produce the B-factors distribution that you like. step 2: Refine the best model out of "step 1" with the strategy=individual_sites+group_adp+tls. This will preserve the distribution of B-factors in the model from "step 1" and will add TLS model on top of it.
Please let me know if you have any questions/problems! Pavel.
Jan Abendroth wrote:
Hi Pavel, thanks a lot for your fast response! Here some clarification: - somehow, the adjustments of the B weights were not taken into account at all. Ie. a "diff" on the pdb-files from jobs run with wxu_scale=0.5 and wxu_scale=2.0 shows that they are identical. While the log file acknowledges the "Command line parameter definitions" for wxu_scale=1 and wxc_scale=2, during the refinement section it states that wxc_scale = 1.0 and wxu_scale=2.16. - yes, I included a TLS refinement. Are TLS refinement ans wxu_scale mutually exclusive? How would one proceed in this situation?
Cheers Jan
On 9/18/07, *Pavel Afonine*
mailto:[email protected]> wrote: Hi Jan,
> in the final stages of refining a structure, I would like to optimize > the restraint weights for geometry and B factors.
Good idea! Although phenix.refine computes "optimal" weight automatically, the values vary from structure to structure.
> It seems to work fine for geometry by defining > "refinement.target_weights.wxc_scale=1.0 ".
Yes, I would try an array of values 0.25, 0.5, 1.0, 1.5, 2.0, 2.5.
> However, when the respective definition for B-factors does not seem to > have an impact at all.
This is very weird. We exercise this in out tests regularly, so it changing wxu_scale should have an impact. It may be that values range for you structure is somehow different... Can you try the extreme values: very big (wxu_scale=10) and very small (wxu_scale=0.1) and see if this makes a difference? Are you using TLS (if yes, then this behavior is explainable)?
> The main reason why I try to fiddle around with the B-weights is that > coot gives me a whole bunch of red bars in the Temperature factor > variance analysis...
The variability of ADP depends on many factors: resolution, model used for global motion (TLS), how internal degrees of freedom modeled ... I do not know if Coot analysis takes this all into account. Otherwise I would use the "red bars" analysis with some care.
Pavel.
_______________________________________________ phenixbb mailing list [email protected] mailto:[email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
------------------------------------------------------------------------
_______________________________________________ phenixbb mailing list [email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
_______________________________________________ phenixbb mailing list [email protected] http://www.phenix-online.org/mailman/listinfo/phenixbb
Hi Jianghai, phenix.refine writes out the total B-factors after TLS refinement (this is why each atom participating in a TLS group receives ANISOU record regardless the resolution). The total B is the sum of individual local B-factors (isotropic) + TLS contribution (anisotropic). Now if you take a model previously refined with TLS and refine just individual B-factors for this model (no TLS) then you don't need to do anything special to preserve the TLS information from the previous runs or read in the TLS matrices. This is simply because this TLS information is "stored" in total atomic B-factors (ANISOU records). One thing here you must be careful about. Like I said above, the model after TLS refinement contains ANISOU records. If you take such a model for individual B-factors refinement, phenix.refine will think that you are going to refine atoms with ANISOU records as individual anisotropic. To prevent phenix.refine from doing this you need to explicitly say that all atoms must be refined as isotropic (no matter what is in you PDB file). Here is how: % phenix.refine model_after_tls.pdb data.mtz adp.individual.isotropic=all For more information, details and examples, see new updated phenix.refine documentation here: http://phenix-online.org/new-site/documentation/refinement.htm We will work out something more automatic for this in future (including possibility to adjust wxu_scale when TLS is used). Thanks for your question and, as always, let me know if you have any other questions! Pavel. Jianghai Zhu wrote:
I will chime in. Is it possible for phenix.refine to get the TLS parameters from a previous run? then we can change wxu_scale value during an individual_adp refinement in the presence of fixed TLS parameters.
Jianghai
participants (3)
-
Jan Abendroth
-
Jianghai Zhu
-
Pavel Afonine