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  December 2010

CCP4BB December 2010

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Fwd: [ccp4bb] Wyckoff positions and protein atoms

From:

Ian Tickle <[log in to unmask]>

Reply-To:

Ian Tickle <[log in to unmask]>

Date:

Wed, 15 Dec 2010 14:47:11 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (235 lines)

Dear George

I notice that the Oxford CRYSTALS program, which is what I used when I
did small-molecule crystallography and which is still quite popular
among the small-molecule people (maybe not as much as Shel-X!), uses
the CIF convention:

OCC= This parameter defines the site occupancy EXCLUDING special
position effects (i.e. is the 'chemical occupancy'). The default is
1.0.  Special position effects are computed by CRYSTALS and multiplied
onto this parameter.

(from http://www.xtl.ox.ac.uk/crystalsmanual-atomic.html )

Also the mmCIF specification on this is the same CIF one (hardly
surprising I guess since it's derived from it):

_atom_site.occupancy  The fraction of the atom type present at this site.
The sum of the occupancies of all the atom types at this site may not
significantly exceed 1.0 unless it is a dummy site.

(from http://mmcif.pdb.org/dictionaries/mmcif_std.dic/Items/_atom_site.occupancy.html
)

which doesn't say so specifically, but it's implied since if the
multiplicity is included then the maximum value of the sum is the
multiplicity, not 1.0.

So there's a real possibility of user - and programmer - confusion
here!  I must say that until I looked at the 4INS file I had assumed
that the PDB occupancy was what it claimed to be, i.e. the real
'chemical' occupancy not the multiplicity-fudged one.

Cheers

-- Ian

On Wed, Dec 15, 2010 at 1:53 PM, George M. Sheldrick
<[log in to unmask]> wrote:
>
> Dear Ian,
>
> Yes. Once an atom has been identified as on a special position because it
> is within a specied tolerance, SHELXL applies the appropriate contraints
> to both the coordinates and the Uij so there is no danger of the atom
> wandering off the special position. Usually, when an atom it very close to
> a special position but not actually on it, it is part of a disordered
> solvent molecule and will be prevented from misbehaving by distance and
> Uij restraints imposed by the user; in such a case the user usually also
> switches off the special position check for that disordered molecule
> (SPEC -1) to avoid atoms being idealized onto the special position by the
> program. For solvent molecules disordered on special positions it is
> also necessary to ignore symmetry equivalent atoms when generating
> idealized hydrogen atoms etc. (PART -N in SHELXL). This is all routine
> practice in small molecule crystallography. I agree that the use of
> orthogonal rather than crystal coordinates can obscur the situation,
> e.g. for an atom on a threefold axis.
>
> Best wishes, George
>
> Prof. George M. Sheldrick FRS
> Dept. Structural Chemistry,
> University of Goettingen,
> Tammannstr. 4,
> D37077 Goettingen, Germany
> Tel. +49-551-39-3021 or -3068
> Fax. +49-551-39-22582
>
>
> On Wed, 15 Dec 2010, Ian Tickle wrote:
>
>> Dear George
>>
>> I would say that an atom has fractional occupancy (but unit
>> multiplicity) unless it's exactly on the special position (though I
>> can foresee problems with rounding of decimal places for an atom say
>> at x=1/3), so that effectively once the atom is fixed exactly on the
>> s.p. the symmetry copies coalesce into a single atom with unit
>> occupancy (but fractional multiplicity).  This is at least one
>> advantage of having co-ordinates stored as fractional - it would
>> probably be more tricky with orthogonalised co-ordinates.  Presumably
>> once an input atom has satisfied the condition of being 'sufficiently
>> close' to a s.p. to be considered as 'on' the s.p. then the
>> constraints fix the co-ordinates exactly on the special position and
>> henceforth it's forcibly prevented from moving off it?  In any case if
>> an atom is very close to its symmetry copy you are going to have
>> matrix conditioning problems for the co-ordinates perpendicular to the
>> axis of symmetry (or mirror plane), so then you have no choice but to
>> disallow co-ordinate shifts of the atom which would take it off the
>> special position?
>>
>> Cheers
>>
>> -- Ian
>>
>> On Wed, Dec 15, 2010 at 11:42 AM, George M. Sheldrick
>> <[log in to unmask]> wrote:
>> >
>> > Dear Ian,
>> >
>> > Of course I could convert the occupancy on reading the atom in and convert
>> > it back agains on reading it out. This is not quite so trivial as it
>> > sounds because I need to set a threshold as to how close the atom has
>> > to be to a special position to be treated as special, and take care
>> > that rounding errors have the same effect on input and output and that
>> > the coordinates have not moved in or out of the special zone in the
>> > meantime.
>> >
>> > As it stands in SHELX, an atom that is near to a twofold will have an
>> > occupancy of 0.5 whether it is disordered close to a special position
>> > or whether it is really special, so this is never a problem.
>> >
>> > SHELXL is mainly used for small molecules that frequently have atoms on
>> > speical positions, and disordered solvent molecules approximately on
>> > sppecial positions are also very common (for example in centrosymmetric
>> > space groups toluene usually lies on the center of symmetry). Occupancies
>> > are often tied to free variables which would also complicate any changes
>> > to the code. And in any case, SHELX has been upwards compatible for the
>> > last 35 years and I wish it to remain that way.
>> >
>> > Best wishes, George
>> >
>> > Prof. George M. Sheldrick FRS
>> > Dept. Structural Chemistry,
>> > University of Goettingen,
>> > Tammannstr. 4,
>> > D37077 Goettingen, Germany
>> > Tel. +49-551-39-3021 or -3068
>> > Fax. +49-551-39-22582
>> >
>> >
>> > On Wed, 15 Dec 2010, Ian Tickle wrote:
>> >
>> >> Dear George
>> >>
>> >> Is applying the multiplicity factor to the occupancy internally in the
>> >> program such a issue anyway?  It need only be done once per atom on
>> >> input (i.e. you multiply each input occupancy by the multiplicity to
>> >> get the combined multiplicity*occupancy value that you would have
>> >> reading in directly in the current version), and then once per atom
>> >> again on output, reversing the process.  There shouldn't be any need
>> >> to change anything in the inner atom/reflection loop where obviously
>> >> it would indeed have slowed things down.
>> >>
>> >> I can see though that the backwards-compatibility issue is more
>> >> serious.  However I suspect it will affect only a small proportion of
>> >> cases (though I accept that the fact that it may affect any at all may
>> >> be sufficient grounds for you to reject it!).  If the input value
>> >> exceeds the multiplicity we can say that it's definitely an occupancy
>> >> (otherwise clearly the occupancy would be > 1).  If it's less there's
>> >> an ambiguity for sure; however then it's more likely to be the
>> >> multiplicity*occupancy (so the occupancy is nearer to 1), on the
>> >> grounds that small occupancies are less likely to be observed, because
>> >> the effect on diffraction will be less significant.  I accept that
>> >> second-guessing the user's intentions in this way is not ideal!  I
>> >> wonder how often fractional occupancies are observed at special
>> >> positions anyway?
>> >>
>> >> Regards
>> >>
>> >> -- Ian
>> >>
>> >> On Fri, Dec 10, 2010 at 11:28 PM, George M. Sheldrick
>> >> <[log in to unmask]> wrote:
>> >> > SHELXL also expects that the occupancy of a fully occupied atom on a
>> >> > threefold axis should be set at 1/3, and will generate this automatically
>> >> > if necessary. It will also generate automatically the necessary
>> >> > constraints for the x, y and z parameters (and for the Uij if the atom is
>> >> > anisotropic). It is essential that this is done correctly if a full-matrix
>> >> > refinement is being performed (e.g. to get esd estimates), otherwise
>> >> > the refinement can explode. The user may change or switch off the
>> >> > tolerance for detecting whether an atom is on a special position
>> >> > (with the SPEC instruction). Setting the occupancy to a fraction avoided
>> >> > a complicated IF construction inside a loop and 35 years ago computers
>> >> > were so slow! I can't change it now because I have to preserve upwards
>> >> > compatibility. Unfortunately the CIF committee decided to use the other
>> >> > definition (i.e. the Zn on the threefold axis has an occupancy of 1.0)
>> >> > and this has caused considerable confusion in the small molecule world
>> >> > ever since; atoms are frequently encountered on special positions in
>> >> > inorganic and mineral structures.
>> >> >
>> >> > George
>> >> >
>> >> > Prof. George M. Sheldrick FRS
>> >> > Dept. Structural Chemistry,
>> >> > University of Goettingen,
>> >> > Tammannstr. 4,
>> >> > D37077 Goettingen, Germany
>> >> > Tel. +49-551-39-3021 or -3068
>> >> > Fax. +49-551-39-22582
>> >> >
>> >> >
>> >> > On Fri, 10 Dec 2010, Ed Pozharski wrote:
>> >> >
>> >> >> On Fri, 2010-12-10 at 21:53 +0000, Ian Tickle wrote:
>> >> >> > Hmmm - but shouldn't the occupancy of the Zn be 1.00 if it's on the
>> >> >> > special position
>> >> >>
>> >> >> Shouldn't 1/3 be better for programming purposes?  If you set occupancy
>> >> >> to 1.0, then you should specify that symmetry operators do not apply for
>> >> >> these atoms, making Fc calculation a bit more cumbersome.
>> >> >>
>> >> >> If definition of the "asu content" is "you get full content of the unit
>> >> >> cell after applying symmetry operators", then occupancy *must* be 1/3,
>> >> >> right?
>> >> >>
>> >> >> The first zinc and the water are on special position, but because they
>> >> >> are not excluded from positional refinement (perhaps they should be),
>> >> >> they will drift a bit.  CNS has distance cutoff for treating atoms as
>> >> >> special positions, if it jumps over the limit during, say, simulated
>> >> >> annealing, it  will cause problems.  Perhaps PROLSQ did something
>> >> >> similar.  It is a good question if it's better to fix these in place or
>> >> >> let them wobble a bit to account for some potential disorder.  While I
>> >> >> see the formal argument that it should be nailed to three-fold axes, it
>> >> >> is also true that this is a mathematical compromise to simplify modeling
>> >> >> that does not reflect physical reality (i.e. you don't have three
>> >> >> partially occupied zinc ions, it's just one).  In any event, given that
>> >> >> this is a 1.5A structure, (-0.002 0.004) is statistically speaking the
>> >> >> same as (0 0).
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Ed.
>> >> >>
>> >> >> --
>> >> >> "I'd jump in myself, if I weren't so good at whistling."
>> >> >>                                Julian, King of Lemurs
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>>
>>

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