Hi DC1ers, So we're whipping up a development environment as we go. Robyn desired a place to install python code for testing, and after trading some emails and phone calls, I think we have a procedure for handling this. Your comments are welcome.
First, I mentioned that in my previous email about sourcing a file to load the lsst environment; THE NAME OF THAT FILE HAS CHANGED. Please, now load the environment by either typing source /usr/projects/LSST/DC1/setlsst.csh or . /usr/projects/LSST/DC1/setlsst.sh depending on your preference. LSST_HOME is being set to /usr/projects/LSST/DC1 (actually you'll see a slightly different path on lsstarchive); however, we probably don't want to put code there for debugging purposes. Rather, it would be better to use a sandbox for this purpose. So, I've set up some support this in the enviroment setup scripts. So before you source the setlsst.csh file, you can set the LSST_DEVEL environment variable to your development directory. The setlsst file will then update you command path and PYTHONPATH to include this development area. You can then run "makesandbox" which will create some directories that our installers will need. Meanwhile, Russell is working on taking advantage of this in our python module setup.py file(s) so that you can install new modules into your development area. Python modules will be installed into lib/python. Is this going to work? cheers, Ray _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
