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: bespoke _chem_link in refmac

From:

"Borhani, David" <[log in to unmask]>

Reply-To:

Borhani, David

Date:

Sun, 23 Nov 2008 18:48:46 -0500

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (113 lines) , CAU+CLR+BU1+MAL+12P+ACM+Links+Na_mon_lib.cif (113 lines)

Judit,

Refmac does seem to be very picky about the order. See attached file in
which I had to add several links; this file works, so a few minutes of
reverse engineering on your part should make it clear what you need to
do in what order. Hope this helps,

Dave

David Borhani, Ph.D.
D. E. Shaw Research, LLC
120 West Forty-Fifth Street, 39th Floor
New York, NY 10036
[log in to unmask]
212-478-0698
http://www.deshawresearch.com

 

> -----Original Message-----
> From: CCP4 bulletin board [mailto:[log in to unmask]] On 
> Behalf Of Debreczeni, Judit
> Sent: Friday, November 21, 2008 7:19 AM
> To: [log in to unmask]
> Subject: [ccp4bb] bespoke _chem_link in refmac
> 
> Hi,
> 
> if you feel you are good at _chem_link sections of dictionary 
> files (and know how refmac understands them), please read on.
> 
> My question in short:
> what is the Right Way of defining a covalent link between a 
> ligand that is not in the standard refmac library and a 
> standard amino acid residue, using _chem_link?
> 
> 
> Longer version:
> I have a series of ligands binding covalently to the same 
> residue with the same geometry, therefore it seems reasonable 
> to define a link for all of them (and use that as an 
> invariant part of the description of the ligands and their 
> bond to the protein). [1]
> 
> I've generated _chem_link and _chem_comp descriptions, merged 
> them in one cif file and wrote a LINK card in the pdb file. 
> The ligand description corresponds to the one in the bound 
> state so no _chem_mod should be required. Still, haven't had 
> much luck with refmac:
>     1. if the _chem_link section precedes the _chem_comp part 
> in the cif file: refmac doesn't seem to recognise the ligand 
> and fails.
>     2. if the _chem_comp part comes first in the cif file, 
> refmac fails with "CYS-INH  not found in the list of links" 
> (where CYS-INH is the _chem_link I defined).
>     3. if the _chem_link_list and _chem_comp_list precede the 
> actual descriptions in the file, refmac simply ignores the 
> link part, which in turn results in a distorted geometry of 
> the ligand-protein bond. There's no warning about 
> unrecognised links in the log file.
> 
> What am I missing here?
> 
> Any suggestion most welcome.
> JED
> 
> 
> [1] I could simply treat the ligand and amino acid residue as 
> one single unit, but computational chemists would like to see 
> them as separate entities, so refining them together (i.e. as 
> a modified amino acid) is not an option. Not very straight 
> forward, anyway.
> Defining one ligand as starting point and generate the others 
> with _chem_mod is somewhat tedious to script, so I dropped 
> that option too.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --------------------------------------------------------------
> ------------
> AstraZeneca UK Limited is a company incorporated in England 
> and Wales with registered number: 03674842 and a registered 
> office at 15 Stanhope Gate, London W1K 1LN.
> Confidentiality Notice: This message is private and 
> confidential and may contain confidential, proprietary and 
> legally privileged information. If you have received this 
> message in error, please notify us and remove it from your 
> system and note that you must not copy, distribute or take 
> any action in reliance on it. Any unauthorised use or 
> disclosure of the contents of this message is not permitted 
> and may be unlawful.
> Disclaimer: Email messages may be subject to delays, 
> interception, non-delivery and unauthorised alterations. 
> Therefore, information expressed in this message is not given 
> or endorsed by AstraZeneca UK Limited unless otherwise 
> notified by an authorised representative independent of this 
> message. No contractual relationship is created by this 
> message by any person unless specifically indicated by 
> agreement in writing other than email.
> Monitoring: AstraZeneca UK Limited may monitor email traffic 
> data and content for the purposes of the prevention and 
> detection of crime, ensuring the security of our computer 
> systems and checking Compliance with our Code of Conduct and Policies.
> 

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

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