# High Performance Scientific Computing in C++ 2024
# High-performance scientific computing in C++ 2024
Course material for the PRACE Advanced Training Course
"High-performance scientific computing in C++",
28 -- 31 October 2024 organized by the Jülich Supercomputing Centre,
Forschungszentrum Jülich, Germany.
# hpcxx2024
## Getting started
You will need to pull from this repository periodically during this course.
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
If your computer does not have "git", you will need to use the download
button to the left of the "Clone" button in the gitlab page.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Recommended way of working with this material
## Add your files
The downloaded or cloned material from this repository will be updated
during the course days. You should keep one copy of the examples and
exercises in the pristine form, and work on your own duplicates.
For example, to work on the day1 examples, do as follows:
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
```bash
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
Only examples (which includes some exercises) and solutions need to
be duplicated. You don't need two copies of the entire material as that
-[ ] [Set up project integrations](https://gitlab.jsc.fz-juelich.de/sdlbio-courses/hpcxx2024/-/settings/integrations)
includes the PDFs of the book, course slides and other utillities.
## Collaborate with your team
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
## Testing your set up
# Editing this README
To work with this material, you will need to have a fairly up-to-date
C++ compiler. GCC version 13.3 or Clang version 18.1 or later are
recommended.
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
Microsoft's Visual C++ compiler has excellent support for C++23, if
you have the latest version installed. During the course, we will focus
on using open source tools, which are available to everyone, rather
than proprietary tools.
## Suggestions for a good README
To test your setup, proceed as follows:
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
```bash
cd wherever_you_downloaded_or_cloned_this_thing
## Name
cd test_your_setup
Choose a self-explaining name for your project.
g++ hello.cc -o hello.gcc
./hello.gcc
## Description
clang++ hello.cc -o hello.clang
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
./hello.clang
g++ -std=c++23 hello_c++23.cc -o hello_cxx23.gcc
## Badges
./hello_cxx23.gcc
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
And finally to test if your compiler can at least partially
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
handle C++20 modules, try the two remaining examples:
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
As the above examples show, we will often need to type a
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
lot of options to compile our programs during this course,
since we want to use C++23, which is not the default
standard for the compilers yet. A few convenient aliases
have been prepared which you can use to shorten the
above compilation steps. To use them, do as follows:
## Roadmap
```bash
If you have ideas for releases in the future, it is a good idea to list them in the README.
source course_material_dir/code/bash/aliases.sh
```
## Contributing
Once you have done that, you can shorten the above
State if you are open to contributions and what your requirements are for accepting them.
steps to the following:
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
```bash
C hello.cc
C hello_c++23.cc
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Cm hello_m.cc
Cm hello_c++23_m.cc
## Authors and acknowledgment
Gh iostream
Show your appreciation to those who have contributed to the project.
Gh concepts
Gm hello_m.cc
Gm hello_c++23_m.cc
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
