There is a slight weirdness about the installation of Mathematica 12.3.0 on the baobab cluster that I would like to point out.
If I am not mistaken, every distribution of Mathematica comes with the binary called wolframscript. Indeed, if you check /unige/mathematica_11.1/bin you have the symlink wolframscript -> /unige/mathematica_11.1/SystemFiles/Kernel/Binaries/Linux-x86-64/wolframscript. It exists in v12.3.0 as well. However you do not have a symlink to wolframscript in /unige/mathematica_12.3/bin, even though /unige/mathematica_12.3/SystemFiles/Kernel/Binaries/Linux-x86-64/wolframscript exists as a fully functional binary.
Now when using ml load, only /unige/mathematica_12.3/bin gets added to PATH, and thus which wolframscript would give the error that it could not find it, and one needs to manually append PATH with the exact binary to be able to use wolframscript from v12.3.0.
The reason why I believe it is important to point this out is that I have noticed a few undocumented instabilities with wolframscript in v11.1.1, which seems to have been solved in v12.3.0, and thus if I specifically want to use v12.3.0, the only way is to first load 12.3.0 and then manually add the path to the binary in PATH, which is a perfectly functional but non-elegant solution.
