Page History
...
Hi Mikhail,
As you requested, I believe I have a first-pass version of the “test release” idea working with the new-style psana1 (both py2 and py3). See below for an example py3 session. It isn’t rock-solid: the situation that is currently not as good as the old-style test release is that you can’t switch between different test release directories in one session ... you have to logout/login and redo the “conda_setup” below in the new test release directory. But given that only developers will see this (mostly you and me, maybe Chuck and Valerio) I think it’s a reasonable tradeoff: the scripts are much simpler if we don’t have to delete stuff from PATH, LD_LIBRARY_PATH, PYTHONPATH.
It’s a first-pass so there may be problems. Let me know if you see any.
chris
----------------------------------------------------------
creating a test release:
source /reg/g/psdm/sw/conda1/manage/bin/psconda.sh -py3
(potentially activate the right conda env if you don’t want the default)
mkdir mytestrel
cd mytestrel
source /reg/g/psdm/sw/conda1/manage/bin/conda_setup
git clone https://github.com/lcls-psana/psana
git clone https://github.com/lcls-psana/python
cd psana
git checkout py3
cd ..
scons
reusing an existing test release:
source /reg/g/psdm/sw/conda1/manage/bin/psconda.sh -py3
cd mytestrel
(potentially activate the right conda env if you don’t want the default, you can see which one is correct in the file .sit_conda_env: it will give you an error if you have it wrong)
source /reg/g/psdm/sw/conda1/manage/bin/conda_setup
scons
As you requested, I believe I have a first-pass version of the “test release” idea working with the new-style psana1 (both py2 and py3). See below for an example py3 session. It isn’t rock-solid: the situation that is currently not as good as the old-style test release is that you can’t switch between different test release directories in one session ... you have to logout/login and redo the “conda_setup” below in the new test release directory. But given that only developers will see this (mostly you and me, maybe Chuck and Valerio) I think it’s a reasonable tradeoff: the scripts are much simpler if we don’t have to delete stuff from PATH, LD_LIBRARY_PATH, PYTHONPATH.
It’s a first-pass so there may be problems. Let me know if you see any.
chris
----------------------------------------------------------
creating a test release:
source /reg/g/psdm/sw/conda1/manage/bin/psconda.sh -py3
(potentially activate the right conda env if you don’t want the default)
mkdir mytestrel
cd mytestrel
source /reg/g/psdm/sw/conda1/manage/bin/conda_setup
git clone https://github.com/lcls-psana/psana
git clone https://github.com/lcls-psana/python
cd psana
git checkout py3
cd ..
scons
reusing an existing test release:
source /reg/g/psdm/sw/conda1/manage/bin/psconda.sh -py3
cd mytestrel
(potentially activate the right conda env if you don’t want the default, you can see which one is correct in the file .sit_conda_env: it will give you an error if you have it wrong)
source /reg/g/psdm/sw/conda1/manage/bin/conda_setup
scons
New psana1 test release
O'Grady, Paul Christopher <cpo@slac.stanford.edu>Mon 12/14/2020 4:32 PM
Mariani, Valerio Dubrovin, Mikhail
Hi Mikhail,
If it helps I think I created a rough “test release” mechanism for new-style psana1. I think you create a testrel directory, checkout the appropriate packages with git then
source /cds/sw/ds/ana/conda1/manage/bin/setup_testrel
Do this only once. Then each time you login and want to activate the testrel you do:
source /cds/sw/ds/ana/conda1/manage/bin/activate_testrel
Then “scons” as usual. It may be I remember this incorrectly, however.
chris
Overview
Content Tools