|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Alien||2,833||3 days ago||6||gpl-3.0||C++|
|ALIEN is a CUDA-powered artificial life simulation program.|
|Fluidx3d||1,282||8 days ago||1||other||C++|
|The fastest and most memory efficient lattice Boltzmann CFD software, running on all GPUs via OpenCL.|
|Gpu Io||1,001||a day ago||1||mit||TypeScript|
|A GPU-accelerated computing library for physics simulations and other mathematical calculations|
|Picongpu||610||3 days ago||424||other||C++|
|Performance-Portable Particle-in-Cell Simulations for the Exascale Era :sparkles:|
|Stuntrally||509||a day ago||23||gpl-3.0||C++|
|Note: development continues in stuntrally3. 3D racing game based on VDrift and OGRE with own Track Editor. The main repository with Stunt Rally sources and data.|
|Gpu Physics Unity||313||4 years ago||C#|
|Through this configuration, no per voxel data is transferred between the GPU and the CPU at runtime.|
|Cartographer||250||2 years ago||1||apache-2.0||GDScript|
|A GPU powered Terrain editor and renderer for Godot Engine|
|Fusion||177||4 years ago||3||mit||C#|
|Unity Physics on GPU|
|Warpx||175||15 hours ago||24||November 03, 2022||375||other||C++|
|WarpX is an advanced, time-based electromagnetic & electrostatic Particle-In-Cell code.|
|Unity Verlet Simulator||135||4 years ago||1||mit||C#|
|Simple verlet integration simulator for Unity.|
PIConGPU is a fully relativistic, manycore, 3D3V particle-in-cell (PIC) code. The Particle-in-Cell algorithm is a central tool in plasma physics. It describes the dynamics of a plasma by computing the motion of electrons and ions in the plasma based on Maxwell's equations.
PIConGPU implements various numerical schemes to solve the PIC cycle. Its features for the electro-magnetic PIC algorithm include:
and the electro-magnetic PIC algorithm is further self-consistently coupled to:
Besides the electro-magnetic PIC algorithm and extensions to it, we developed a wide range of tools and diagnostics, e.g.:
As one of our supported compute platforms, GPUs provide a computational performance of several TFLOP/s at considerable lower invest and maintenance costs compared to multi CPU-based compute architectures of similar performance. The latest high-performance systems (TOP500) are enhanced by accelerator hardware that boost their peak performance up to the multi-PFLOP/s level. With its outstanding performance and scalability to more than 18'000 GPUs, PIConGPU was one of the finalists of the 2013 Gordon Bell Prize.
PIConGPU is developed and maintained by the Computational Radiation Physics Group at the Institute for Radiation Physics at HZDR in close collaboration with the Center for Information Services and High Performance Computing (ZIH) of the Technical University Dresden (TUD). We are a member of the Dresden GPU Center of Excellence that cooperates on a broad range of scientific GPU and manycore applications, workshops and teaching efforts.
PIConGPU is a scientific project. If you present and/or publish scientific results that used PIConGPU, you should set a reference to show your support.
Our according up-to-date publication at the time of your publication should be inquired from:
Please also consider adding yourself to our community map. We would love to hear from you!
The following slide should be part of oral presentations. It is intended to acknowledge the team maintaining PIConGPU and to support our community:
(coming soon) presentation_picongpu.pdf (svg version, key note version, png version: 1920x1080 and 1024x768)
PIConGPU is licensed under the GPLv3+. Furthermore, you can develop your own particle-mesh algorithms based on our general library PMacc that is shipped alongside PIConGPU. PMacc is dual licensed under both the GPLv3+ and LGPLv3+. For a detailed description, please refer to LICENSE.md
See our notes in INSTALL.rst.
Dear User, please be aware that this is an open beta release! We hereby emphasize that we are still actively developing PIConGPU at great speed and do, from time to time, break backwards compatibility.
When using this software, please stick to the
master branch containing the
latest stable release. It also contains a file
CHANGELOG.md with the
latest changes (and how to update your simulations). Read it first before
updating between two versions! Also, we add a git
tag according to a version
number for each release in
For any questions regarding the usage of PIConGPU please do not contact the developers and maintainers directly.
Instead, please sign up to our PIConGPU-Users mailing list so we can distribute and archive user questions: Subscribe (select "Feed" on bottom left).
Before you post a question, browse the PIConGPU documentation, wiki, issue tracker and the mailing list history to see if your question has been answered, already.
PIConGPU is a collaborative project. We thus encourage users to engage in answering questions of other users and post solutions to problems to the list. A problem you have encountered might be the future problem of another user.
In addition, please consider using the collaborative features of GitHub if you have questions or comments on code or documentation. This will allow other users to see the piece of code or documentation you are referring to.
Main ressources are in our online manual, the user section of our wiki, documentation files in
.md (Markdown) and
.rst (reStructuredText) format in this repository and a getting started video.
Feel free to visit picongpu.hzdr.de to learn more about the PIC algorithm.
PIConGPU follows a
master - dev
development model. That means our latest stable release is shipped in a branch
master while new and frequent changes to the code are incooporated
in the development branch
Every time we update the master branch, we publish a new release
of PIConGPU. Before you pull the changes in, please read our
You may have to update some of your simulation
.cfg files by
hand since PIConGPU is an active project and new features often require changes
in input files. Additionally, a full description of new features and fixed bugs
in comparison to the previous release is provided in that file.
In case you decide to use new, potentially buggy and experimental features
dev branch, be aware that support is very limited and you must
participate or at least follow the development yourself. Syntax changes
and in-development bugs will not be announced outside of their according pull
requests and issues.
Before drafting a new release, we open a new
release-* branch from
* being the version number of the upcoming release. This branch only
receives bug fixes (feature freeze) and users are welcome to try it out
(however, the change log and a detailed announcement might still be missing in
If you like to jump in right away, see
The PIConGPU Team expresses its gratitude to:
Florian Berninger, Heiko Burau, Robert Dietrich, Carlchristian Eckert, Wen Fu, Ph.D., Alexander Grund, Sebastian Hahn, Anton Helm, Wolfgang Hoehnig, Dr.-Ing. Guido Juckeland, Jeffrey Kelling, Maximilian Knespel, Dr. Remi Lehe, Felix Schmitt, Frank Winkler, Benjamin Schneider, Joseph Schuchart, Conrad Schumann, Stefan Tietze, Marija Vranic, Ph.D., Benjamin Worpitz, Erik Zenker, Sophie Rudat, Sebastian Starke, Alexander Matthes, Kseniia Bastrakova, Brian Edward Marre, Bernhard Manfred Gruber, Jakob Trojok, Anton Lebedev, Felix Meyer, Lennert Sprenger, Manhui Wang, Maxence Thevenet, Ilja Goethel and Finn-Ole Carstens.
Kudos to everyone, mentioned or unmentioned, who contributed further in any way!