JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for CCP4BB Archives


CCP4BB Archives

CCP4BB Archives


CCP4BB@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  November 2008

CCP4BB November 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Choosing TLS groups.

From:

Ian Tickle <[log in to unmask]>

Reply-To:

Ian Tickle <[log in to unmask]>

Date:

Fri, 14 Nov 2008 11:57:19 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (161 lines)

 
Hi Pavel

I think Ethan made my point very nicely, so I don't really have much to
add, except maybe a concrete example will help.  Let's keep it as simple
and ideal as possible: I hope you'll agree that any proposed method has
to at least work perfectly in the ideal case before you try to apply it
in the general case (at least that's how I always test my software!), so
let's construct a simple, ideal situation and see how well the
alternative methods stack up.

First let's suppose that we have 2 domains (A & B) connected by a single
bond parallel to the x axis, and the only rigid-body motion is a 1 A^2
mean-square displacement also parallel to x for both domains, so T11(A)
= T11(B) = 1 A^2 and all other TLS elements for both A & B are
identically zero.  Suppose also that the rigid-body motion describes the
actual atomic motion exactly which means of course that all the residual
Biso's will be zero, and also that the total Biso's of all atoms in both
A & B will be 8pi^2/3 (mean of the diagonal elements).  In particular
the differences between both residual Biso's and total Biso's for the 2
connecting atoms will be zero, and the rigid-bond test is satisfied.  So
obviously it won't make any difference whether we restrain residual B
difference or total B difference, the restraint will give the right
result in either case.

Now let's assume the same setup, except that now T11(B) = 0.5 A^2, but
the rigid-bond test still demands that the total Biso's (representing
the actual motion of the atoms) for the connecting atoms have zero
difference, let's suppose they are both still 8pi^2/3.  This means that
the residual Biso's for the connecting atoms in A & B are zero and
4pi^2/3 respectively.  Hence restraining the difference between residual
Biso's to zero will give a result that does not correspond to reality,
restraining the difference between total Biso's does (in fact this is
merely a direct consequence of the rigid-bond test).

I guess I'm saying the same thing as Ethan, he said it more eloquently,
I just like to see what happens when you plug in actual values.

Cheers

-- Ian


> -----Original Message-----
> From: [log in to unmask] 
> [mailto:[log in to unmask]] On Behalf Of Ethan A Merritt
> Sent: 14 November 2008 06:06
> To: Pavel Afonine
> Cc: [log in to unmask]
> Subject: Re: [ccp4bb] Choosing TLS groups.
> 
> On Thursday 13 November 2008, Pavel Afonine wrote:
> > Hi Ian,
> > 
> > > All - I was just in a discussion about TLS and one thing 
> that came out
> > > that I hadn't been aware of is that for the Biso restraints Refmac
> > > restrains the difference between the 'residual' Bs, i.e. 
> with the TLS
> > > contributions subtracted, not the 'total' Bs.  Now it 
> seems to me that
> > > this isn't quite correct, because it's the total motion 
> of the atoms
> > > that matters, i.e. the total mean square along-bond 
> displacements for
> > > bonded atoms should be equal.  However, I can see that in 
> practical
> > > terms it won't make any significant difference provided 
> appropriate
> > > precautions are taken with the choice of TLS groups.
> > >   
> > 
> > given the formula for total atomic B-factor:
> > 
> > Btotal = Bcryst + Btls + Blocal + ...
> > 
> > my naive understanding is that the B-factors describing 
> local atomic 
> > vibrations Blocal (or residual B-factors as named in 
> Refmac) should obey 
> > Hirshfeld's "rigid-bond test" (Acta Cryst. (1976). A32, 
> 239-244), which 
> > is (to some approximation) enforced by the  restraints applied to 
> > "residual" B-factors (as it is Refmac or in phenix.refine).
> 
> It makes perfect sense to apply the restraints to the residual B
> _within_ a TLS group.  Furthermore, the along-bond variance from the
> Btls component is zero for atoms within the group anyhow (by 
> definition).
> So for two atoms in the same TLS group, applying the restraint to the
> total is numerically identical to applying it to the residual B only.
> 
> But this doesn't address Ian's concern about discontinuities across
> a group boundary.  If two neighboring atoms are in different 
> TLS groups,
> then the along-bond variance from the two Btls components is 
> different.
> Hence in this case the _total_ B should be restrained.
> 
> > I think given the arbitrariness (or accuracy if you like) 
> in defining 
> > TLS groups, applying similarity restraints to the total B 
> would not be a 
> > good idea. 
> 
> I do not follow you thinking on that point.  If restraining the total
> B is a good idea in the usual refinement protocol, either isotropic or
> anisotropic, in how would it suddenly become not a good idea in
> the presence of a TLS-based protocol?
> 
> The TLS description is not "truth". It is a convenient model 
> that allows
> us to predict (or explain) the ADP for each atom. Because it is only a
> model, not truth, we should restrain it to conform to our 
> prior knowledge.
> In this particular case the prior expectation is that the net ADPs
> of adjacent atoms are compatible, which means that their along-bond
> components should be equal.  Therefore it only makes sense to 
> apply the
> restraint to the net ADP.
> 
> Think of it like this.  The same formulae which express the 
> "restraint"
> also express the extent to which the current model deviates from our
> ideal for a "good" model.  If I hand you a refined model, you can
> calculate this deviation from goodness without even a hint as to
> how I arrived at that model.  It might have been Biso only, it might
> have been TLS, it might have been a random drawing of B values from
> a large hat.  Doesn't matter.  The same is true if you apply the
> restraint during refinement;  if it's a good restraint, it's good 
> regardless of how your model B factors are generated.
> 
> > I faced this dilemma a few years ago when implementing TLS  
> > refinement in phenix.refine. And to prove my feelings and make a 
> > decision, I systematically tried both possibilities, and 
> the best result 
> > was to apply the restraints to residual B-factors. 
> 
> I hesitate to suggest it, but...
> might this be pointing to a coding error rather than to a flaw in the
> rationale?  
> 
> > The NCS restraints are applied to residual B-factors too
> > (although I didn't test it systematically).
> 
> Applyinig NCS restraints to B factors is a whole separate area
> for discussion. Let's not go there just now :-)
> 
> -- 
> Ethan A Merritt
> Biomolecular Structure Center
> University of Washington, Seattle 98195-7742
> 
> 


Disclaimer
This communication is confidential and may contain privileged information intended solely for the named addressee(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient you must not review, use, disclose, copy, distribute or take any action in reliance upon it. If you have received this communication in error, please notify Astex Therapeutics Ltd by emailing [log in to unmask] and destroy all copies of the message and any attached documents. 
Astex Therapeutics Ltd monitors, controls and protects all its messaging traffic in compliance with its corporate email policy. The Company accepts no liability or responsibility for any onward transmission or use of emails and attachments having left the Astex Therapeutics domain.  Unless expressly stated, opinions in this message are those of the individual sender and not of Astex Therapeutics Ltd. The recipient should check this email and any attachments for the presence of computer viruses. Astex Therapeutics Ltd accepts no liability for damage caused by any virus transmitted by this email. E-mail is susceptible to data corruption, interception, unauthorized amendment, and tampering, Astex Therapeutics Ltd only send and receive e-mails on the basis that the Company is not liable for any such alteration or any consequences thereof.
Astex Therapeutics Ltd., Registered in England at 436 Cambridge Science Park, Cambridge CB4 0QA under number 3751674

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager