💬 In some cases software developers offer ready-made binary versions of their software.
☝🏻 It should be noted that ready binary versions are typically not optimized for CSC supercomputers.
‼️ Especially all MPI codes need to be compiled on the machine they will be run on to ensure correct operation.
/projappldirectory of your project
/projappldirectory of your project:
cd /projappl/<project> # replace <project> with your CSC project, e.g. project_2001234
mkdir -p $USER
💬 In this example we’ll install the binary release of the GCTA software.
command not founderror because you are not accessing the right folder yet.
cd gcta-1.94.1-linux-kernel-3-x86_64 ./gcta-1.94.1
💬 Instead of providing the full path in the command line, you can also add the application to your
./gcta-1.94.1-linux-kernel-3-x86_64if not there yet.
💡 When adding paths to
$PATH, always remember to append the current
$PATH, otherwise some of your normal shell commands etc. will stop working.
☝🏻 To add paths automatically, you can add the
export command to your
$HOME/.bashrc file. Instead of
$PWD, use the full path:
export PATH=/projappl/<project>/$USER/gcta-1.94.1-linux-kernel-3-x86_64:$PATH # replace <project> with your CSC project, e.g. project_2001234
‼️ If you make changes to your environment (e.g. edit
.bashrc), it is possible that there will be conflicts with applications pre-installed by CSC.
💭 If you encounter problems after modifying your environment, it is possible to restore it to the default state permanently or temporarily using the