# Error encountered meas\_base using -t sims (sims\_2\_3\_1) **URL:** \ **Category:** Support\ **Created:** [October 1, 2016, 12:20am UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203 "2016-10-01T00:20:09Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![heather999](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@heather999](https://www.rubin.community/u/heather999)\ **Post date:** [October 1, 2016, 12:20am UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/1 "2016-10-01T00:20:09Z")
Hi, I’m working to support upcoming DESC Twinkles runs (at SLAC) with an updated DMstack installation (lsst\_apps and lsst\_sims). This is using a RH6 machine with gcc 4.9.2. We required a new tag of lsst\_sims, and @danielsf kindly set us up last night. I started from scratch and decided to do a “eups distrib install lsst\_apps -t sims --nolocks” It went along happily for quite awhile, but ended here: ``` [58/70] meas_base 12.1+3 ... ***** error: from /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/build.log: tests/testApertureFlux.py tests/testMeasureSources.py tests/testSincPhotSums.py tests/testScaledApertureFlux.py The following tests failed: /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testClassification.py.failed /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testJacobian.py.failed /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testApertureFlux.py.failed /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testMeasureSources.py.failed /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testSincPhotSums.py.failed /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/meas_base-12.1+3/tests/.tests/testScaledApertureFlux.py.failed 6 tests failed scons: *** [checkTestStatus] Error 1 scons: building terminated because of errors. + exit -4 eups distrib: Failed to build meas_base-12.1+3.eupspkg: Command: source /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/eups/bin/setups.sh; export EUPS_PATH=/nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40; (/nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/build.sh) >> /nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/build.log 2>&1 4>/nfs/farm/g/lsst/u1/software/redhat6-x86_64-64bit-gcc44/DMstack/w.2016.40/EupsBuildDir/Linux64/meas_base-12.1+3/build.msg exited with code 252 ``` Any suggestions or known recent issues with meas\_base? Thanks, Heather ---
**Author:** ![timj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/timj/32/10_2.png) [@timj](https://www.rubin.community/u/timj)\ **Post date:** [October 1, 2016, 12:32am UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/2 "2016-10-01T00:32:33Z")
> [@heather999](#): > > The following tests failed The fact that the lines above this one indicate no test output suggest that the tests are crashing straight away. Can you confirm that the listed `.failed` files contain no useful output? You might have to go into the `meas_base` build directory, set it up and run the tests manually. ---
**Author:** ![heather999](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@heather999](https://www.rubin.community/u/heather999)\ **Post date:** [October 1, 2016, 12:50am UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/3 "2016-10-01T00:50:46Z")
Thanks, @timj. Yes, sadly the \*.failed files are all empty. I might need some guidance on how to setup meas\_build so I can run the tests manually… I’m poking around the [build.sh](http://build.sh) script. ---
**Author:** ![price](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/price/32/488_2.png) [@price](https://www.rubin.community/u/price)\ **Post date:** [October 1, 2016, 8:06pm UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/4 "2016-10-01T20:06:03Z")
``` git clone git@github.com:LSST/meas_base.git cd meas_base setup -r . scons ``` ---
**Author:** ![heather999](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@heather999](https://www.rubin.community/u/heather999)\ **Post date:** [October 6, 2016, 2:55pm UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/5 "2016-10-06T14:55:30Z")
and just to close out this issue… I realized I was using an older python installation 🙂 Once I fixed that, I have no longer encountered any problems with meas\_base. Sorry for the trouble. ---
**Author:** ![timj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/timj/32/10_2.png) [@timj](https://www.rubin.community/u/timj)\ **Post date:** [October 6, 2016, 3:35pm UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/6 "2016-10-06T15:35:25Z")
Thanks. `newinstall.sh` is meant to check your python version and the EUPS `python` package is also meant to check. Did you somehow switch the python in your path between doing the install of the EUPS `python` validation package and the rest of the `eups distrib install`? ---
**Author:** ![heather999](https://avatars.discourse-cdn.com/v4/letter/h/f4b2a3/32.png) [@heather999](https://www.rubin.community/u/heather999)\ **Post date:** [October 6, 2016, 4:13pm UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/7 "2016-10-06T16:13:21Z")
No, there was no change in the version of python during the installation process. This was an older anaconda installation (2.5.0) - one I probably updated a few times, but python itself was at 2.7.11. I am still a little surprised it caused trouble, but once I saw that I could do a full install just fine when using the vanilla python that newinstall offered, I was left to assume my trouble was due to my python installation. Attempting to re-run the unit tests by hand, I got as far as receiving a “Segmentation fault” with little else to go on, short of debugging, Then I realized I was pointing to a python install that I had not intended to use. Once I fixed that and re-installed, things went just fine. ---
**Author:** ![ljones](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ljones/32/1804_2.png) [@ljones](https://www.rubin.community/u/ljones)\ **Post date:** [October 21, 2016, 4:53am UTC](https://www.rubin.community/t/error-encountered-meas-base-using-t-sims-sims-2-3-1/1203/8 "2016-10-21T04:53:23Z")
I realize this is old, but for the record, an anaconda install on Linux with numpy /scipy etc installed without no-mkl produces this exact error from meas\_base (at least in the v12 version of meas\_base). The miniconda install from LSST uses the no-mkl versions so would not produce the segfault errors.