Closed alejands closed 8 months ago
You cannot use python
after sourcing CMSSW, that would create a mess, even if you can make it work. I think all we need to do is to find the setup.sh
script that works.
You cannot use
python
after sourcing CMSSW, that would create a mess, even if you can make it work.
Noted. Good to know.
While I couldn't find scripts for el8 easily, I was able to find a bunch for el9 by doing:
ls /cvmfs/sft.cern.ch/lcg/views/ / el9 *
Let's keep this in mind when the time comes. Also, we rarely run at lxplus. We use mostly KISTI and LPC.
No longer relevant after migrating to using the Python 3.8 inside CMSSW_11_3_4
.
See:
The current
setup_lcg.sh
andenv_lcg.sh
files are configured to use nodes running SL6 or CC7 operating systems.https://github.com/mcremone/decaf/blob/8e989f5b9b4d1f6e0f9f4077cabe28452c2ba6ca/env_lcg.sh#L1-L7
This works for the time being, as the default node on the LPC cluster still runs on SL7 (which appears to be compatible), however this may be soon become deprecated given that lxplus has switched it's default alias to EL9 as of December 7, 2023.
Currently the LPC offers SL7 and EL8 nodes, and likewise for their GPU nodes. Both scripts above are able to run on SL7 nodes with no issues, but on EL8 nodes the
python
executable no longer exists, onlypython3
which these scripts can't find.You can use
python
after sourcing a CMSSW environment withcmsenv
, but you run into a different error of the LCG files no longer being available on these nodes.I don't believe this is an immediate cause for concern and we should focus on the UL issues first, but I'm posting it as an issue so it doesn't slip our minds. This feels like it should be straightforward to update (fingers crossed 🤞).