- cctbxbb - phenix-online.org

Inserting F000 into reflection (mtg) file
by Nicholas Pearce 22 Aug '16

22 Aug '16

Hi Everyone, I’ve been looking through the cctbx/phenix scripts and although there’s a script for estimating F000 (phenix.f000), I can’t find any way of inserting it into an mtz file to make it accessible for easy map generation. Is this implemented anywhere/what do people use as the best way of doing this? If the insertion of F000 into an mtz file has been purposefully avoided, I presume it's done because we don't want the possibility of someone refining a model where F000 is used in refinement. Unless there’s another reason? Thanks, Nick

2 1

Git
by Graeme.Winter＠diamond.ac.uk 01 Aug '16

01 Aug '16

Folks, Can we revisit the idea of moving to git for cctbx? Thanks 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

7 18

Structure Factor for 000
by Gareth.Nisbet＠diamond.ac.uk 28 Jul '16

28 Jul '16

Is it possible to get the structure_factors function to give the structure factor for the 000 reflection? I appreciate this might be a slightly odd question. Gareth -- 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 3

Berkeley Server Downtime (24 hours, 7/22 - 7/23)
by Billy Poon 20 Jul '16

20 Jul '16

Dear all, On Friday, July 22, our servers will be shut down starting at 5:00 pm Pacific for scheduled maintenance in our building. We expect that the servers will be available the next day (7/23) by 5:00 pm Pacific at the latest. This will affect, - The Phenix web site (http://phenix-online.org/) - The DIALS West web site (http://dials.lbl.gov/) - The CCI web site (http://cci.lbl.gov/) - The Structural Biology Technology Portal (http://technology.sbkb.org/) Bug reports and emails requesting help should be queued and we will receive them once the servers are back online. We apologize for any inconvenience. -- Billy K. Poon Research Scientist, Molecular Biophysics and Integrated Bioimaging Lawrence Berkeley National Laboratory 1 Cyclotron Road, M/S 33R0345 Berkeley, CA 94720 Tel: (510) 486-5709 Fax: (510) 486-5909 Web: https://phenix-online.org

1 0

Re: [cctbxbb] Git
by R. D. Oeffner 02 Jul '16

02 Jul '16

How often is this git repo of cctbx copied from the svn repo of cctbx? Rob -----Original Message----- From: cctbxbb-request(a)phenix-online.org Sent: Friday, July 1, 2016 8:00 PM To: cctbxbb(a)phenix-online.org Subject: cctbxbb Digest, Vol 88, Issue 1 Send cctbxbb mailing list submissions to cctbxbb(a)phenix-online.org To subscribe or unsubscribe via the World Wide Web, visit http://phenix-online.org/mailman/listinfo/cctbxbb or, via email, send a message with subject or body 'help' to cctbxbb-request(a)phenix-online.org You can reach the person managing the list at cctbxbb-owner(a)phenix-online.org When replying, please edit your Subject line so it is more specific than "Re: Contents of cctbxbb digest..." Today's Topics: 1. Re: Git (markus.gerstel(a)diamond.ac.uk) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Jul 2016 12:34:56 +0000 From: <markus.gerstel(a)diamond.ac.uk> To: <cctbxbb(a)phenix-online.org> Subject: Re: [cctbxbb] Git Message-ID: <415F7F573406BB498256C68158D45674666211BB@exchmbx01> Content-Type: text/plain; charset="utf-8" Hello everyone, Following up the earlier discussion, do have we reached a consensus? Also, I think timeframe has not been discussed, but I assume this will boil down to ?after phenix release? anyway. In the meantime I have contacted (nearly) all cctbx developers and obtained their github user-IDs - alongside some enthusiastic* feedback. I will mass-invite you all soonishly to a cctbx organisation with a preliminary git copy of the svn history to play with. Best wishes -Markus Markus Gerstel MBCS Postdoctoral Research Associate Tel: +44 1235 778698 Diamond Light Source Ltd. Diamond House Harwell Science & Innovation Campus Didcot Oxfordshire OX11 0DE * The best comment I received was ?What?s CCTBX?? ? and that was talking to the correct person :) (name withheld) -- 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

1 0

Installation failure after package updates
by markus.gerstel＠diamond.ac.uk 27 Jun '16

27 Jun '16

Following the latest package updates we are now observing installer failures. In particular the configure step appears to fail with a missing libffi.so.6 Any ideas how to rectify this, or if this error can be ignored safely? -Markus Running with --verbose: ========================================================================== DIALS Installation version: dev20160610 machine type: intel-linux-2.6-x86_64 OS version: 2.6.32-573.18.1.el6.x86_64 destination: /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610 # of processors: 24 ========================================================================= Configuring DIALS components... /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build ['/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/bin/python', '/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/configure.py', '--current_working_directory', '/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build', 'dials', 'xia2', 'iota', 'prime'] : Python: 2.7.8 "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/bin/python" : Compiler: default : Build mode: release : Warning level: 0 : Precompiled Headers: False : Static libraries: False : Static exe: False : Scan Boost headers: False : Write full flex_fwd.h files: False : Build Boost.Python extensions: True : Define BOOST_PYTHON_NO_PY_SIGNATURES: False : Define BOOST_PYTHON_BOOL_INT_STRICT: True : Enable OpenMP if possible: False : Boost threads enabled: False : Enable CUDA: False : Use opt_resources if available: False : Use environment flags: False : Enable C++11: False : Force true division: True : command_version_suffix: None : Relocatable paths anchored at: /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build : Top-down list of all modules involved: : prime "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/prime" : iota "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/iota" : xia2 "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/xia2" : mmtbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/mmtbx" : dials "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/dials" : xfel "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/xfel" : cma_es "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cma_es" : gltbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/gltbx" : crys3d "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/crys3d" : rstbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/rstbx" : spotfinder "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/spotfinder" : annlib+adaptbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/annlib" : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/annlib_adaptbx" : dxtbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/dxtbx" : iotbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/iotbx" : cbflib+adaptbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cbflib" : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cbflib_adaptbx" : ccp4io+adaptbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/ccp4io" : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/ccp4io_adaptbx" : smtbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/smtbx" : ucif "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/ucif" : cctbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cctbx" : chiltbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/chiltbx" : scitbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/scitbx" : fable "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/fable" : omptbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/omptbx" : boost+adaptbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/boost" : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/boost_adaptbx" : tbxx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/tbxx" : libtbx "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx" : Creating files in build directory: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build" : dispatcher_include_template.sh : dispatcher_head.sh : setpaths.sh : setpaths.csh : setpaths_all.sh : setpaths_all.csh : setpaths_debug.sh : unsetpaths.sh : setpaths_debug.csh : unsetpaths.csh : SConstruct : Makefile : run_tests.csh : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/boost_adaptbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/fable/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/scitbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cctbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/smtbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cbflib_adaptbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/iotbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/dxtbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/spotfinder/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/rstbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/crys3d/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/gltbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/xfel/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/xfel/ui/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/dials/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/mmtbx/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/xia2/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/iota/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/prime/command_line" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/boost_adaptbx/libtbx_refresh.py" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/scitbx/libtbx_refresh.py" : Generating C++ header files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/include/scitbx/array_family" : Generating C++ files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/include/scitbx/array_family/boost_python" : Using fable to convert scitbx/lbfgs.f : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cctbx/libtbx_refresh.py" : Generating C++ files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/cctbx/eltbx" : Generating C++ files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/include/cctbx/boost_python" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/smtbx/libtbx_refresh.py" : Generating C++ files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/include/smtbx/boost_python" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/cbflib_adaptbx/libtbx_refresh.py" : Copying to lib: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cbflib/pycbf/pycbf.py" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/iotbx/libtbx_refresh.py" : Using fable to convert iotbx/pdb/hybrid_36_f.f : Writing: iotbx/pdb/hybrid_36_fem.cpp : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/annlib_adaptbx/libtbx_refresh.py" : Generating C++ files for self-inclusive approximate nearest neighbor : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/crys3d/libtbx_refresh.py" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/gltbx/libtbx_refresh.py" : Generating C++ files in: : "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/gltbx" : Info: Re-using existing font cpp files. : Hint: Remove gltbx/FONTS_UCS_DONE_FLAG_FILE : to force generation of new font files. : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/xfel/libtbx_refresh.py" : Creating cxi_user directory : Creating cxi_user/__init__.py : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/dials/libtbx_refresh.py" : DIALS 1.dev.360-ge6510c8 : Identifying autocompletable commands: dials.analyse_background dials.combine_found_spots dials.find_spots dials.index dials.integrate dials.reciprocal_lattice_viewer dials.refine dials.reindex dials.rl_png : Installing autocompletion script into: setpaths_all.sh setpaths_debug.sh setpaths.sh : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/mmtbx/libtbx_refresh.py" : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/xia2/libtbx_refresh.py" : XIA2 0.4.0.381-g9b3a992 : Processing: "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build/exe_dev" : Regenerating module files in /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base : /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/etc/pango not present, could not regenerate pango files : generating gtk.immodules file : /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/bin/gtk-query-immodules-2.0: error while loading shared libraries: libffi.so.6: cannot open shared object file: No such file or directory : Traceback (most recent call last): : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/configure.py", line 22, in <module> : if not run(): : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/configure.py", line 17, in run : libtbx.env_config.cold_start(sys.argv) : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/env_config.py", line 2264, in cold_start : env.refresh() : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/env_config.py", line 1537, in refresh : regenerate_module_files.run(libtbx.env.under_base('.'), only_if_needed=True) : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/auto_build/regenerate_module_files.py", line 154, in run : fix_gtk(base_dir, out) : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/auto_build/regenerate_module_files.py", line 72, in fix_gtk : log=out) : File "/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/auto_build/installer_utils.py", line 81, in call : raise RuntimeError("Call to '%s' failed with exit code %d" % (args, rc)) : RuntimeError: Call to '/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/bin/gtk-query-immodules-2.0 /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/lib/gtk-2.0/2.10.0/immodules/*.so> /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/etc/gtk-2.0/gtk.immodules' failed with exit code 127 Traceback (most recent call last): File "./bin/install.py", line 97, in <module> installer(sys.argv[1:]).install() File "/scratch/jenkins_slave/workspace/dials_install_dls_module/dials-installer-dev/lib/libtbx/auto_build/install_distribution.py", line 197, in install self.install_from_binary() File "/scratch/jenkins_slave/workspace/dials_install_dls_module/dials-installer-dev/lib/libtbx/auto_build/install_distribution.py", line 318, in install_from_binary self.reconfigure(log=log) File "/scratch/jenkins_slave/workspace/dials_install_dls_module/dials-installer-dev/lib/libtbx/auto_build/install_distribution.py", line 484, in reconfigure call(args=args, log=log, verbose=self.options.verbose) File "/scratch/jenkins_slave/workspace/dials_install_dls_module/dials-installer-dev/lib/libtbx/auto_build/installer_utils.py", line 81, in call raise RuntimeError("Call to '%s' failed with exit code %d" % (args, rc)) RuntimeError: Call to '/dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/base/bin/python /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/modules/cctbx_project/libtbx/configure.py --current_working_directory /dls/science/groups/scisoft/DIALS/CD/latest/dials-dev20160610/build dials xia2 iota prime' failed with exit code 1 Markus Gerstel MBCS Postdoctoral Research Associate Tel: +44 1235 778698 Diamond Light Source Ltd. Diamond House Harwell Science & Innovation Campus Didcot Oxfordshire OX11 0DE -- 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

2 6

Re: [cctbxbb] error
by markus.gerstel＠diamond.ac.uk 23 Jun '16

23 Jun '16

Hi James, CCing cctbxbb for further support I can reproduce at least similar errors with both DIALS 1.2.5 and current nightly builds. I think this may be a matplotlib 1.3.1 problem. A minimal reproducer is: $ dials.python > import matplotlib.pyplot as plt > plt.imshow([[1]]) Gtk-Message... > (press ctrl+D) Segmentation fault When compiled on the same machine I do not get the Gtk-Messages, but I do get the segmentation fault. Markus Gerstel MBCS Postdoctoral Research Associate Tel: +44 1235 778698 Diamond Light Source Ltd. Diamond House Harwell Science & Innovation Campus Didcot Oxfordshire OX11 0DE From: Parkhurst, James (DLSLtd,RAL,LSCI) Sent: 21 June 2016 16:58 To: Gerstel, Markus (DLSLtd,RAL,LSCI) Subject: FW: error Hi Markus, I've been getting my summer student to do the cctbx_introduction tutorials in dials_scratch. He's using a version of dials downloaded from the website and when he runs the introduction script he gets errors about gdk-pixbuf giving paths to /scratch/jenkins_slave/workspace/. This seems like there is a jenkins path being set in the distributed installers. Would you have any idea how I can fix this? I'm downloading the linux installer of DIALS now so I can test this myself. Thanks, James ________________________________ [sse87232@ws188 cctbx_introduction_1]$ dials.python cctbx_introduction_1_test.py ximg2701_00001.cbf (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory (cctbx_introduction_1_test.py:6243): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/scratch/jenkins_slave/workspace/dials_release_build/compilationtarget/native/label/dials-ws133/build_dials/base/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory Segmentation fault (core dumped) [sse87232@ws188 cctbx_introduction_1]$ which dials.python /dls/science/users/sse87232/dials/dials-v1-2-4/build/bin/dials.python -- 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

4 6

past contributors
by markus.gerstel＠diamond.ac.uk 16 Jun '16

16 Jun '16

I have now contacted everyone who ever contributed to cctbx in the past to get name/email details in preparation for an svn->git conversion. Everyone except these three: Erik McKee (emckee) Vishal Verma (vermav) ydr (y0udar) Anyone know how to get into contact with them? -Markus -- 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

2 1

Not wishing to raise this again but...
by Graeme.Winter＠diamond.ac.uk 16 Jun '16

16 Jun '16

... is there any enthusiasm out there for moving cctbx to git? The more I work with git the more I wish this existed properly for cctbx. I've raised this a bunch of times and always it is "not right now" however "a good idea" - this'll be the last time I ask... Could we move to git, please? I note the bootstrap script for Windows now has a git dependency even! Am happy to help if I can with anything though I think it should be pretty simple... was for DIALS & xia2 :) Thanks 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

8 23

Not wishing to raise this again but...
by R.D. Oeffner 15 Jun '16

15 Jun '16

Personally I think moving the cctbx to git is a great idea as it would make it easier and safer when developing and testing new features. Given so many teams are using the cctbx this seems like a compelling reason for it to be moved. We had a chat a while ago with Berkeley about this but I've forgotten what the consensus was. Rob > > Message: 1 > Date: Tue, 14 Jun 2016 12:10:03 +0000 > From: <Graeme.Winter(a)diamond.ac.uk> > To: <cctbxbb(a)phenix-online.org> > Subject: Re: [cctbxbb] Not wishing to raise this again but... > Message-ID: <13999B6FC038EB44B067771E3CFBD091BC327D8E@exchmbx03> > Content-Type: text/plain; charset="us-ascii" > > Hi All, > > This sounds like it is heading in a pragmatic direction - I would find > it very helpful to gauge feeling for or against this. To make this > simple I have attempted (starting from a completely ignorant position) > to put together one of those online survey things: > > https://www.surveymonkey.co.uk/r/GXPY5JW > > If you could pick an option that would be great, explaining why would > be even better, or hitting reply-all to this thread would also work > (as has previously done so) I'll collate answers over the next few > days & feed back when we have (say) 10-20 or a few days have passed > >> From experience with moving xia2 & DIALS it was surprisingly >> straightforward (an opinion) > > Thanks & cheerio Graeme > > -----Original Message----- > From: cctbxbb-bounces(a)phenix-online.org > [mailto:[email protected]] On Behalf Of > markus.gerstel(a)diamond.ac.uk > Sent: 14 June 2016 12:18 > To: cctbxbb(a)phenix-online.org > Subject: Re: [cctbxbb] Not wishing to raise this again but... > > Hi Pavel, > > I volunteered to do this some time ago, just like for DIALS, and would > still be happy to do this. > We can do the move slowly, so allow users (developers) with a git > repository while development still happens in SVN for say a couple of > weeks, and I would be happy to run the git support for that time and > for the aftermath of the move. > > Best wishes > -Markus > > -----Original Message----- > From: cctbxbb-bounces(a)phenix-online.org > [mailto:[email protected]] On Behalf Of Pavel Afonine > Sent: 14 June 2016 12:11 > To: cctbx mailing list > Subject: Re: [cctbxbb] Not wishing to raise this again but... > > Hey there! > > Well I guess I say something even though I don't have much to say > really. I've been contributing to CCTBX for the past 13 years, so I > feel like this conversation is not too irrelevant to me to say the > least. > > I don't have strong opinion about staying with svn vs moving to git. I > routinely contribute to CCTBX (which is SVN-based) and I routinely > contribute to my other activity - Q|R (Quantum Refinement, which is > hosted by GitHub). I'm comfortable with both environments as I'm using > only the minimal functionality of both: check in, check out, diff.. > period. I'm not interested in branching/etc sophistication; this is > just because the way I structure my workflow.. > > My current understanding is that moving CCTBX to use git boils down to: > - actually someone doing it; AND > - taking good proper responsible care of the aftermath (if any). > > So far no-one volunteered to embrace this challenge, as far as I know. > > In summary I think we should move to git, at least to follow the > vector of progress. > > All the best, > Pavel >

3 2