Closed dkirkby closed 6 years ago
More recent releases work: 18.3, 18.6, 18.7.
Unfortunately NERSC removed a module that we previously required. In the past we have sometimes gotten them to re-instantiate a removed module, but this flavor of problem will always be an issue when working at NERSC where we don't control the upgrade path for core modules like gcc.
Suggestions welcome.
I didn't try those since I didn't see them listed in /global/common/cori/contrib/desi/desiconda/startup/modulefiles/desimodules/
.
That path is outdated. The standard DESI software path is now /global/common/software/desi/${NERSC_HOST}
.
Ah, that is an old and deprecated location. NERSC asked us to move here:
/global/common/software/desi/cori/desiconda/startup/modulefiles/desimodules/
. One dangling action item is to remove those old locations (with warnings and instructions for what people should do instead).
Cross post. My reply was in reference to @dkirkby not @weaverba137 . /global/common/software/desi/${NERSC_HOST}
is the new location as he noted.
Ok, thanks. The old locations are still used by /project/projectdirs/desi/software/desi_environment.sh
for 17.* and 18.1, but perhaps that's unnecessary since those releases exist under the new location?
Workaround to get 18.1 and prior, thanks to @rcthomas
module load pe_archive
source /project/projectdirs/desi/software/desi_environment.sh 18.1
@sbailey, should we close this with the existing workaround, or do we need to include this in the 18.9 version of desimodules?
We should not need this for 18.9. I think the workaround is ok for the old versions. If it keeps coming up, we could retroactively add "module load pe_archive" to the old module files, but let's not do that right now.
I just noticed that the following command fails:
All numbered releases (17.12, 17.9, ...) fail the same way, but the default (master) works.
Is this a transient problem or are others seeing the same thing?