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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

CCP4BB Home

CCP4BB Home

CCP4BB  June 2015

CCP4BB June 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Residual density feature

From:

Colin Levy <[log in to unmask]>

Reply-To:

Colin Levy <[log in to unmask]>

Date:

Wed, 17 Jun 2015 10:10:44 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (187 lines)

Dear all,

Many thanks for the responses received,

To summarise the options for unidentified blobs appear to be:

1. Build something in and define it as a UNL (unknown ligand)

Some debate arose over the specifics of the term ³unknown ligand² and
wether a broader unknown entity description might be more accurate.

2. Leave the difference density and describe the location of the observed
feature using a SITE record.

As my intention was simply to draw attention to the presence of this
feature whilst not implying any identification I have chosen to go down
the latter route and simply leave the difference density for others to
ponder in the future.

Many thanks,

Colin




Manchester
Protein
Structure
Facility

Dr. Colin W. Levy
MIB G034
Tel. 0161 275 5090
Mob.07786 197 554
[log in to unmask]








On 16/06/2015 18:22, "Dale Tronrud" <[log in to unmask]> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>On 6/14/2015 2:49 AM, Robbie Joosten wrote:
>> Hi Colin,
>>
>> You can define an UNL (unknown ligand) in the blob. This is the
>> standard name for such a compound. It becomes a bit messy in
>> refinement in terms of restraints, but it does exactly what you
>> want it to do: say you noticed the blob but couldn't figure out
>> what it was.
>>
> There is danger along this route - but I suppose this is a
>philosophical matter. Your PDB file is your model for what is in the
>crystal. If you don't know what a compound in your crystal is, can
>you say that you have modeled it? What are your intentions when you
>place this "unknown" residue in your model -- Are you just placing a
>marker to tell those who follow that you noticed something here or are
>you saying "this is how electrons are arranged here".
>
> Recently I was looking at 1I1W for some reason. It is a very nice
>model at 0.89 A resolution. It contains, however, several single atom
>residues of type UNX and the atoms are of type X. The problem I have
>is that these atoms have their occupancy set to 1.0 and have varying B
>factors. What am I supposed to make of a fully occupied atom of
>unknown type?
>
> Apparently I'm not alone in my confusion. The Electron Density
>Server does not supply a map for this entry. I can see nothing wrong
>with the data nor the rest of the model so I presume the service is
>failing because it doesn't know how to calculate the scattering of an
>atom of unknown type.
>
> So, my question is - If you place marker atoms to indicate the
>binding of any unknown ligand, should the difference density disappear
>from your map? Certainly if you are interested in bootstrapping phase
>information you would want this, but is this appropriate for deposition?
>Should you be able to say your difference map is flat and your R value
>low when all you did was shrug your shoulders and say "I don't know"?
>
> There is a, sadly underused, feature of the PDB format called the
>SITE record. With it you can describe the residues of your protein
>that form a binding site and give a text description in a REMARK 800
>statement. This option would allow you to acknowledge that something
>is binding at this location but leave the difference peak for others
>to view and puzzle over on their own.
>
>Dale Tronrud
>
>> Cheers, Robbie
>>
>>> -----Original Message----- From: CCP4 bulletin board
>>> [mailto:[log in to unmask]] On Behalf Of Dom Bellini Sent:
>>> Sunday, June 14, 2015 11:36 To: [log in to unmask] Subject:
>>> Re: [ccp4bb] Residual density feature
>>>
>>> Dear Colin,
>>>
>>>
>>>
>>> I believe people usually refer to it as "unidentified blob" when
>>> depositing/writing in
>> these
>>> cases. But I wonder whether others may suggest better options.
>>>
>>>
>>>
>>> Best,
>>>
>>>
>>>
>>> D
>>>
>>> ________________________________ From: CCP4 bulletin board
>>> [[log in to unmask]] on behalf of Colin Levy
>>> [[log in to unmask]] Sent: 14 June 2015 09:53 To: ccp4bb
>>> Subject: [ccp4bb] Residual density feature
>>>
>>> Dear all,
>>>
>>> I am currently working on a structure that contains a residual
>>> density feature located
>> within
>>> the active site. Due to a combination of factors including
>>> limited occupancy, modest resolution, twinning etc it has not
>>> been possible to unambiguously identify this feature
>> despite
>>> fairly extensive efforts.
>>>
>>> What is the best way of dealing with such a feature when
>>> depositing the structure?
>> Ideally I
>>> would like to draw attention to the presence of residual density
>>> whilst not implying
>> that I have
>>> been able to identify it.
>>>
>>> Many thanks,
>>>
>>> Colin
>>>
>>>
>>> Manchester Protein Structure Facility
>>>
>>> Dr. Colin W. Levy MIB G034 Tel. 0161 275 5090 Mob.07786 197 554
>>> [log in to unmask]<mailto:[log in to unmask]>
>>>
>>>
>>> -- This e-mail and any attachments may contain confidential,
>>> copyright and or privileged material, and are for the use of the
>>> intended addressee only. If you are not the
>> intended
>>> addressee or an authorised recipient of the addressee please
>>> notify us of receipt by
>> returning
>>> the e-mail and do not use, copy, retain, distribute or disclose
>>> the information in or
>> attached to
>>> the e-mail. Any opinions expressed within this e-mail are those
>>> of the individual and not
>> necessarily of
>>> Diamond Light Source Ltd. Diamond Light Source Ltd. cannot
>>> guarantee that this e-mail or any attachments are free
>> from
>>> viruses and we cannot accept liability for any damage which you
>>> may sustain as a result
>> of
>>> software viruses which may be transmitted in or with the
>>> message. Diamond Light Source Limited (company no. 4375679).
>>> Registered in England and Wales with its registered office at
>>> Diamond House, Harwell Science and Innovation Campus, Didcot,
>>> Oxfordshire, OX11 0DE, United Kingdom
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2.0.22 (MingW32)
>
>iEYEARECAAYFAlWAW3AACgkQU5C0gGfAG12vbQCgubFnSV97Xu/GLtOlW9T7il56
>rYQAniTJS2Rt6tLUeNCX0xSjFBaxIW56
>=gPOx
>-----END PGP SIGNATURE-----

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