November 2016 - cctbxbb - phenix-online.org

Failing shelxl test
by Graeme.Winter＠diamond.ac.uk 09 Nov '16

09 Nov '16

Folks, I keep getting this error: libtbx.python "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py" P31 [FAIL] Time: 1.38 Return code: 1 OKs: 0 Standard error: Traceback (most recent call last): File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 253, in <module> run(args=sys.argv[1:]) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 250, in run debug_utils.parse_options_loop_space_groups(args, run_call_back) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/debug_utils.py", line 120, in parse_options_loop_space_groups show_cpu_times, **kwds) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/debug_utils.py", line 83, in loop_space_groups call_back_result = call_back(flags, space_group_info, **kwds) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 244, in run_call_back verbose=flags.Verbose) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 234, in exercise run_shelx(shelx_titl, structure_factors, verbose=verbose) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 210, in run_shelx check_anisou(shelx_titl, xray_structure, shelx_pdb, verbose) File "/Users/graeme/svn/cctbx/modules/cctbx_project/cctbx/development/run_shelx.py", line 163, in check_anisou assert TotalMismatches == 0 AssertionError Please verify these tests manually. it is annoying as I understand it is to do with a change in shelxl - would it be OK to comment the test out to allow builds to pass? I am not sure it is useful at the moment Thank you 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

1 0

Re: [cctbxbb] Git status update
by markus.gerstel＠diamond.ac.uk 04 Nov '16

04 Nov '16

Hello everyone, since I have received no complaints and heard nothing to the contrary, so I thought I would let you know on the current state of the git migration: Until *Thursday, 1 September 2016*, 07:59 BST/08:59 CEST/11:59 pm PDT Cctbx development happens on Sourceforge. Note that cctbx development is "frozen" in preparation for the phenix release. If you are actively developing cctbx you should *now* sign up for a GitHub account. If you are not among the 27 people that have already joined the cctbx project at https://github.com/cctbx then please send me a mail with your github account name so I can invite you. In preparation for the move to github you should also install git on your machines. Set up your local installation of git on each machine you are using by running > git config --global pull.rebase true > git config --global user.name "John Doe" > git config --global user.email "your_email(a)example.com" Use an email address you have set up in your GitHub account at https://github.com/settings/emails. Note that this address will be forever publically readable! If you do not want your mail address to be public, you need to verify any (private) mail address with GitHub and then check the /Keep my email address private/ box at the link above. You can then use the dummy address <yourgithubname>@users.noreply.github.com instead. Other useful settings may be > git config --global alias.up "pull --rebase" To enable a *git up* command working much like svn up does. > git config --global alias.unstage "reset HEAD" *git unstage* to easily undo *git add*/*git rm*. > git config --global alias.mkremotebranch "push origin -u" *git mkremotebranch* will copy your current local branch to GitHub. > git config --global alias.rmremotebranch "push origin --delete" *git rmremotebranch <name>* will delete said branch from GitHub. > git config --global color.ui auto This adds color to the git output, which some may find useful for eg. *git status*. On the 1st of September the transitional period starts, and we will begin changing scripts to point to the new code locations. The transition may be delayed somewhat if the phenix release encounters any delays. I will send you further updates closer to the day. You can find and comment on the transition plan at https://docs.google.com/document/d/1bTiGbnvw8lNUrBLbRmhEdnd22McDqBbiKxcpyga… Best wishes -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

6 16

use_internal_variance in iotbx.merging_statistics
by Keitaro Yamashita 02 Nov '16

02 Nov '16

Dear Phenix/CCTBX developers, iotbx/merging_statistics.py is used by phenix.merging_statistics, phenix.table_one, and so on. By upgrading phenix from 1.10.1 to 1.11, merging statistics-related codes were significantly changed. Previously, miller.array.merge_equivalents() was always called with argument use_internal_variance=False, which is consistent with XDS, Aimless and so on. Currently, use_internal_variance=True is default, and cannot be changed by users (see below). These changes were made by @afonine and @rjgildea in rev. 22973 (Sep 26, 2015) and 23961 (Mar 8, 2016). Could anyone explain why these changes were introduced? https://sourceforge.net/p/cctbx/code/22973 https://sourceforge.net/p/cctbx/code/23961 My points are: - We actually cannot control use_internal_variance= parameter because it is not passed to merge_equivalents() in class filter_intensities_by_sigma. - In previous versions, if I gave XDS output to phenix.merging_statistics, <I/sigma> values calculated in the same way (as XDS does) were shown; but not in the current version. - For (for example) phenix.table_one users who expect this behavior, it can give inconsistency. The statistics would not be consistent with the data used in refinement. cf. the related discussion in cctbxbb: http://phenix-online.org/pipermail/cctbxbb/2012-October/000611.html Best regards, Keitaro

4 6