- cctbxbb - phenix-online.org

Clipper updates for C++11
by Billy Poon 12 Aug '19

12 Aug '19

Hi everyone, As part of making CCTBX-based software compile with C++11, it looks like we need to update our checkout of clipper to the latest version. http://www.ysbl.york.ac.uk/~cowtan/clipper/clipper.html As a side note, is this a feature that is widely used? If not, we can disable the downloading of the clipper source files. Also, in addition to this post on the bulletin board, I have started an issue on Github (https://github.com/cctbx/cctbx_project/issues/379). Feel free to comment on any of these forums. -- 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] Molprobity / CCTBX incompatibility
by Nigel Moriarty 12 Aug '19

12 Aug '19

But maybe the installation of cctbx has molprobity.reduce and not phenix.reduce so if that is the case we can change the script to look for molprobity.reduce instead of phenix.reduce. Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging 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 On Mon, Aug 12, 2019 at 2:58 PM Robert Nolte <robert.t.nolte(a)gsk.com> wrote: > According to the log file when I just tried to run it, it is phenix.reduce > that it can’t find. > > Bob > > > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 5:55 PM > *To:* Robert Nolte <robert.t.nolte(a)gsk.com> > *Cc:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com>; > Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > I'm just trying to find out if, at the command line, whether it is > phenix.reduce or molprobity.reduce. Charitha just needs to type one or the > other to see what happens. > > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 2:44 PM Robert Nolte <robert.t.nolte(a)gsk.com> > wrote: > > Nigel, > > Currently it is not running. This was working from the scratch > install last week. I am not sure what is going on now. > > Bob > > > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 4:52 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Does molprobity.reduce run? > > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 1:14 PM Charitha Belluru Shetty < > charitha-belluru.b.shetty(a)gsk.com> wrote: > > Hi Nigel, > > > > I hit the send button too soon..Ignore my previous email 😊 > > > > -bash-4.2$ source setpaths.sh > > -bash-4.2$ > > -bash-4.2$ env |grep -i reduce > > -bash-4.2$ > > > > So the “setpath.sh” has the below contents… > > > > $ cat /hpc/apps/current/molprobity/v4.4.app/MolProbity/build/setpaths.sh > > # THIS IS AN AUTOMATICALLY GENERATED FILE. > > # DO NOT EDIT! CHANGES WILL BE LOST. > > ocwd="`pwd`" > > if [ -n "$LIBTBX_BUILD_RELOCATION_HINT" ]; then > > cd "$LIBTBX_BUILD_RELOCATION_HINT" > > LIBTBX_BUILD_RELOCATION_HINT= > > export LIBTBX_BUILD_RELOCATION_HINT > > elif [ -n "$BASH_SOURCE" ]; then > > LIBTBX_BUILD=`dirname "$BASH_SOURCE[0]"` > > cd "$LIBTBX_BUILD" > > else > > cd "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build" > > fi > > LIBTBX_BUILD=`pwd -P` > > export LIBTBX_BUILD > > LIBTBX_OPATH="$PATH" > > export LIBTBX_OPATH > > PATH="$LIBTBX_BUILD/bin:$PATH" > > export PATH > > cd "$ocwd" > > ocwd= > > alias libtbx.setpaths_all=". \"$LIBTBX_BUILD/setpaths_all.sh\"" > > alias libtbx.unsetpaths=". \"$LIBTBX_BUILD/unsetpaths.sh\"" > > if [ -n "$LIBTBX_OPATH" ]; then > > LIBTBX_TMPVAL="$LIBTBX_OPATH" > > else > > LIBTBX_TMPVAL= > > fi > > export LIBTBX_TMPVAL > > PATH=`libtbx.path_utility prepend LIBTBX_TMPVAL "$LIBTBX_BUILD/bin" < > /dev/null` > > export PATH > > if [ "$PATH" = "L_I_B_T_B_X_E_M_P_T_Y" ]; then unset PATH; fi > > LIBTBX_TMPVAL= > > LIBTBX_OPATH= > > LIBTBX_BUILD= > > > > > > Best Regards, > > Charitha Shetty > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 4:08 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Once you source the setpaths.sh file in the build directory do you have > phenix.reduce or molprobity.reduce? > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 12:43 PM Charitha Belluru Shetty < > charitha-belluru.b.shetty(a)gsk.com> wrote: > > Hi Christopher/ Nigel, > > > > Thank you for your quick reply. > > > > The build process was completed without any error. Pasting few of the > lines from it… > > > > > > ===== Running in build: rebuild rotarama > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rota8000-cys.data -> rota8000-cys.pickle: converting ... done. > > rota8000-asp.data -> rota8000-asp.pickle: converting ... done. > > rota8000-ser.data -> rota8000-ser.pickle: converting ... done. > > rota8000-gln.data -> rota8000-gln.pickle: converting ... done. > > rota8000-ile.data -> rota8000-ile.pickle: converting ... done. > > rota8000-pro.data -> rota8000-pro.pickle: converting ... done. > > rota8000-lys.data -> rota8000-lys.pickle: converting ... done. > > rota8000-thr.data -> rota8000-thr.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: converting ... done. > > rota8000-glu.data -> rota8000-glu.pickle: converting ... done. > > rota8000-met.data -> rota8000-met.pickle: converting ... done. > > rota8000-his.data -> rota8000-his.pickle: converting ... done. > > rota8000-leu.data -> rota8000-leu.pickle: converting ... done. > > rota8000-arg.data -> rota8000-arg.pickle: converting ... done. > > rota8000-trp.data -> rota8000-trp.pickle: converting ... done. > > rota8000-asn.data -> rota8000-asn.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: already up to date. > > rota8000-val.data -> rota8000-val.pickle: converting ... done. > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rama8000-ileval-nopreP.data -> rama8000-ileval-nopreP.pickle: converting > ... done. > > rama8000-gly-sym.data -> rama8000-gly-sym.pickle: converting ... done. > > rama8000-cispro.data -> rama8000-cispro.pickle: converting ... done. > > rama8000-general-noGPIVpreP.data -> rama8000-general-noGPIVpreP.pickle: > converting ... done. > > rama8000-transpro.data -> rama8000-transpro.pickle: converting ... done. > > rama8000-prepro-noGP.data -> rama8000-prepro-noGP.pickle: converting ... > done. > > u+s,u,s: 10.06 9.83 0.23 > > ===== Running in .: libtbx.refresh > > Python: 2.7.16 > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/bin/python2.7" > > 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: True > > Enable CUDA: False > > Use conda: False > > Use opt_resources if available: False > > Use environment flags: False > > Enable C++11: False > > Python3 migration warning policy: None > > command_version_suffix: None > > Relocatable paths anchored at: > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/build > > Top-down list of all modules involved: > > mmtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx" > > iotbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx" > > ccp4io+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io_adaptbx" > > smtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx" > > ucif > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/ucif" > > cctbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx" > > scitbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx" > > fable > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable" > > omptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/omptbx" > > boost+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/boost" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx" > > tbxx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/tbxx" > > chiltbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/chiltbx" > > libtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx" > > Creating files in build directory: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/libtbx_refresh.py" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/libtbx_refresh.py" > > Generating C++ header files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family/boost_python" > > Using fable to convert scitbx/lbfgs.f > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/libtbx_refresh.py" > > Generating C++ files in: > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/cctbx/eltbx" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/cctbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/libtbx_refresh.py" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/smtbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/libtbx_refresh.py" > > Processing: "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/exe_dev" > > Regenerating module files in > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/pango not present, > could not regenerate pango files > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/gtk-2.0 not > present, could not regenerate gdk-pixbuf.loaders > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/fonts not present, > could not rebuild fonts > > generating index.theme file > > Done. > > > > *Bootstrap success: build* > > *++++++++++ MolProbity configure.sh finished.* > > > > > > > > [tm375568@uptus060-3 MolProbity]$ ./setup.sh > > ++++++++++ creating directories ... > > ++++++++++ setting permisions ... > > *Couldn't get a file descriptor referring to the console **à I assume > this can be ignored. * > > [tm375568@uptus060-3 MolProbity]$ > > > > Best Regards, > > Charitha Shetty > > > > *From:* Christopher Williams <christopher.sci.williams(a)gmail.com> > *Sent:* Monday, August 12, 2019 3:34 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Nigel Moriarty (nwmoriarty(a)lbl.gov) <nwmoriarty(a)lbl.gov>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Hmm. It looks like Reduce and/or Probe has failed to install correctly. > Most likely an early call to Reduce has resulted in an empty file, which is > then passed into other programs, resulting in error messages. > > > > The configure script ran a build process. Do you know if that process > finished successfully or if it ended with errors? If the build exited > early, it may have never reached the part where Reduce gets compiled. Some > dependencies have changed, and I have been having trouble with my own > builds lately. > > > > It is also possible that there was just a network hiccup that prevented > something from downloading correctly, and a second attempt will work. > > > > I am working on a new configure/install script for more consistent > handling of dependencies. Hopefully it will be ready in about a day. > > > > Good luck, > > -Christopher Williams > > ---Richardson Lab, Duke University > > > > > > > > > > > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* >

1 0

Re: [cctbxbb] Molprobity / CCTBX incompatibility
by Nigel Moriarty 12 Aug '19

12 Aug '19

I'm just trying to find out if, at the command line, whether it is phenix.reduce or molprobity.reduce. Charitha just needs to type one or the other to see what happens. Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging 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 On Mon, Aug 12, 2019 at 2:44 PM Robert Nolte <robert.t.nolte(a)gsk.com> wrote: > Nigel, > > Currently it is not running. This was working from the scratch > install last week. I am not sure what is going on now. > > Bob > > > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 4:52 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Does molprobity.reduce run? > > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 1:14 PM Charitha Belluru Shetty < > charitha-belluru.b.shetty(a)gsk.com> wrote: > > Hi Nigel, > > > > I hit the send button too soon..Ignore my previous email 😊 > > > > -bash-4.2$ source setpaths.sh > > -bash-4.2$ > > -bash-4.2$ env |grep -i reduce > > -bash-4.2$ > > > > So the “setpath.sh” has the below contents… > > > > $ cat /hpc/apps/current/molprobity/v4.4.app/MolProbity/build/setpaths.sh > > # THIS IS AN AUTOMATICALLY GENERATED FILE. > > # DO NOT EDIT! CHANGES WILL BE LOST. > > ocwd="`pwd`" > > if [ -n "$LIBTBX_BUILD_RELOCATION_HINT" ]; then > > cd "$LIBTBX_BUILD_RELOCATION_HINT" > > LIBTBX_BUILD_RELOCATION_HINT= > > export LIBTBX_BUILD_RELOCATION_HINT > > elif [ -n "$BASH_SOURCE" ]; then > > LIBTBX_BUILD=`dirname "$BASH_SOURCE[0]"` > > cd "$LIBTBX_BUILD" > > else > > cd "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build" > > fi > > LIBTBX_BUILD=`pwd -P` > > export LIBTBX_BUILD > > LIBTBX_OPATH="$PATH" > > export LIBTBX_OPATH > > PATH="$LIBTBX_BUILD/bin:$PATH" > > export PATH > > cd "$ocwd" > > ocwd= > > alias libtbx.setpaths_all=". \"$LIBTBX_BUILD/setpaths_all.sh\"" > > alias libtbx.unsetpaths=". \"$LIBTBX_BUILD/unsetpaths.sh\"" > > if [ -n "$LIBTBX_OPATH" ]; then > > LIBTBX_TMPVAL="$LIBTBX_OPATH" > > else > > LIBTBX_TMPVAL= > > fi > > export LIBTBX_TMPVAL > > PATH=`libtbx.path_utility prepend LIBTBX_TMPVAL "$LIBTBX_BUILD/bin" < > /dev/null` > > export PATH > > if [ "$PATH" = "L_I_B_T_B_X_E_M_P_T_Y" ]; then unset PATH; fi > > LIBTBX_TMPVAL= > > LIBTBX_OPATH= > > LIBTBX_BUILD= > > > > > > Best Regards, > > Charitha Shetty > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 4:08 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Once you source the setpaths.sh file in the build directory do you have > phenix.reduce or molprobity.reduce? > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 12:43 PM Charitha Belluru Shetty < > charitha-belluru.b.shetty(a)gsk.com> wrote: > > Hi Christopher/ Nigel, > > > > Thank you for your quick reply. > > > > The build process was completed without any error. Pasting few of the > lines from it… > > > > > > ===== Running in build: rebuild rotarama > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rota8000-cys.data -> rota8000-cys.pickle: converting ... done. > > rota8000-asp.data -> rota8000-asp.pickle: converting ... done. > > rota8000-ser.data -> rota8000-ser.pickle: converting ... done. > > rota8000-gln.data -> rota8000-gln.pickle: converting ... done. > > rota8000-ile.data -> rota8000-ile.pickle: converting ... done. > > rota8000-pro.data -> rota8000-pro.pickle: converting ... done. > > rota8000-lys.data -> rota8000-lys.pickle: converting ... done. > > rota8000-thr.data -> rota8000-thr.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: converting ... done. > > rota8000-glu.data -> rota8000-glu.pickle: converting ... done. > > rota8000-met.data -> rota8000-met.pickle: converting ... done. > > rota8000-his.data -> rota8000-his.pickle: converting ... done. > > rota8000-leu.data -> rota8000-leu.pickle: converting ... done. > > rota8000-arg.data -> rota8000-arg.pickle: converting ... done. > > rota8000-trp.data -> rota8000-trp.pickle: converting ... done. > > rota8000-asn.data -> rota8000-asn.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: already up to date. > > rota8000-val.data -> rota8000-val.pickle: converting ... done. > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rama8000-ileval-nopreP.data -> rama8000-ileval-nopreP.pickle: converting > ... done. > > rama8000-gly-sym.data -> rama8000-gly-sym.pickle: converting ... done. > > rama8000-cispro.data -> rama8000-cispro.pickle: converting ... done. > > rama8000-general-noGPIVpreP.data -> rama8000-general-noGPIVpreP.pickle: > converting ... done. > > rama8000-transpro.data -> rama8000-transpro.pickle: converting ... done. > > rama8000-prepro-noGP.data -> rama8000-prepro-noGP.pickle: converting ... > done. > > u+s,u,s: 10.06 9.83 0.23 > > ===== Running in .: libtbx.refresh > > Python: 2.7.16 > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/bin/python2.7" > > 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: True > > Enable CUDA: False > > Use conda: False > > Use opt_resources if available: False > > Use environment flags: False > > Enable C++11: False > > Python3 migration warning policy: None > > command_version_suffix: None > > Relocatable paths anchored at: > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/build > > Top-down list of all modules involved: > > mmtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx" > > iotbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx" > > ccp4io+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io_adaptbx" > > smtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx" > > ucif > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/ucif" > > cctbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx" > > scitbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx" > > fable > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable" > > omptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/omptbx" > > boost+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/boost" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx" > > tbxx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/tbxx" > > chiltbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/chiltbx" > > libtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx" > > Creating files in build directory: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/libtbx_refresh.py" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/libtbx_refresh.py" > > Generating C++ header files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family/boost_python" > > Using fable to convert scitbx/lbfgs.f > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/libtbx_refresh.py" > > Generating C++ files in: > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/cctbx/eltbx" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/cctbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/libtbx_refresh.py" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/smtbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/libtbx_refresh.py" > > Processing: "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/exe_dev" > > Regenerating module files in > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/pango not present, > could not regenerate pango files > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/gtk-2.0 not > present, could not regenerate gdk-pixbuf.loaders > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/fonts not present, > could not rebuild fonts > > generating index.theme file > > Done. > > > > *Bootstrap success: build* > > *++++++++++ MolProbity configure.sh finished.* > > > > > > > > [tm375568@uptus060-3 MolProbity]$ ./setup.sh > > ++++++++++ creating directories ... > > ++++++++++ setting permisions ... > > *Couldn't get a file descriptor referring to the console **à I assume > this can be ignored. * > > [tm375568@uptus060-3 MolProbity]$ > > > > Best Regards, > > Charitha Shetty > > > > *From:* Christopher Williams <christopher.sci.williams(a)gmail.com> > *Sent:* Monday, August 12, 2019 3:34 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Nigel Moriarty (nwmoriarty(a)lbl.gov) <nwmoriarty(a)lbl.gov>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Hmm. It looks like Reduce and/or Probe has failed to install correctly. > Most likely an early call to Reduce has resulted in an empty file, which is > then passed into other programs, resulting in error messages. > > > > The configure script ran a build process. Do you know if that process > finished successfully or if it ended with errors? If the build exited > early, it may have never reached the part where Reduce gets compiled. Some > dependencies have changed, and I have been having trouble with my own > builds lately. > > > > It is also possible that there was just a network hiccup that prevented > something from downloading correctly, and a second attempt will work. > > > > I am working on a new configure/install script for more consistent > handling of dependencies. Hopefully it will be ready in about a day. > > > > Good luck, > > -Christopher Williams > > ---Richardson Lab, Duke University > > > > > > > > > > > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* >

1 0

Re: [cctbxbb] Molprobity / CCTBX incompatibility
by Nigel Moriarty 12 Aug '19

12 Aug '19

Does molprobity.reduce run? Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging 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 On Mon, Aug 12, 2019 at 1:14 PM Charitha Belluru Shetty < charitha-belluru.b.shetty(a)gsk.com> wrote: > Hi Nigel, > > > > I hit the send button too soon..Ignore my previous email 😊 > > > > -bash-4.2$ source setpaths.sh > > -bash-4.2$ > > -bash-4.2$ env |grep -i reduce > > -bash-4.2$ > > > > So the “setpath.sh” has the below contents… > > > > $ cat /hpc/apps/current/molprobity/v4.4.app/MolProbity/build/setpaths.sh > > # THIS IS AN AUTOMATICALLY GENERATED FILE. > > # DO NOT EDIT! CHANGES WILL BE LOST. > > ocwd="`pwd`" > > if [ -n "$LIBTBX_BUILD_RELOCATION_HINT" ]; then > > cd "$LIBTBX_BUILD_RELOCATION_HINT" > > LIBTBX_BUILD_RELOCATION_HINT= > > export LIBTBX_BUILD_RELOCATION_HINT > > elif [ -n "$BASH_SOURCE" ]; then > > LIBTBX_BUILD=`dirname "$BASH_SOURCE[0]"` > > cd "$LIBTBX_BUILD" > > else > > cd "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build" > > fi > > LIBTBX_BUILD=`pwd -P` > > export LIBTBX_BUILD > > LIBTBX_OPATH="$PATH" > > export LIBTBX_OPATH > > PATH="$LIBTBX_BUILD/bin:$PATH" > > export PATH > > cd "$ocwd" > > ocwd= > > alias libtbx.setpaths_all=". \"$LIBTBX_BUILD/setpaths_all.sh\"" > > alias libtbx.unsetpaths=". \"$LIBTBX_BUILD/unsetpaths.sh\"" > > if [ -n "$LIBTBX_OPATH" ]; then > > LIBTBX_TMPVAL="$LIBTBX_OPATH" > > else > > LIBTBX_TMPVAL= > > fi > > export LIBTBX_TMPVAL > > PATH=`libtbx.path_utility prepend LIBTBX_TMPVAL "$LIBTBX_BUILD/bin" < > /dev/null` > > export PATH > > if [ "$PATH" = "L_I_B_T_B_X_E_M_P_T_Y" ]; then unset PATH; fi > > LIBTBX_TMPVAL= > > LIBTBX_OPATH= > > LIBTBX_BUILD= > > > > > > Best Regards, > > Charitha Shetty > > > > *From:* Nigel Moriarty <nwmoriarty(a)lbl.gov> > *Sent:* Monday, August 12, 2019 4:08 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Christopher Williams <christopher.sci.williams(a)gmail.com>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Once you source the setpaths.sh file in the build directory do you have > phenix.reduce or molprobity.reduce? > > Cheers > > > > Nigel > > > > --- > > Nigel W. Moriarty > Building 33R0349, Molecular Biophysics and Integrated Bioimaging > > 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 > > > > > > On Mon, Aug 12, 2019 at 12:43 PM Charitha Belluru Shetty < > charitha-belluru.b.shetty(a)gsk.com> wrote: > > Hi Christopher/ Nigel, > > > > Thank you for your quick reply. > > > > The build process was completed without any error. Pasting few of the > lines from it… > > > > > > ===== Running in build: rebuild rotarama > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rota8000-cys.data -> rota8000-cys.pickle: converting ... done. > > rota8000-asp.data -> rota8000-asp.pickle: converting ... done. > > rota8000-ser.data -> rota8000-ser.pickle: converting ... done. > > rota8000-gln.data -> rota8000-gln.pickle: converting ... done. > > rota8000-ile.data -> rota8000-ile.pickle: converting ... done. > > rota8000-pro.data -> rota8000-pro.pickle: converting ... done. > > rota8000-lys.data -> rota8000-lys.pickle: converting ... done. > > rota8000-thr.data -> rota8000-thr.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: converting ... done. > > rota8000-glu.data -> rota8000-glu.pickle: converting ... done. > > rota8000-met.data -> rota8000-met.pickle: converting ... done. > > rota8000-his.data -> rota8000-his.pickle: converting ... done. > > rota8000-leu.data -> rota8000-leu.pickle: converting ... done. > > rota8000-arg.data -> rota8000-arg.pickle: converting ... done. > > rota8000-trp.data -> rota8000-trp.pickle: converting ... done. > > rota8000-asn.data -> rota8000-asn.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: already up to date. > > rota8000-val.data -> rota8000-val.pickle: converting ... done. > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rama8000-ileval-nopreP.data -> rama8000-ileval-nopreP.pickle: converting > ... done. > > rama8000-gly-sym.data -> rama8000-gly-sym.pickle: converting ... done. > > rama8000-cispro.data -> rama8000-cispro.pickle: converting ... done. > > rama8000-general-noGPIVpreP.data -> rama8000-general-noGPIVpreP.pickle: > converting ... done. > > rama8000-transpro.data -> rama8000-transpro.pickle: converting ... done. > > rama8000-prepro-noGP.data -> rama8000-prepro-noGP.pickle: converting ... > done. > > u+s,u,s: 10.06 9.83 0.23 > > ===== Running in .: libtbx.refresh > > Python: 2.7.16 > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/bin/python2.7" > > 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: True > > Enable CUDA: False > > Use conda: False > > Use opt_resources if available: False > > Use environment flags: False > > Enable C++11: False > > Python3 migration warning policy: None > > command_version_suffix: None > > Relocatable paths anchored at: > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/build > > Top-down list of all modules involved: > > mmtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx" > > iotbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx" > > ccp4io+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io_adaptbx" > > smtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx" > > ucif > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/ucif" > > cctbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx" > > scitbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx" > > fable > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable" > > omptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/omptbx" > > boost+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/boost" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx" > > tbxx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/tbxx" > > chiltbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/chiltbx" > > libtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx" > > Creating files in build directory: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/libtbx_refresh.py" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/libtbx_refresh.py" > > Generating C++ header files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family/boost_python" > > Using fable to convert scitbx/lbfgs.f > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/libtbx_refresh.py" > > Generating C++ files in: > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/cctbx/eltbx" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/cctbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/libtbx_refresh.py" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/smtbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/libtbx_refresh.py" > > Processing: "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/exe_dev" > > Regenerating module files in > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/pango not present, > could not regenerate pango files > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/gtk-2.0 not > present, could not regenerate gdk-pixbuf.loaders > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/fonts not present, > could not rebuild fonts > > generating index.theme file > > Done. > > > > *Bootstrap success: build* > > *++++++++++ MolProbity configure.sh finished.* > > > > > > > > [tm375568@uptus060-3 MolProbity]$ ./setup.sh > > ++++++++++ creating directories ... > > ++++++++++ setting permisions ... > > *Couldn't get a file descriptor referring to the console **à I assume > this can be ignored. * > > [tm375568@uptus060-3 MolProbity]$ > > > > Best Regards, > > Charitha Shetty > > > > *From:* Christopher Williams <christopher.sci.williams(a)gmail.com> > *Sent:* Monday, August 12, 2019 3:34 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Nigel Moriarty (nwmoriarty(a)lbl.gov) <nwmoriarty(a)lbl.gov>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Hmm. It looks like Reduce and/or Probe has failed to install correctly. > Most likely an early call to Reduce has resulted in an empty file, which is > then passed into other programs, resulting in error messages. > > > > The configure script ran a build process. Do you know if that process > finished successfully or if it ended with errors? If the build exited > early, it may have never reached the part where Reduce gets compiled. Some > dependencies have changed, and I have been having trouble with my own > builds lately. > > > > It is also possible that there was just a network hiccup that prevented > something from downloading correctly, and a second attempt will work. > > > > I am working on a new configure/install script for more consistent > handling of dependencies. Hopefully it will be ready in about a day. > > > > Good luck, > > -Christopher Williams > > ---Richardson Lab, Duke University > > > > > > > > > > > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* >

1 0

Re: [cctbxbb] Molprobity / CCTBX incompatibility
by Nigel Moriarty 12 Aug '19

12 Aug '19

Once you source the setpaths.sh file in the build directory do you have phenix.reduce or molprobity.reduce? Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging 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 On Mon, Aug 12, 2019 at 12:43 PM Charitha Belluru Shetty < charitha-belluru.b.shetty(a)gsk.com> wrote: > Hi Christopher/ Nigel, > > > > Thank you for your quick reply. > > > > The build process was completed without any error. Pasting few of the > lines from it… > > > > > > ===== Running in build: rebuild rotarama > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rota8000-cys.data -> rota8000-cys.pickle: converting ... done. > > rota8000-asp.data -> rota8000-asp.pickle: converting ... done. > > rota8000-ser.data -> rota8000-ser.pickle: converting ... done. > > rota8000-gln.data -> rota8000-gln.pickle: converting ... done. > > rota8000-ile.data -> rota8000-ile.pickle: converting ... done. > > rota8000-pro.data -> rota8000-pro.pickle: converting ... done. > > rota8000-lys.data -> rota8000-lys.pickle: converting ... done. > > rota8000-thr.data -> rota8000-thr.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: converting ... done. > > rota8000-glu.data -> rota8000-glu.pickle: converting ... done. > > rota8000-met.data -> rota8000-met.pickle: converting ... done. > > rota8000-his.data -> rota8000-his.pickle: converting ... done. > > rota8000-leu.data -> rota8000-leu.pickle: converting ... done. > > rota8000-arg.data -> rota8000-arg.pickle: converting ... done. > > rota8000-trp.data -> rota8000-trp.pickle: converting ... done. > > rota8000-asn.data -> rota8000-asn.pickle: converting ... done. > > rota8000-phetyr.data -> rota8000-phetyr.pickle: already up to date. > > rota8000-val.data -> rota8000-val.pickle: converting ... done. > > Processing data files in > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/chem_data/rotarama_data": > > rama8000-ileval-nopreP.data -> rama8000-ileval-nopreP.pickle: converting > ... done. > > rama8000-gly-sym.data -> rama8000-gly-sym.pickle: converting ... done. > > rama8000-cispro.data -> rama8000-cispro.pickle: converting ... done. > > rama8000-general-noGPIVpreP.data -> rama8000-general-noGPIVpreP.pickle: > converting ... done. > > rama8000-transpro.data -> rama8000-transpro.pickle: converting ... done. > > rama8000-prepro-noGP.data -> rama8000-prepro-noGP.pickle: converting ... > done. > > u+s,u,s: 10.06 9.83 0.23 > > ===== Running in .: libtbx.refresh > > Python: 2.7.16 > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/bin/python2.7" > > 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: True > > Enable CUDA: False > > Use conda: False > > Use opt_resources if available: False > > Use environment flags: False > > Enable C++11: False > > Python3 migration warning policy: None > > command_version_suffix: None > > Relocatable paths anchored at: > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/build > > Top-down list of all modules involved: > > mmtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx" > > iotbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx" > > ccp4io+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/ccp4io_adaptbx" > > smtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx" > > ucif > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/ucif" > > cctbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx" > > scitbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx" > > fable > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable" > > omptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/omptbx" > > boost+adaptbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/boost" > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx" > > tbxx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/tbxx" > > chiltbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/chiltbx" > > libtbx > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx" > > Creating files in build directory: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/libtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/fable/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/iotbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/command_line" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/boost_adaptbx/libtbx_refresh.py" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/scitbx/libtbx_refresh.py" > > Generating C++ header files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/scitbx/array_family/boost_python" > > Using fable to convert scitbx/lbfgs.f > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/cctbx/libtbx_refresh.py" > > Generating C++ files in: > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/cctbx/eltbx" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/cctbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/smtbx/libtbx_refresh.py" > > Generating C++ files in: > > > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/include/smtbx/boost_python" > > Processing: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/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: > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/libtbx_refresh.py" > > Processing: "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/exe_dev" > > Regenerating module files in > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/pango not present, > could not regenerate pango files > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/gtk-2.0 not > present, could not regenerate gdk-pixbuf.loaders > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/base/etc/fonts not present, > could not rebuild fonts > > generating index.theme file > > Done. > > > > *Bootstrap success: build* > > *++++++++++ MolProbity configure.sh finished.* > > > > > > > > [tm375568@uptus060-3 MolProbity]$ ./setup.sh > > ++++++++++ creating directories ... > > ++++++++++ setting permisions ... > > *Couldn't get a file descriptor referring to the console **à** I assume > this can be ignored.* > > [tm375568@uptus060-3 MolProbity]$ > > > > Best Regards, > > Charitha Shetty > > > > *From:* Christopher Williams <christopher.sci.williams(a)gmail.com> > *Sent:* Monday, August 12, 2019 3:34 PM > *To:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Cc:* Nigel Moriarty (nwmoriarty(a)lbl.gov) <nwmoriarty(a)lbl.gov>; > cctbxbb(a)phenix-online.org; Robert Nolte <robert.t.nolte(a)gsk.com> > *Subject:* Re: Molprobity / CCTBX incompatibility > > > > *EXTERNAL* > > Hmm. It looks like Reduce and/or Probe has failed to install correctly. > Most likely an early call to Reduce has resulted in an empty file, which is > then passed into other programs, resulting in error messages. > > > > The configure script ran a build process. Do you know if that process > finished successfully or if it ended with errors? If the build exited > early, it may have never reached the part where Reduce gets compiled. Some > dependencies have changed, and I have been having trouble with my own > builds lately. > > > > It is also possible that there was just a network hiccup that prevented > something from downloading correctly, and a second attempt will work. > > > > I am working on a new configure/install script for more consistent > handling of dependencies. Hopefully it will be ready in about a day. > > > > Good luck, > > -Christopher Williams > > ---Richardson Lab, Duke University > > > > > > > > > > > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* >

1 0

Re: [cctbxbb] Molprobity / CCTBX incompatibility
by Nigel Moriarty 12 Aug '19

12 Aug '19

Not sure about the selection problem but the missing commands are likely molprobity.reduce and molprobity.probe. Chris, you should be able to change that. Cheers Nigel --- Nigel W. Moriarty Building 33R0349, Molecular Biophysics and Integrated Bioimaging 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 On Mon, Aug 12, 2019 at 11:43 AM Charitha Belluru Shetty < charitha-belluru.b.shetty(a)gsk.com> wrote: > Hi Christopher/Nigel, > > > > We downloaded the molprobity after the patch and ran the configure.sh and > setup scripts. Now things got worst. > > > > Can you please help us on this. > > > > Here is the output we are getting. > > > > > > > > > > > > > > When we press the *“Click here”* button, below log file is generated. > > > > [PLACE YOUR COMMENTS HERE] > > > > ================================================== > > USER / SERVER INFORMATION > > ================================================== > > User IP : 11.27.95.128 > > User browser : Mozilla/5.0 (Windows NT 10.0; Win64; x64) > AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.100 Safari/537.36 > > Session ID : c2h8n399dagb0ggfn8kpla6fu4 > > Session URL : > http://uptus002vm.corpnet2.com/molprobity/index.php?MolProbSID=c2h8n399dagb… > > > > MolProb. ver. : 4.4 > > Server name : uptus002vm.corpnet2.com > > Server time : 2019 Aug 12 18:24:41 > > > > ================================================== > > ERRORS FROM THIS SESSION > > ================================================== > > > > > > sh: phenix.reduce: command not found > > sh: phenix.reduce: command not found > > sh: phenix.reduce: command not found > > sh: phenix.probe: command not found > > sh: phenix.probe: command not found > > sh: phenix.reduce: command not found > > sh: phenix.reduce: command not found > > sh: phenix.probe: command not found > > sh: phenix.probe: command not found > > > > Starting phenix.clashscore > > on Mon Aug 12 13:50:31 2019 by appmgmt > > > =============================================================================== > > > > Processing files: > > > ------------------------------------------------------------------------------- > > > > Files not used by program: > > -------------------------- > > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/public_html/data/c2h8n399dagb0ggfn8kpla6fu4/coordinates/1irkFH.pdb > > > > Processing PHIL parameters: > > > ------------------------------------------------------------------------------- > > > > Adding command-line PHIL: > > ------------------------- > > b_factor_cutoff=40 > > clash_cutoff=-0.4 > > > > Final processed PHIL parameters: > > > ------------------------------------------------------------------------------- > > data_manager { > > default_output_filename = "cctbx_program" > > } > > b_factor_cutoff = 40 > > > > > > Starting job > > > =============================================================================== > > Sorry: 0 model(s) found. Expected at least 1. > > chartClashlist ran for 5 seconds > > do Charts ran for 0 seconds > > sh: phenix.probe: command not found > > do Kinemage ran for 0 seconds > > > > Traceback (most recent call last): > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/../modules/cctbx_project/mmtbx/command_line/mp_geo.py", > line 7, in <module> > > mp_geo.run(sys.argv[1:]) > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/validation/molprobity/mp_geo.py", > line 132, in run > > pdb_hierarchy.models()[0].chains(): > > IndexError: list index out of range > > > > > > > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.probe: command not found > > > > > > > > Starting phenix.clashscore > > > > on Mon Aug 12 13:50:31 2019 by appmgmt > > > > > =============================================================================== > > > > > > > > Processing files: > > > > > ------------------------------------------------------------------------------- > > > > > > > > Files not used by program: > > > > -------------------------- > > > > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/public_html/data/c2h8n399dagb0ggfn8kpla6fu4/coordinates/1irkFH.pdb > > > > > > > > Processing PHIL parameters: > > > > > ------------------------------------------------------------------------------- > > > > > > > > Adding command-line PHIL: > > > > ------------------------- > > > > b_factor_cutoff=40 > > > > clash_cutoff=-0.4 > > > > > > > > Final processed PHIL parameters: > > > > > ------------------------------------------------------------------------------- > > > > data_manager { > > > > default_output_filename = "cctbx_program" > > > > } > > > > b_factor_cutoff = 40 > > > > > > > > > > > > Starting job > > > > > =============================================================================== > > > > Sorry: 0 model(s) found. Expected at least 1. > > > > chartClashlist ran for 5 seconds > > > > do Charts ran for 0 seconds > > > > sh: phenix.probe: command not found > > > > do Kinemage ran for 0 seconds > > > > > > > > Traceback (most recent call last): > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/../modules/cctbx_project/mmtbx/command_line/mp_geo.py", > line 7, in <module> > > > > mp_geo.run(sys.argv[1:]) > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/validation/molprobity/mp_geo.py", > line 132, in run > > > > pdb_hierarchy.models()[0].chains(): > > > > IndexError: list index out of range > > > > > > > > > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.reduce: command not found > > > > sh: phenix.probe: command not found > > > > sh: phenix.probe: command not found > > > > > > > > Starting phenix.clashscore > > > > on Mon Aug 12 13:50:31 2019 by appmgmt > > > > > =============================================================================== > > > > > > > > Processing files: > > > > > ------------------------------------------------------------------------------- > > > > > > > > Files not used by program: > > > > -------------------------- > > > > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/public_html/data/c2h8n399dagb0ggfn8kpla6fu4/coordinates/1irkFH.pdb > > > > > > > > Processing PHIL parameters: > > > > > ------------------------------------------------------------------------------- > > > > > > > > Adding command-line PHIL: > > > > ------------------------- > > > > b_factor_cutoff=40 > > > > clash_cutoff=-0.4 > > > > > > > > Final processed PHIL parameters: > > > > > ------------------------------------------------------------------------------- > > > > data_manager { > > > > default_output_filename = "cctbx_program" > > > > } > > > > b_factor_cutoff = 40 > > > > > > > > > > > > Starting job > > > > > =============================================================================== > > > > Sorry: 0 model(s) found. Expected at least 1. > > > > chartClashlist ran for 5 seconds > > > > do Charts ran for 0 seconds > > > > sh: phenix.probe: command not found > > > > do Kinemage ran for 0 seconds > > > > > > > > Traceback (most recent call last): > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/../modules/cctbx_project/mmtbx/command_line/mp_geo.py", > line 7, in <module> > > > > mp_geo.run(sys.argv[1:]) > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/validation/molprobity/mp_geo.py", > line 132, in run > > > > pdb_hierarchy.models()[0].chains(): > > > > IndexError: list index out of range > > > > > > > > > > > > > > > > > > > > sh: phenix.reduce: command not found > > > > > > > > sh: phenix.reduce: command not found > > > > > > > > sh: phenix.reduce: command not found > > > > > > > > sh: phenix.probe: command not found > > > > > > > > sh: phenix.probe: command not found > > > > > > > > sh: phenix.reduce: command not found > > > > > > > > sh: phenix.reduce: command not found > > > > > > > > sh: phenix.probe: command not found > > > > > > > > sh: phenix.probe: command not found > > > > > > > > > > > > > > > > Starting phenix.clashscore > > > > > > > > on Mon Aug 12 13:50:31 2019 by appmgmt > > > > > > > > > =============================================================================== > > > > > > > > > > > > > > > > Processing files: > > > > > > > > > ------------------------------------------------------------------------------- > > > > > > > > > > > > > > > > Files not used by program: > > > > > > > > -------------------------- > > > > > > > > > /hpc/apps/2018/molprobity/v4.4.app/MolProbity/public_html/data/c2h8n399dagb0ggfn8kpla6fu4/coordinates/1irkFH.pdb > > > > > > > > > > > > > > > > Processing PHIL parameters: > > > > > > > > > ------------------------------------------------------------------------------- > > > > > > > > > > > > > > > > Adding command-line PHIL: > > > > > > > > ------------------------- > > > > > > > > b_factor_cutoff=40 > > > > > > > > clash_cutoff=-0.4 > > > > > > > > > > > > > > > > Final processed PHIL parameters: > > > > > > > > > ------------------------------------------------------------------------------- > > > > > > > > data_manager { > > > > > > > > default_output_filename = "cctbx_program" > > > > > > > > } > > > > > > > > b_factor_cutoff = 40 > > > > > > > > > > > > > > > > > > > > > > > > Starting job > > > > > > > > > =============================================================================== > > > > > > > > Sorry: 0 model(s) found. Expected at least 1. > > > > > > > > chartClashlist ran for 5 seconds > > > > > > > > do Charts ran for 0 seconds > > > > > > > > sh: phenix.probe: command not found > > > > > > > > do Kinemage ran for 0 seconds > > > > > > > > > > > > > > > > Traceback (most recent call last): > > > > > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/build/../modules/cctbx_project/mmtbx/command_line/mp_geo.py", > line 7, in <module> > > > > > > > > mp_geo.run(sys.argv[1:]) > > > > > > > > File > "/hpc/apps/2018/molprobity/v4.4.app/MolProbity/modules/cctbx_project/mmtbx/validation/molprobity/mp_geo.py", > line 132, in run > > > > > > > > pdb_hierarchy.models()[0].chains(): > > > > > > > > IndexError: list index out of range > > > > > > Best Regards, > > Charitha Shetty > > > > *From:* Robert Nolte > *Sent:* Sunday, August 11, 2019 12:39 PM > *To:* Nigel Moriarty (nwmoriarty(a)lbl.gov) <nwmoriarty(a)lbl.gov>; > cctbxbb(a)phenix-online.org > *Cc:* Charitha Belluru Shetty <charitha-belluru.b.shetty(a)gsk.com> > *Subject:* Molprobity / CCTBX incompatibility > > > > We are trying to reinstall our internal molprobity server, and have hit an > issue with the github version where it appears to be a version conflict > with the version of cctbx that is currently being downloaded by > configuration script in the master branch of molprobity. We are getting > errors when we run the validation routine such as > > > > Unrecogized PHIL parameter: data_version=8000 > > > > or > > > > Unrecognized PHIL parameter: clash_cutoff=-0.4 > > > > The analysis for clashscore, rotalyze, are failing to run and we get a > number of divide by zero errors for several of the other ‘visualize’ and > ‘eff_resolution’ routines. > > > > Can you help get this working. > > Thanks, > > Bob Nolte > > > > > > > > *GSK monitors email communications sent to and from GSK in order to > protect GSK, our employees, customers, suppliers and business partners, > from cyber threats and loss of GSK Information. GSK monitoring is conducted > with appropriate confidentiality controls and in accordance with local laws > and after appropriate consultation.* >

1 0

Molprobity / CCTBX incompatibility
by Robert Nolte 11 Aug '19

11 Aug '19

We are trying to reinstall our internal molprobity server, and have hit an issue with the github version where it appears to be a version conflict with the version of cctbx that is currently being downloaded by configuration script in the master branch of molprobity. We are getting errors when we run the validation routine such as Unrecogized PHIL parameter: data_version=8000 or Unrecognized PHIL parameter: clash_cutoff=-0.4 The analysis for clashscore, rotalyze, are failing to run and we get a number of divide by zero errors for several of the other 'visualize' and 'eff_resolution' routines. Can you help get this working. Thanks, Bob Nolte GSK monitors email communications sent to and from GSK in order to protect GSK, our employees, customers, suppliers and business partners, from cyber threats and loss of GSK Information. GSK monitoring is conducted with appropriate confidentiality controls and in accordance with local laws and after appropriate consultation.

1 0

Azure pipelines Linux builds failing with segmentation fault
by richard.gildea＠diamond.ac.uk 01 Aug '19

01 Aug '19

Recent Azure builds are failing for the Linux builds with the following error: ##[section]Starting: Test ============================================================================== Task : Command line Description : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows Version : 2.151.2 Author : Microsoft Corporation Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line ============================================================================== Generating script. ========================== Starting Command Output =========================== [command]/bin/bash --noprofile --norc /__w/_temp/823d09b8-e953-4f93-a9a8-0d863a25f1ce.sh /__w/_temp/823d09b8-e953-4f93-a9a8-0d863a25f1ce.sh: line 11: 6307 Segmentation fault (core dumped) libtbx.run_tests_parallel module=boost_adaptbx module=cctbx module=cma_es module=fable module=gltbx module=iotbx module=libtbx module=rstbx module=scitbx module=simtbx module=smtbx module=spotfinder module=annlib_adaptbx module=cbflib_adaptbx nproc=4 ##[error]Bash exited with code '139'. ##[section]Finishing: Test https://dev.azure.com/cctbx/cctbx_project/_build/results?buildId=256 The last successful Linux Python 2.7 master build was https://dev.azure.com/cctbx/cctbx_project/_build/results?buildId=240 The first failing Linux Python 2.7 master build was https://dev.azure.com/cctbx/cctbx_project/_build/results?buildId=245 Mac builds appear to be fine. Does anyone have any idea what is the issue? Cheers, Richard Dr Richard Gildea Data Analysis Scientist Tel: +441235 77 8078 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 2

Failing tests on python3 builds
by richard.gildea＠diamond.ac.uk 30 Jul '19

30 Jul '19

Hi, Whilst looking into test failures reported against a pull request I currently have open, I noticed that there are several (9) failing tests on the Python 3 build. It appears that Markus reported these 3 weeks ago - is anyone looking into these failures? Having builds permanently reporting failure isn't particularly helpful as it discourages people from looking at the results, and will likely lead to further Python 3 regressions being introduced into the codebase. https://dev.azure.com/cctbx/cctbx_project/_build/results?buildId=240 https://github.com/cctbx/cctbx_project/issues Cheers, Richard Dr Richard Gildea Data Analysis Scientist Tel: +441235 77 8078 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

3 4

"duplicate" cif categories
by wtempel 06 Jul '19

06 Jul '19

Hi, wwpdb onedep recently rejected a file that I had manipulated (but not validated, I admit) in IOTBX. The error was "duplicate categories", or a similar complaint. I had added _reflns.* items related to data processing to a phenix.refine cif file that already included a _reflns.B_iso_Wilson_estimate. Merely running sort() on the relevant block made the error go away, but who knows what side effects there may have been. Does the CCTBX ecosystem provide some higher-level management of cif categories? Thanks. Wolfram

1 0

align density maps
by Peter Schmidtke 02 Jul '19

02 Jul '19

2 3

pickling nan values
by Robert Oeffner 13 Jun '19

13 Jun '19

Hi all, It seems that a flex.double array containing "nan" values doesn't survive pickling as in: oeffner@grove:~$ cctbx.python Python 2.7.15 (default, Sep 11 2018, 23:48:45) [GCC 4.4.7 20120313 (Red Hat 4.4.7-18)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> >>> from cctbx.array_family import flex >>> import pickle >>> flex_nans = flex.double(3, float('nan')) >>> list(flex_nans) [nan, nan, nan] >>> list(pickle.loads( pickle.dumps(flex_nans))) [0.0, 0.0, 0.0] >>> >>> If the flex double is cast into a python list then it does survive pickling as in: >>> >>> list(pickle.loads( pickle.dumps(list( flex_nans )))) [nan, nan, nan] >>> I would like to use nan values to indicate missing or invalid data values. Would anyone have a suggestion how to go about this? Many thanks, Rob -- Robert Oeffner, Ph.D. Research Associate, The Read Group Department of Haematology, Cambridge Institute for Medical Research University of Cambridge Cambridge Biomedical Campus The Keith Peters Building Hills Road Cambridge CB2 0XY www.cimr.cam.ac.uk/investigators/read/index.html tel: +44(0)1223 763234

2 1

Fwd: Conda/DIALS 1.14.5 source build with --use-conda does not work
by Nicholas Devenish 28 May '19

28 May '19

(Forwarding this manually as apparently my Diamond address isn't on cctbxbb) Hi All, On 24 May 2019, at 14:12, David Waterman - UKRI STFC < david.waterman(a)stfc.ac.uk<mailto:[email protected]>> wrote: > In the process, I discovered that the source builds we point to from > https://dials.github.io/installation.html don't work with --use-conda > because the paths to various packages are out of date. This seems to be to be a fundamental problem with the conda implementation? Let’s try to reproduce an old build from, say, 1st march: the point in cctbx_project at which dials 1.14 split off. This is https://github.com/cctbx/cctbx_project/commit/35652e06564da7ff989500a6d929b… . Try reproducing this point: git clone git(a)github.com<mailto:[email protected]>:cctbx/cctbx_project.git modules/cctbx_project ( cd modules/cctbx_project/ && git checkout 35652e06564da7ff989500a6d929bc595f69040f ) ln -s modules/cctbx_project/libtbx/auto_build/bootstrap.py . ./bootstrap.py base --use-conda —> many "An HTTP error occurred when trying to retrieve this URL.” This means that with the current conda implementation it’s impossible to guarantee reproducibility for any build beyond the past few days, without lots and lots of manual work reconstructing the versioning out of the file list dump. Because the version constraints aren’t kept with the repository, this means that a source distribution is not nearly enough to recreate any given release. This seems like a problem? Nick

3 2

Python3 / scons / non-conda builds
by Graeme.Winter＠Diamond.ac.uk 13 May '19

13 May '19

Dear All, Back in the mists of time, one could build cctbx modules without bootstrap or conda by having the right modules available yourself - a so-called baseless install which I think is still important in X-fel land? Anyhow, trying this with Python3 suggests that we have some special constraints which are perhaps too tight regarding module locations - for example scons - Grey-Area p3_compile :( $ pip3 install scons Collecting scons Downloading https://files.pythonhosted.org/packages/65/41/ac58638421414acc64e26fc120c81… (831kB) 100% |████████████████████████████████| 839kB 14.3MB/s Installing collected packages: scons Successfully installed scons-3.0.5 You are using pip version 19.0.1, however version 19.1.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Grey-Area p3_compile :) $ make ./bin/libtbx.scons -j "`./bin/libtbx.show_number_of_processors`" ModuleNotFoundError: No module named 'SCons' During handling of the above exception, another exception occurred: Sorry: SCons is not available. A possible solution is to unpack a SCons distribution in one of these directories: "/Users/graeme/svn/scr" "/Users/graeme/svn/scr/cctbx_project" SCons distributions are available at this location: http://www.scons.org/ It may be necessary to rename the unpacked distribution, e.g.: mv scons-0.96.1 scons make: *** [default] Error 1 Grey-Area p3_compile :( $ which scons /Library/Frameworks/Python.framework/Versions/3.7/bin/scons Should we require that scons is installed as part of cctbx when it is already installed on the system? If we *do* have to have this constraint, maybe that should be checked at configure time (where it complains about six and future) Thoughts? In other news - the syntax changing branch referenced in https://github.com/cctbx/cctbx_project/pull/325 now compiles correctly on Python3 (note: not run, just compile but this means that it’s purpose is done) for the modules which it intends to touch and has no conflicts right now… Best wishes 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

2 2

Overloading Python builtin names with local variables
by Graeme.Winter＠Diamond.ac.uk 03 May '19

03 May '19

Morning all, As a side-effect of looking at some of the Python3 refactoring I stumbled across a few places where e.g. range is used as a variable name. While this is fine and legal, when moving the code to Python3 xrange => range and from builtins import range is a back-port of Python3 range to Python2 which allows the existing behaviour of xrange generator to be maintained This is fine except for where range is a variable name and we then get a “variable referenced before assignment” type error As a general statement I would say overloading Python reserved names with local variables is untidy at best, and can easily cause confusion (as well as real problems as identified above) - I have therefore taken the liberty of adding a tool to libtbx which can be used to find such variables to give people a chance to avoid them: Grey-Area dxtbx :) [master] $ libtbx.find_reserved_names format/ Checking format/ format/FormatSMVRigakuSaturn.py:239 "format" format = self._scan_factory.format("SMV") format/FormatTIFFRayonixESRF.py:36 "format" format = {LITTLE_ENDIAN: "<", BIG_ENDIAN: ">"}[order] format/FormatTIFFRayonixESRF.py:29 "bytes" width, height, depth, order, bytes = FormatTIFFRayonix.get_tiff_header( format/FormatCBFMini.py:231 "format" format = self._scan_factory.format("CBF") format/FormatTIFFRayonix.py:176 "format" format = self._scan_factory.format("TIFF") format/FormatTIFFRayonix.py:31 "bytes" width, height, depth, order, bytes = FormatTIFF.get_tiff_header(image_file) format/FormatTIFFRayonix.py:74 "bytes" width, height, depth, order, bytes = FormatTIFF.get_tiff_header(image_file) format/FormatSMVRigakuEiger.py:243 "format" format = self._scan_factory.format("SMV") format/FormatSMVADSC.py:212 "format" format = self._scan_factory.format("SMV") format/Registry.py:88 "format" for format in sorted(self._formats, key=lambda x: x.__name__): format/FormatSMVJHSim.py:141 "format" format = self._scan_factory.format("SMV") format/FormatSMVRigakuPilatus.py:188 "format" format = self._scan_factory.format("SMV") format/FormatSMVADSCSN928.py:47 "format" format = self._scan_factory.format("SMV") format/FormatRAXISIVSpring8.py:134 "format" format = self._scan_factory.format("RAXIS") format/FormatTIFFRayonixSPring8.py:31 "bytes" width, height, depth, order, bytes = FormatTIFFRayonix.get_tiff_header( format/FormatSMVADSCmlfsom.py:37 "format" format = self._scan_factory.format("SMV") format/FormatTIFFBruker.py:174 "format" format = self._scan_factory.format("TIFF") format/FormatTIFFBruker.py:31 "bytes" width, height, depth, order, bytes = FormatTIFF.get_tiff_header(image_file) format/FormatTIFFBruker.py:71 "bytes" width, height, depth, order, bytes = FormatTIFF.get_tiff_header(image_file) format/FormatCBFMiniADSCHF4M.py:26 "format" for format in ["%a_%b_%d_%H:%M:%S_%Y"]: format/FormatCBFMiniADSCHF4M.py:169 "format" format = self._scan_factory.format("CBF") format/FormatSMVADSCNoDateStamp.py:54 "format" format = self._scan_factory.format("SMV") format/FormatSMVRigakuSaturnNoTS.py:228 "format" format = self._scan_factory.format("SMV") format/FormatPYunspecified.py:152 "format" format = "" format/FormatSMVRigakuA200.py:234 "format" format = self._scan_factory.format("SMV") format/FormatCBFMiniEigerPhotonFactory.py:131 "format" format = self._scan_factory.format("CBF") format/FormatSMVTimePix_SU.py:97 "format" format = self._scan_factory.format("SMV") format/FormatCBFMiniPilatus.py:83 "format" format = self._scan_factory.format("CBF") format/FormatCBFMiniPilatusHelpers.py:22 "format" for format in ["%Y-%b-%dT%H:%M:%S", "%Y-%m-%dT%H:%M:%S", "%Y/%b/%d %H:%M:%S"]: format/FormatSMVADSCSNAPSID19.py:91 "format" format = self._scan_factory.format("SMV") format/FormatCBFMiniEiger.py:216 "format" format = self._scan_factory.format("CBF") format/FormatSMVNOIR.py:218 "format" format = self._scan_factory.format("SMV") format/FormatSMVCMOS1.py:197 "format" format = self._scan_factory.format("SMV") format/FormatRAXIS.py:238 "format" format = self._scan_factory.format("RAXIS") is an example where “format” is scattered all over the place but is also a useful function - replacing with fmt will mean the same and avoid this overloading, as an example. This uses AST parsing to work through the code and find variable assignments - doing this for dials found lots of examples of “file” and “type” being used. How much people care about this is a local issue, but I thought the tool would be useful All the best 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

modulo operation on flex.double
by Robert Oeffner 11 Apr '19

11 Apr '19

Hi, I have a flex.double array of phase values between -360 and 360 degrees I would like to cast them all in one go to lie within 0 to 360. Does anybody know if there is a nice way of doing this with flex arrays? The modulo operator doesn't seem to be supported for flex arrays unlike the +, -, * and the / operators. This would otherwise be handy as I could then convert the array in one line of code like phases = phases % 360.0 If not I guess I'll have to numpy the problem :-) Many thanks, Rob

5 5

Re: [cctbxbb] cannot compile Phenix
by R. D. Oeffner 06 Apr '19

06 Apr '19

>From the messages on the cctbx github mailing list it seems that Dials people have been extricating dxtbx from cctbx_project. Rob -----Original Message----- From: Pavel Afonine Sent: Saturday, April 6, 2019 7:07 PM To: phenixdev Subject: cannot compile Phenix Hi, anyone knows why current Phenix code is broken: python bootstrap.py --builder=phenix --sfuser=afonine --cciuser=afonine update python bootstrap.py --builder=phenix --sfuser=afonine --cciuser=afonine build --nproc=12 leads to (...) AttributeError: 'empty' object has no attribute 'dxtbx_include': File "/Users/pafonine/phenix/build/SConstruct", line 31: SConscript("spotfinder/SConscript") File "/Users/pafonine/phenix/modules/scons/engine/SCons/Script/SConscript.py", line 607: return method(*args, **kw) File "/Users/pafonine/phenix/modules/scons/engine/SCons/Script/SConscript.py", line 544: return _SConscript(self.fs, *files, **subst_kw) File "/Users/pafonine/phenix/modules/scons/engine/SCons/Script/SConscript.py", line 253: call_stack[-1].globals) File "/Users/pafonine/phenix/modules/cctbx_project/spotfinder/SConscript", line 22: env_etc.dxtbx_include, usr+sys time: 1.94 seconds wall clock time: 4.51 seconds Process failed with return code 2 Any idea for a workaround? Pavel --- This email has been checked for viruses by AVG. https://www.avg.com

2 3

jupyter notebook
by wtempel 02 Apr '19

02 Apr '19

Hi all, how does one configure, and run inside a jupyter notebook, a cctbx-enabled kernel, beginning with a downloaded [cctbx build]( http://cci.lbl.gov/cctbx_build/)? [This page]( https://medium.com/@sljack1992/making-a-custom-ipython-notebook-kernel-c59e…) seems to describe the first part, but may no longer apply to more recent cctbx builds. Thanks. Wolfram Tempel

2 1

mtz2map gridding
by Elliot Nelson 21 Feb '19

21 Feb '19

Hi All, I've been trying to use Phenix.mtz2map to sample maps to a particular array size with the "gridding" option, but found that this seems to have no effect on the output of the program. I was wondering whether there were some restrictions to the integers that are permitted or otherwise what might be the cause of this behaviour. Having hunted through the code it seems to just set n_real in the crystal gridding, which is then fed into an fft - possibly the latter ignores n_reals that aren't sensible? Any idea? Thanks, Conor on behalf of Conor Wild: conor.wild(a)oriel.ox.ac.uk Elliot DPhil Student, Systems Approaches to Biomedical Science<http://www.sabsidc.ox.ac.uk/> Protein Crystallography<http://www.thesgc.org/groupprofile/9489>, Structural Genomics Consortium, NDM, University of Oxford Oxford Protein Informatics Group<http://opig.stats.ox.ac.uk/>, Department of Statistics, University of Oxford

2 1

OpenMP in fftpack
by Keitaro Yamashita 31 Jan '19

31 Jan '19

Dear CCTBX/PHENIX developers, According to PHENIX FAQ: https://www.phenix-online.org/documentation/faqs/index.html#general > In addition to these options, it is also possible to compile phenix.refine and Phaser with the OpenMP library, which automatically parallelizes specific instructions such as the FFT. This requires using the source installer for Phenix, and adding the argument "--openmp" to the install command. Because of threading conflicts, OpenMP is not compatible with the Phenix GUI. FFT in phenix.refine can be parallelized if OpenMP is enabled. However, it seems incorrect since 2017 due to this change: https://github.com/cctbx/cctbx_project/commit/3e932248e0491847a04ddeee429f8… The FAQ may need updating, but I am curious to know why it is disabled now. Best regards, Keitaro

1 0

This is a test
by Billy Poon 28 Jan '19

28 Jan '19

The Phenix website was down for a few hours, so this is a test to see if the bulletin board is working. -- 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/cctbx] master: Fix typo geobox (1ad3fe055)
by Pavel Afonine 22 Dec '18

22 Dec '18

Bad idea to hard-wire package name into lowest level code. Now imagine we need the same for afit, amber, quantumbio, rosetta, etc.. Are we going to have a page-long block of "if" statements. Please re-think and remove. For example, whether you want to shift it or not can be a parameter that you cast way level up in the context specific code. Pavel On 12/20/18 09:53, CCTBX commit wrote: > Repository : ssh://g18-sc-serv-04.diamond.ac.uk/cctbx > On branch : master > > ------------------------------------------------------------------------ > > > commit 1ad3fe05571162839e770c35ed032a7fc38a33b7 > Author: Gydo van Zundert <gydo.vanzundert(a)schrodinger.com> > Date: Wed Dec 19 14:58:36 2018 -0500 > > Fix typo geobox > > > ------------------------------------------------------------------------ > > > 1ad3fe05571162839e770c35ed032a7fc38a33b7 > mmtbx/refinement/real_space/individual_sites.py | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/mmtbx/refinement/real_space/individual_sites.py > b/mmtbx/refinement/real_space/individual_sites.py > index c61e88b01..20f38a6b0 100644 > --- a/mmtbx/refinement/real_space/individual_sites.py > +++ b/mmtbx/refinement/real_space/individual_sites.py > @@ -350,7 +350,7 @@ class box_refinement_manager(object): > > # When using the Schrodinger force field, move the whole > structure as the > # selected atoms are environment aware. > - if geobox.get_source() == 'SCHRODINGER': > + if geo_box.get_source() == 'SCHRODINGER': > geo_box.shift_cart(box.shift_cart) > > rsr_simple_refiner = simple( > @@ -377,7 +377,7 @@ class box_refinement_manager(object): > iselection, sites_cart_refined) > self.xray_structure.set_sites_cart(sites_cart_moving) > self.sites_cart = self.xray_structure.sites_cart() > - if geobox.get_source() == 'SCHRODINGER': > + if geo_box.get_source() == 'SCHRODINGER': > geo_box.shift_cart(shift_back) > else: # NCS constraints are present > # select on xrs, grm, ncs_groups > > ------------------------------------------------------------------------ > > To unsubscribe from the CCTBX-COMMIT list, click the following link: > https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=CCTBX-COMMIT&A=1 >

4 6

Broken iotbx/pdb/cif test
by richard.gildea＠diamond.ac.uk 19 Dec '18

19 Dec '18

According to Jenkins these two tests have been broken for several days - does anyone know what the issue is and could a fix be applied? Both look like the same error. iotbx/regression/tst_pdb_as_cif.py iotbx/regression/tst_data_manager.py These have been failing since this commit: https://github.com/cctbx/cctbx_project/commit/2c119fcf012ca4cc60dfce231902c… The tests also fail locally for me (not just on Jenkins). Cheers, Richard Traceback (most recent call last): File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/iotbx/regression/tst_pdb_as_cif.py", line 106, in <module> exercise_01() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/iotbx/regression/tst_pdb_as_cif.py", line 37, in exercise_01 logger=null_out(), File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/iotbx/cli_parser.py", line 71, in run_program task.run() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/programs/pdb_as_cif.py", line 37, in run txt = model.model_as_mmcif() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 879, in model_as_mmcif if self.get_restraints_manager() is not None: File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 622, in get_restraints_manager self.setup_restraints_manager() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 1042, in setup_restraints_manager self._process_input_model() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 959, in _process_input_model use_neutron_distances = self._pdb_interpretation_params.pdb_interpretation.use_neutron_distances) File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/utils/__init__.py", line 998, in __init__ use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 675, in __init__ use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 689, in convert_all use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 700, in convert_lib_atom entry = cif_types.energy_lib_atom(**dict(row)) File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/cif_types.py", line 49, in __init__ raise_value_error("Floating-point") File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/cif_types.py", line 39, in raise_value_error expected_type, looped_id.split(":",1)[0], val)) ValueError: Floating-point value expected in CIF file: _lib_atom.ion_radius 1,7 Traceback (most recent call last): File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/iotbx/regression/tst_data_manager.py", line 532, in <module> test_model_datatype() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/iotbx/regression/tst_data_manager.py", line 233, in test_model_datatype dm.get_model().model_as_mmcif(), overwrite=True) File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 879, in model_as_mmcif if self.get_restraints_manager() is not None: File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 622, in get_restraints_manager self.setup_restraints_manager() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 1042, in setup_restraints_manager self._process_input_model() File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/model/model.py", line 959, in _process_input_model use_neutron_distances = self._pdb_interpretation_params.pdb_interpretation.use_neutron_distances) File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/utils/__init__.py", line 998, in __init__ use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 675, in __init__ use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 689, in convert_all use_neutron_distances=use_neutron_distances, File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/server.py", line 700, in convert_lib_atom entry = cif_types.energy_lib_atom(**dict(row)) File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/cif_types.py", line 49, in __init__ raise_value_error("Floating-point") File "/scratch/jenkins_slave/workspace/cctbx_tests/build_dials/modules/cctbx_project/mmtbx/monomer_library/cif_types.py", line 39, in raise_value_error expected_type, looped_id.split(":",1)[0], val)) ValueError: Floating-point value expected in CIF file: _lib_atom.ion_radius 1,7 Dr Richard Gildea Data Analysis Scientist Tel: +441235 77 8078 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

3 7

forcing building boost_python early in SConscript
by Robert Oeffner 17 Nov '18

17 Nov '18

We are working on a newer version of Phaser. The new SConscript file for Phaser imports features from boost_python. Therefore it is currently not straightforward to build it since an empty build directory does not yet contain the boost_python module to be imported by SConscript (or python). So SCons crashes when it reads the new Phaser SCsonscript stating that boost_python cannot be imported. Currently our workaround is to first build CCTBX alone and then subsequently to build Phaser. My question is if it is possible to specify dependencies in cctbx_project/boost_adaptbx/SConscript to force building boost_python early on. On Windows boost_thread and a few other libraries are built before other SConscript files are read. So I have put some Depends(boost_thread, boost_python) andDepends(boost_thread, boost_python_meta_ext) statements into cctbx_project/boost_adaptbx/SConscript. These do seem to force building the boost_python.lib and .dll files. But building the boost_python_meta_ext python module fails with the error: boost_adaptbx\meta_ext.cpp(14): fatal error C1083: Cannot open include file: 'boost_adaptbx/type_id_eq.h' It's possible that I'm not using SCons as it's supposed to be used. Let me know if anyone has a suggestion on how to force building boost_python before other SConscript are read. Many thanks, Rob -- Robert Oeffner, Ph.D. Research Associate, The Read Group Department of Haematology, Cambridge Institute for Medical Research University of Cambridge Cambridge Biomedical Campus Wellcome Trust/MRC Building Hills Road Cambridge CB2 0XY www.cimr.cam.ac.uk/investigators/read/index.html tel: +44(0)1223 763234

5 5

Fwd: Re: indexing diffraction pattern
by Pavel Afonine 14 Nov '18

14 Nov '18

Perhaps someone can reply Wen.. Pavel -------- Forwarded Message -------- Subject: Re: indexing diffraction pattern Date: Sat, 10 Nov 2018 09:30:53 -0500 From: Wen Jiang <jiang12(a)purdue.edu> To: Pavel Afonine <pafonine(a)lbl.gov> Pavel, Sorry for insufficient details. The scenario is that I have a numpy 2D array of float values that represents an image of "diffraction pattern" (generated by an image processing operation, not actual X-ray diffraction). I need to determine the peak positions and then find a 2D lattice (two 2D vectors) going through these peaks. I have my own simple functions that can detect the peaks and find a 2-D lattice to cross the peaks but it often fails when the "diffraction pattern" is not very clean. Thus, I want to find a more robust method that works well when the peaks are relatively weak, not very sharp, and when there are some spurious peaks off the lattice. I think these tasks are exactly what cctbx has solved for indexing X-ray diffraction images. Hope that these explanations help clarify the problem. Thanks, Wen Prof. Wen Jiang Department of Biological Sciences Department of Chemistry (Courtesy) Scientific Director, Purdue Cryo-EM Facility Purdue University Hockmeyer Hall of Structural Biology 240 S. Martin Jischke Drive West Lafayette, IN 47907 http://jiang.bio.purdue.edu On Sat, Nov 10, 2018 at 8:03 AM Pavel Afonine <pafonine(a)lbl.gov <mailto:[email protected]>> wrote: Hi Wen, I'm not sure I fully understand your question... You say a function that takes a numpy array.. Array of what? Then, "a list of diffraction spots" -- these are measured in diffraction experiment. If you could provide more details as to what you are trying to do as well as what exactly the inputs are then I will do my best to see how to do this in CCTBX or forward your questions to CCTBX mailing list so that others can comment. All the best, Pavel On 11/10/18 03:56, Wen Jiang wrote: > Hi Pavel, > I am looking for a function that takes a numpy array and returns a > list of diffraction spots and lattice vectors. I think > cctbx should have such a function but I am not familiar with it. > Can you point me in the right direction? > Thanks, > > Wen > > Prof. Wen Jiang > Department of Biological Sciences > Department of Chemistry (Courtesy) > Scientific Director, Purdue Cryo-EM Facility > Purdue University > Hockmeyer Hall of Structural Biology > 240 S. Martin Jischke Drive > West Lafayette, IN 47907 > http://jiang.bio.purdue.edu >

2 1