Hello Jack, all,
> a notification from Intel for a new MPI release.
> The immediate question that arose was "oh shit, now WTF do
> I call a toolchain with this change?".
I can tell you what I do:
In effect, I assume I can baptize toolchains for my own private use and then
issue a PR on github.
At that moment, it becomes Kenneth's problem (boegel on github), since he is
the release manager.
It would be great to setup a (community-helpful) rule that new toolchains get a
"naming advice"
within 48 hours. That helps to remove unnecessary load to the submittor.
(I've been there: you may have to rename 100s of easyconfigs as a consequence,
if not so)
Also, this would have the nice incentive that people now have a cause to *share
early* their toolchains. Your take?
> But that was never clear and I'm glad that EB
> has moved toward a YEARrelease numbering scheme.
It is great to have it, however it's not panacea for all use(r)s
(esp. with current usual assumption of including latest and greatest).
> Also entwined in the issue is the preferred GCC. At present,
> as I see it, there are three releases that should be supported:
You pretty much described it right about 4.8/4.9/5.x, I and some others share
that view.
> goolf-1.7.20 - GCC-484/OpenMPI-184/OpenBLAS-0213/FFTW-334/ScaLAPACK-202
IMHO, as of today, the above is the best vehicle for bio* codes and related
paraphernalia.
> intel-2015B - GCC-484/iccifort-2015.3.187/impi-5.0.3.048/imkl-11.2.3.187
The alternative capitalization signifies move conservative choices? in fact,
this direction is interesting!
> Of course, with Intel's new MPI this morning, I need something new.
> And the intro of gcc 5 just adds to the chaos.
You'll eventually get used to this chaos :)
> xyzzy-20150708
That's why EB is there: you can *make* and *share* xyzzy today.
> I don't have a solution. Wish I did. I'm still trying to figure out
easybuild+git PRs are your friends; that's where it goes.
If you can share bits and pieces before they become mature PRs, that also helps.
> what to call a toolchain with GCC/MPICH2/OpenBLAS/FFTW/ScaLAPACK
> for use on the BG/Q (its partial to MPICH2).
gmolf, perhaps?
Remember, names are mostly there to help the human; For EB itself, it only
matters then how the --try-toolchain, --try-software-version options function.
> Keep up the good work and I promise at least three pints
Watch out, participation will go up with these offers ;-)
cheers,
F.
--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
| sed 's/better bash/bash better/' # Yelling in a CERN forum
