# Installing stack 12.1 with conda **URL:** \ **Category:** Support\ **Tags:** stack-install\ **Created:** [December 13, 2016, 7:03pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485 "2016-12-13T19:03:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mbl](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mbl](https://www.rubin.community/u/mbl)\ **Post date:** [December 13, 2016, 7:03pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/1 "2016-12-13T19:03:31Z")
Hello, I want to install pipeline of version 12.1 with conda, and have just tried the channel [http://conda.lsst.codes/stack](http://conda.lsst.codes/stack) It seems that the conda packages have been upgraded to 12.1 version. I have deleted all my 12.0 packages and re-install v12.1, but a lot of packages were enabled by conda with the following message: ```auto Package http://conda.lsst.codes/stack::lsst-meas-extensions-psfex-0.12.1.post1-0 uses a pre-link script. Pre-link scripts are potentially dangerous discouraged. ``` I’d be grateful if you can help me with this. In addition, I was wondering if the demo test (which currently is still compatible with v12.0) will work for v12.1? Thank you ---
**Author:** ![jmatt](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jmatt/32/96_2.png) [@jmatt](https://www.rubin.community/u/jmatt)\ **Post date:** [December 13, 2016, 7:50pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/2 "2016-12-13T19:50:45Z")
Hi mbl, Thanks for bringing this up. The pre-link script is there to ensure eups is configured correctly before installing. At this time we don’t have a work around to avoid this warning message. It should not affect your Conda environment other than configuring LSST’s Conda install of eups. The previous DM stack Conda binaries are still available in version specific Conda channels. Here is the v12.0 channel: [http://conda.lsst.codes/stack/0.12.0](http://conda.lsst.codes/stack/0.12.0). These old channels are not actively maintained but are still publicly available. So there may be issues. I’d recommend using a single Conda channel and environment at a time. This will avoid problems mixing incompatible packages from different LSST Conda binary releases. The demo does change based on the current release. Similar to other binary artifacts older demos are still available but need to be specified. The 12.0 demo is available from git here: [https://github.com/lsst/lsst\_dm\_stack\_demo/tree/12.0](https://github.com/lsst/lsst_dm_stack_demo/tree/12.0) or archived here: [https://github.com/lsst/lsst\_dm\_stack\_demo/archive/12.0.tar.gz](https://github.com/lsst/lsst_dm_stack_demo/archive/12.0.tar.gz). ---
**Author:** ![FabioHernandez](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/fabiohernandez/32/82_2.png) [@FabioHernandez](https://www.rubin.community/u/FabioHernandez)\ **Post date:** [December 14, 2016, 6:17am UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/3 "2016-12-14T06:17:02Z")
> [@mbl](#): > > I was wondering if the demo test (which currently is still compatible with v12.0) will work for v12.1? My attention was drawn recently to the fact that the v12.0 demo, that is, the one available at ```auto https://github.com/lsst/lsst_dm_stack_demo/archive/12.0.tar.gz ``` does not fully work when you run it using v12.1 software, at least not when the stack is installed from source via `newinstall.sh` as I do. There seems to be an issue in the verification phase. Here is what I get: ```auto $ ./bin/demo.sh this produces the usual messages $ ./bin/compare detected-sources.txt Traceback (most recent call last): File "./bin/compare", line 176, in if compareWithNumPy(args.filename, args.reference, args.tolerance): File "./bin/compare", line 104, in compareWithNumPy table1, table2 = get_array(filename), get_array(reference) File "./bin/compare", line 51, in get_array array = np.loadtxt(f, dtype=DTYPE) File "/cvmfs/lsst.in2p3.fr/software/linux-x86_64/lsst-v12.1/Linux64/miniconda2/3.19.0.lsst4/lib/python2.7/site-packages/numpy/lib/npyio.py", line 928, in loadtxt items = [conv(val) for (conv, val) in zip(converters, vals)] File "/cvmfs/lsst.in2p3.fr/software/linux-x86_64/lsst-v12.1/Linux64/miniconda2/3.19.0.lsst4/lib/python2.7/site-packages/numpy/lib/npyio.py", line 658, in floatconv return float.fromhex(asstr(x)) ValueError: invalid hexadecimal floating-point string ``` I have not tried against a v12.1 stack installed via conda, but I would be surprised if the demo fully worked. The v12.1 demo, available at ```auto https://github.com/lsst/lsst_dm_stack_demo/archive/12.1.tar.gz ``` does work against the v12.1 stack. ---
**Author:** ![jbosch](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jbosch/32/12_2.png) [@jbosch](https://www.rubin.community/u/jbosch)\ **Post date:** [December 14, 2016, 3:12pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/4 "2016-12-14T15:12:05Z")
In general, we do not expect that a demo from one release will work with code from another. The demo package includes comparison scripts and “expected output” files that we use to guard against unexpected changes in the outputs of the pipeline, but small expected changes are quite frequent, and those involve changes to the demo package. ---
**Author:** ![mbl](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mbl](https://www.rubin.community/u/mbl)\ **Post date:** [December 14, 2016, 6:32pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/5 "2016-12-14T18:32:10Z")
Thank you. Now the issue has been fixed now. ---
**Author:** ![mbl](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mbl](https://www.rubin.community/u/mbl)\ **Post date:** [December 14, 2016, 6:34pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/6 "2016-12-14T18:34:08Z")
I was also wondering if obs\_base was included with stack 12.1. I now have stack 12.1 installed but I am unable to find obs\_base. I need it to setup/declare for instance, obs\_decam. I believe it was something included in v12.0 though. ---
**Author:** ![swinbank](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/swinbank/32/24_2.png) [@swinbank](https://www.rubin.community/u/swinbank)\ **Post date:** [December 14, 2016, 7:22pm UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/7 "2016-12-14T19:22:30Z")
Unfortunately, the creation of obs\_base post-dates the 12.1 release. You can see the complete contents of 12.1 here: [https://sw.lsstcorp.org/eupspkg/tags/v12\_1\_2.list](https://sw.lsstcorp.org/eupspkg/tags/v12_1_2.list) (sorry, I’m not aware of a nicer online interface to that information). obs\_base was originally created by [renaming daf\_butlerUtils](https://jira.lsstcorp.org/browse/DM-7915), which was in 12.1. However, I don’t think you can expect a modern obs\_decam to work with the 12.1 vintage daf\_butlerUtils. Your best bet is probably to use an older version of obs\_decam in conjunction with the 12.1 stack release. I’m guessing that [2818ce61](https://github.com/lsst/obs_decam/tree/2818ce61a87075e937ba1918d6002a0af911b588) might work, but I haven’t confirmed it. The good news is that this should become a lot less painful for the next release, which will include a version of obs\_decam ([DM-8256](https://jira.lsstcorp.org/browse/DM-8256)). ---
**Author:** ![ctslater](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ctslater/32/28_2.png) [@ctslater](https://www.rubin.community/u/ctslater)\ **Post date:** [December 15, 2016, 2:44am UTC](https://www.rubin.community/t/installing-stack-12-1-with-conda/1485/8 "2016-12-15T02:44:28Z")
obs\_decam has a version tagged as 12.1, which will work with the 12.1 stack. If you check out that tag it will know to use daf\_butlerUtils and not obs\_base.