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  February 2016

CCP4BB February 2016

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Individual B-factors at low resolution: a cautionary tale?

From:

Paul Adams <[log in to unmask]>

Reply-To:

Paul Adams <[log in to unmask]>

Date:

Fri, 12 Feb 2016 09:21:45 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (271 lines)

Hi Tristan,

  what you observe makes a lot of sense - and I would advocate the use of TLS for sure. Any B-factor model is going to have problems when the underlying coordinates are incorrect. 

  Cheers,
	Paul

> On Feb 12, 2016, at 2:08 AM, Tristan Croll <[log in to unmask]> wrote:
> 
> Hi Paul,
> 
> The structures that I've been primarily focusing on are mostly historical ones like the one that belongs to the attached validation slider, that were largely or entirely hand-built into 3.5-4 Angstrom density using mid-2000s tools. It's no secret that large errors are common in such structures - not just poor backbone conformation or incorrect rotamers, but substantial shifts in register. In such situations, if you give the refinement an inch it will take a mile. When you have register shifts that leave a Ser in place of a Met, or loops threaded through density that turns out to be fictional, *any* B-factor you apply will be wrong, and if it has the freedom to do so the refinement will do its best to pick a B-factor that makes the model seem less wrong. Nearest-neighbour restraints certainly help, but when the neighbour (and its neighbour, and *its* neighbour) is also wrong, then you're still left with scope for a lot of over-fitting - and every individual instance of over-fitting has a ripple effect throughout the structure.
> 
> In these situations, I've found time and again that the simpler TLS-only model leads to maps that are *far* more interpretable, where I can clearly and easily identify the source and solution of a problem that was previously obscure. The 2mFo-DFc maps become sharper and stronger - but more importantly, so do the mFo-DFc maps. A great deal of noise seems to go away, and weak regions in particular tend to become more connected (not model bias as far as I can tell, because the new connections tend to point to improvements in the structure).
> 
> All that being said, once the model is closer to a finished state where the bulk (>>90%) is well-fitted and all the quality indicators are in good shape (by "good shape" here, I mean that I currently have this structure at a clashscore of 2.6, Rama favoured/outliers at 93.5/0.48%, and rotamer outliers at 1.17%, with Rfree almost 3% lower than the original), then I find that adding restrained individual B-factor refinement can help - *if* the TLS-only model has converged first. If I start from an entirely reset model, it's very variable - sometimes it converges well, sometimes it runs away entirely... and sometimes, like in my original example here, it seems to converge well but starts losing previously-resolved details.
> 
> Best regards,
> 
> Tristan
> 
> ________________________________________
> From: CCP4 bulletin board <[log in to unmask]> on behalf of Paul Adams <[log in to unmask]>
> Sent: Friday, 12 February 2016 4:23 AM
> To: [log in to unmask]
> Subject: Re: [ccp4bb] Individual B-factors at low resolution: a cautionary tale?
> 
> We observe the same thing with the ADP restraints used in Phenix. The local distance-based restraints on displacements are very effective even at low resolution. There is scope for improvement no doubt, but users are encouraged to use individual restrained ADPs even at low resolution rather than grouped displacements.
> 
>> On Feb 11, 2016, at 9:45 AM, Zbyszek Otwinowski <[log in to unmask]> wrote:
>> 
>> Refmac has made a lot of progress in refining individual B-factors at very
>> low resolution. At such resolution, the procedure is not always stable;
>> however, with some effort, we have found a considerable improvement of
>> R-free in all our 4-5 A resolution limit data.
>> 
>> The same applies to the refinement of anisotropic B-factors, it may work
>> at much lower resolution (e.g. 2A) than typically assumed.
>> 
>> To achieve improvement in the above situations, we perform many
>> alternative strategies of the refinement. These strategies depend on the
>> version of Refmac and type of problem and quality of the model. The better
>> the model, the more improvement we observe.
>> 
>> Our experience may, or may not, apply to Phenix and other refinement
>> programs as the differences between programs are likely to be significant.
>> Our observations are consistent with past negative experience with regard
>> to B-factor refinement; however, in most situations we could find a
>> work-around.
>> 
>> Zbyszek Otwinowski
>> 
>> 
>>> There must be some middle ground here, in the form of a restraint scheme
>>> that allows one to gracefully reduce the effective parameter count as the
>>> resolution decreases, without "step changes" between different schemes.
>>> Perhaps by applying some variation on a LOWESS smooth to the B-factors,
>>> with the strength of the weighting term determined by the Wilson B factor?
>>> 
>>> 
>>> ________________________________
>>> From: Bjørn Pedersen <[log in to unmask]>
>>> Sent: Thursday, 11 February 2016 6:05 PM
>>> To: Tristan Croll
>>> Cc: [log in to unmask]
>>> Subject: Re: [ccp4bb] Individual B-factors at low resolution: a cautionary
>>> tale?
>>> 
>>> Hi Tristan,
>>> I think your reasoning makes a lot of sense. I would be skeptical of the
>>> use of individual B-factors at this resolution of 3.6A in general, working
>>> with 'low-quality' anisotropic data etc. Regions with extremely high
>>> b-factors should help to warn you that you could be 'falling' into a local
>>> minimum hole.
>>> With think kind of data I often find it useful to 'reset' all B-factors in
>>> my current model to the estimated Wilson B-factor once in a while. That
>>> helps me to escape the local minimum of the model (along with multiple
>>> parallel rounds of simulated annealing tracking the R-factors of the
>>> low-resolution shells).
>>> 
>>> The followup question I have is more along the lines of whether it would
>>> ever be justifiable to use individual B-factors at this resolution? I have
>>> always been a proponent of the one/two B-factors per residue in this
>>> resolution range, but I was wondering what the community thinks of this
>>> these days, with current improvements in target functions, parametizations
>>> etc etc?
>>> 
>>> All the best
>>> -Bjørn
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Mon, Feb 8, 2016 at 7:46 PM, Tristan Croll
>>> <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>>> 
>>> For the most part they haven't moved far (1-2 tenths of an Angstrom in the
>>> backbone, further for sidechains) - and secondary structure remains
>>> essentially unchanged, which is a plus. I think it will come good with a
>>> little more tinkering.
>>> 
>>> 
>>> ________________________________
>>> From: Eleanor Dodson
>>> <[log in to unmask]<mailto:[log in to unmask]>>
>>> Sent: Tuesday, 9 February 2016 4:28 AM
>>> 
>>> To: Tristan Croll
>>> Cc: [log in to unmask]<mailto:[log in to unmask]>
>>> Subject: Re: [ccp4bb] Individual B-factors at low resolution: a cautionary
>>> tale?
>>> 
>>> Yes - the really isnt enough information at that resolution to support the
>>> number of parameters with xy,z,b per atom. Do your atoms move away from
>>> their correct positions too?
>>> 
>>> On 8 February 2016 at 18:22, Tristan Croll
>>> <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>>> 
>>> 
>>> That's OK - I tend to be very hands-on with my corrections. :)
>>> 
>>> 
>>> But what has me interested is not so much this, but that refining with
>>> individual B-factors actually seems to end up obscuring the information
>>> that says where the wrong atoms should go! In this particular case I went
>>> through multiple rounds of rebuilding/refinement of this domain, where
>>> successive adjustments simultaneously improved fit to the map, resolved
>>> clashes and improved the secondary structure, and each refinement with a
>>> TLS-only model led to sharper and stronger density. Then with a few rounds
>>> of rebuilding elsewhere combined with individual B-factor refinement, it's
>>> all but gone. I think it really argues for the idea that at these
>>> resolutions the B-factor model should be kept as simple as possible while
>>> rebuilding, and only extended to individual B-factors (if at all) in a
>>> final round for deposition.
>>> 
>>> 
>>> Cheers,
>>> 
>>> 
>>> Tristan
>>> 
>>> ________________________________
>>> From: Eleanor Dodson
>>> <[log in to unmask]<mailto:[log in to unmask]>>
>>> Sent: Tuesday, 9 February 2016 4:02 AM
>>> To: Tristan Croll
>>> Cc: [log in to unmask]<mailto:[log in to unmask]>
>>> Subject: Re: [ccp4bb] Individual B-factors at low resolution: a cautionary
>>> tale?
>>> 
>>> Yes - I think you are right. We use "B factors" as mop-up-error factors.
>>> If the atoms are in the wrong place a very high B factor is a useful
>>> indicator that the atom should be deleted or moved! But you will probably
>>> need to do some hands-on correction to use the information
>>> Eleanor
>>> 
>>> 
>>> 
>>> On 8 February 2016 at 10:18, Tristan Croll
>>> <[log in to unmask]<mailto:[log in to unmask]>> wrote:
>>> 
>>> Hi all,
>>> 
>>> 
>>> The attached image depicts the weakest region of the 3.6 Angstrom
>>> structure I've been working on. The three maps shown are 2mFo-DFc at 1
>>> sigma, from three different refinements. The purple one is the first,
>>> after extensive rebuilding and refinement using strictly a TLS-only
>>> B-factor model. Not strong, but after sharpening and cross-checking with
>>> its slightly better resolved NCS partner, enough to be happy with it. The
>>> green map is the result of taking the refined TLS-only model and further
>>> refining with individual B-factors. So far so good - the maps are more or
>>> less the same.
>>> 
>>> 
>>> The blue surface is the current map, after multiple rounds of rebuilding
>>> in the (much) more strongly resolved regions, with TLS plus restrained
>>> individual B-factor refinement from a blank slate in between each round.
>>> It's looking... not so great.
>>> 
>>> 
>>> This result make a lot of sense when I think about it further - but just
>>> to check if my reasoning is correct:
>>> 
>>> 
>>> One way to look at refinement with a single overall B-factor is that
>>> you're implicitly "flattening" your model - increasing the contribution of
>>> the weakly resolving regions, and decreasing the contribution of the
>>> stronger regions - akin to adjusting the contrast in a photograph. That's
>>> reflected (no pun intended) in the maps becoming stronger in these areas
>>> and a general sharpening throughout, even if the R factors are 1-2% higher
>>> than with individual B-factors. Most importantly, though, I think it
>>> forces the refinement algorithms to pay more attention to the coordinates
>>> in these regions. Once these are refined to convergence in the TLS-only
>>> B-factor model, then it seems safe to introduce individual B-factors since
>>> the refinement will simply fall further into the current local minimum.
>>> But if the model is refined from scratch with individual B-factors, then
>>> it's much easier for the refinement to over-fit the strongly resolving
>>> regions, balanced by smearing out the weak ones - significantly reducing
>>> the interpretability of weaker regions and resulting in an overall
>>> poorer-quality model.
>>> 
>>> 
>>> Does this make sense?
>>> 
>>> 
>>> Best regards,
>>> 
>>> 
>>> Tristan
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> Zbyszek Otwinowski
>> UT Southwestern Medical Center at Dallas
>> 5323 Harry Hines Blvd.
>> Dallas, TX 75390-8816
>> Tel. 214-645-6385
>> Fax. 214-645-6353
> 
> --
> Paul Adams
> Interim Division Director, Molecular Biophysics & Integrated Bioimaging, Lawrence Berkeley Lab
> Division Deputy for Biosciences, Advanced Light Source, Lawrence Berkeley Lab
> Adjunct Professor, Department of Bioengineering, U.C. Berkeley
> Vice President for Technology, the Joint BioEnergy Institute
> Laboratory Research Manager, ENIGMA Science Focus Area
> 
> Building 33, Room 347
> Building 80, Room 247
> Building 978, Room 4126
> Tel: 1-510-486-4225, Fax: 1-510-486-5909
> http://cci.lbl.gov/paul
> 
> Lawrence Berkeley Laboratory
> 1 Cyclotron Road
> BLDG 33R0345
> Berkeley, CA 94720, USA.
> 
> Executive Assistant: Louise Benvenue [ [log in to unmask] ][ 1-510-495-2506 ]
> --
> <multipercentile_validation.png>

-- 
Paul Adams
Interim Division Director, Molecular Biophysics & Integrated Bioimaging, Lawrence Berkeley Lab
Division Deputy for Biosciences, Advanced Light Source, Lawrence Berkeley Lab
Adjunct Professor, Department of Bioengineering, U.C. Berkeley
Vice President for Technology, the Joint BioEnergy Institute
Laboratory Research Manager, ENIGMA Science Focus Area

Building 33, Room 347
Building 80, Room 247
Building 978, Room 4126
Tel: 1-510-486-4225, Fax: 1-510-486-5909
http://cci.lbl.gov/paul

Lawrence Berkeley Laboratory
1 Cyclotron Road
BLDG 33R0345
Berkeley, CA 94720, USA.

Executive Assistant: Louise Benvenue [ [log in to unmask] ][ 1-510-495-2506 ]
--

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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