This repo contains source code and descriptions for the examples and exercises that will be explained during the PACS (Programmazione Avanzata per il Calcolo Scientifico - Advanced Programming for Scientific Computing) and Advanced Methods for Scientific Computing (AMSC) courses at Politecnico di Milano. For the AMSC course, only a subset of the examples will be used at the lectures and labs. I encourage interested students to look at the various examples.
Essential note: The examples are located in the AMSC branch, which has been designated as the main branch, not in the master branch.
You can create other branches for your experiments, if you want, but do not mess around with the master branch
The repository contains git submodules, so to check it out properly, you have to type
git clone --recursive https://github.com/HPC-Courses/AMSC-CodeExamples.git
or (preferably)
git clone --recursive git@github.com:HPC-Courses/AMSC-CodeExamples.git
In the latter case, you must register your ssh keys on a personal GitHub account.
To keep your local repo updated with changes upstream do frequently
git pull --recurse-submodulesor just from this directory,
./update.shThe software requires a C++ compiler, i.e., gcc >= 8.0 or clang >= 8. You may check the version of your compiler with the option -v. Several examples have now been ported to c++17 and some examples of c++20 are being added. Check whether your compile supports those standards. You may have a look here
In the course, we use the mk module system provided in this repository (nothing to do with girt submodules!). However, this is not strictly required, you can do without, if you have a recent Linux distribution.
You may want to use some IDE. Either eclipse, CLion or VisualStudio. Clion and VisualStudio allow integration with Copilot. Visual studio allows also integration with dev containers
This directory contains some utilities:
load_modules If you use the module (mk) system, by typing
source load_modulesor
. load_modules.shwill load the main modules used in the examples, apart from hdf5, which is used only in the example on input-output streams. If you do not use module youu do not need it.
change_submodules_url.sh This script changes the protocol of the submodules to https. You may need it if you use containers (see later on)
change_submodules_url_ssh.sh This script changes the protocol of the submodules to ssh. SSSh protocol is the default for the submodules. You may need this utilityit if you use containers (see later on)
If you do not have used --recursive when cloning this repo and you want to use
the git submodules containing third-party software type:
./install_git_submodules.shThe file submodule_commands.txt contains some reminders of useful git commands for operating with submodules
-
change_submodules_url.shchanges the protocol of the submodules to https. You should not need it! -
change_submodules_url_ssh.shchanges the protocol of the submodules to ssh. You should not need it!
- Go to the
Extras/directory, which contains additional software used by some examples and follow the instructions in the localREADME.mdfile. - Go to the
Examples/directory and follow the instructions in the localREADME.mdfile.
If you want the repository of the laboratories of the course, you can clone this repo
I have used standard makefiles since I find that they allow simpler handling of "disaggregated software", where you have several partially independent examples which share, however, some common features. Indeed porting to cmake is possible, but so far it is not planned.
The code in this repository is just a collection of examples. Some of them are rather complete and may form the basis of derivative work. You are free to use them at your wish (give credits please), but remember that I do not make any claim on their suitability for your work, nor that they are free of bugs.
The code in this repository is just a collection of examples. Some of them are rather complete and may form the basis of derivative work. You are free to use them at your wish (give credits please and let me know of bugs or possible improvements), but remember that I do not make any claim on their suitability for your work, nor that they are free of bugs.
Luca Formaggia (github username: lformaggia)