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: Ligand at four fold NCS axis

From:

Dale Tronrud <[log in to unmask]>

Reply-To:

Dale Tronrud <[log in to unmask]>

Date:

Sun, 7 Feb 2016 16:04:07 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

   My bad!  As Boaz Shaanan pointed out to me, I missed the "NCS" in
your subject line.  This means that my answer was not relevant to your
question.

   The source of the confusion surrounding your situation is that the
PDB file format does not easily allow one to describe exactly what your
model is.  What you really have is a tetramer with a single ligand at
its center, which breaks its symmetry and makes it a P1 particle.  This
entire particle sits in the crystal in a disordered fashion, since the
outside has four-fold symmetry.  Refinement programs are not going to
like four entire tetramers at 1/4 occupancy where nearly all the atoms
superimpose.

   Compounding the problem is the fact that the PDB file format does not
really specify what the relationship is between the "A" alternative
location of residue 1 and the "A" alternative location of residue 2.  I
would prefer to think that 1.A can bond to 2.A and have bad contacts
with 2.A but not to 2.B, but the format doesn't say that.  And if it
did, we would run out of letters for alt locs pretty fast.

   If you define your ligand to have four different names, the
refinement program will assume you mean that there are four residues in
the same universe and assume there are bad contacts between them.  If
you give the ligands four different names but specify different alt locs
(e.g. 1.A, 2.B, 3.C, and 4.D) the program still can't safely assume
there should be no bad contacts (because of the vague format
specification).  You should be able to give all four molecules the same
name but different alt locs (e.g. 1.A, 1.B, 1.C, and 1.D) and the bad
contacts should be ignored.  If there are alt locs for the surrounding
protein atoms that match the alt locs of your ligand you are back to the
format specification problem - it is not safe to assume that 123.A is in
the same universe as 1.A.

   When you find that the program is pushing apart atoms that you don't
think should be seeing each other, you can either change the names (and
there may be no workable naming solution) or use the tool in the
refinement program to tell it to ignore particular bad contacts.  Every
refinement program has such a tool.  The fact that you have to add this
ad hoc override is not a flaw in the program, it is a flaw in the file
format.

Dale Tronrud


On 2/7/2016 7:03 AM, Boaz Shaanan wrote:
> Hi Dale,
> 
> Just wondering:  is the scenario your're describing also valid for 4-fold NCS axis (as is the case here), where the occupancies may not be as strictly related ? It sounds to me more  relevant to crystallographic 4-fold axis but I could well be wrong of course. 
> 
> Cheers,
> 
>                 Boaz
> 
> 
> Boaz Shaanan, Ph.D.
> Dept. of Life Sciences
> Ben-Gurion University of the Negev
> Beer-Sheva 84105
> Israel
> 
> E-mail: [log in to unmask]
> Phone: 972-8-647-2220  Skype: boaz.shaanan
> Fax:   972-8-647-2992 or 972-8-646-1710
> 
> 
> 
> 
> 
> ________________________________________
> From: CCP4 bulletin board [[log in to unmask]] on behalf of Dale Tronrud [[log in to unmask]]
> Sent: Saturday, February 06, 2016 10:46 PM
> To: [log in to unmask]
> Subject: Re: [ccp4bb] Ligand at four fold NCS axis
> 
>    If you have a ligand sitting on a four-fold axis, let's call the four
> residues 1, 2, 3, 4.  Residues 2, 3, and 4 are generated by the
> refinement program using symmetry so the occupancy of 1 should be set to
> 0.25 to generate a total occupancy of 1.0.
> 
>    Now you say that residue 1 has four conformations.  Let's call them
> 1.A, 1.B, 1.C and 1.D.  The sum of the occupancies of these
> conformations have to add up to the occupancy of 1.  If their
> occupancies are equal you have to set them to 0.0625 (or 1/16).
> 
>    The refinement program will generate 2.A, 3.C and all the rest.
> 
> Dale Tronrud
> 
> On 2/6/2016 11:41 AM, Appu kumar wrote:
>> Dear CCp4 Users,
>> I am refining a tetrameric protein which has ligand placed at the center
>> axis. There is one tetramer in ASU.  I added the ligand with 0.25
>> occupancy and performed the refinement using both phenix and refmac.
>> Refinement leaves lots of green density around the ligand inferring that
>> there may be four different conformation of the ligand. When i made four
>> different conformation of ligand (each with 0.25 occupancy) and started
>> refinement, there is lot of clashes in ligand itself. Is there a ways to
>> refine the four different conformation of ligand with different
>> conformation with 0.25 occupancy avoiding clashes in ligands?
>>
>> I appreciate your input, suggestions  on the refinement.
>>
>> Thank you
>> Appu
> 

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