cctbxbb

Download

[email protected]

July 2015

10 participants
12 discussions

List usage
by Nigel Moriarty 20 Jul '15

20 Jul '15

Folks To those of you on the cctbx list (and even those not), as moderator I have received over a dozen requests from the server. One cause of the problem is non-members posting to a members-only list. This is usually caused by people including the ccbx list in a long list of recipients. This leads to another problem. The list complains about too many recipients. I'm sure that some of the discussion regarding the current SourceForge situation has been garbled as a result. There is an easy solution. When sending to the list, include only the list in the recipients. Anybody who is interested should subscribe to the list. Non members such as David Waterman should be encouraged to join the list. Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Physical Biosciences Division Lawrence Berkeley National Laboratory Berkeley, CA 94720-8235 Phone : 510-486-5709 Email : NWMoriarty(a)LBL.gov Fax : 510-486-5909 Web : CCI.LBL.gov

1 0

Building cctbx bundles without phenix.* dispatcher scripts
by Graeme.Winter＠diamond.ac.uk 02 Jul '15

02 Jul '15

Hi Folks Following on from various conversations going on here about programs in the default dials bundle which necessarily includes cctbx & lots of useful utilities in there, the question was asked why it includes bits of Phenix. In real life it does not include bits of phenix - they are bits of e.g. mmtbx which have dispatcher scripts which ask to be called phenix.xyz for example, as they are *also* used in phenix. Is there a way we can set the dispatcher prefix at the time of running libtbx.configure? That way you could have phenix.xyz or cctbx.xyz in other situations… then in the dials bundles we could make it clear that there are no bits of Phenix in there. Many thanks in advance, Graeme -- 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

3 2