GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
author={S. Schwarz and T. Kempe and J. Fr{\"o}hlich},
}
@inproceedings{bauer2019code,
title={Code generation for massively parallel phase-field simulations},
author={Bauer, Martin and H{\"o}tzer, Johannes and Ernst, Dominik and Hammer, Julian and Seiz, Marco and Hierl, Henrik and H{\"o}nig, Jan and K{\"o}stler, Harald and Wellein, Gerhard and Nestler, Britta and others},
booktitle={Proceedings of the International Conference for High Performance Computing, Networking, Storage and Analysis},
pages={1--32},
year={2019},
doi={10.1145/3295500.3356186}
}
@article{bauer2020walberla,
title={waLBerla: A block-structured high-performance framework for multiphysics simulations},
author={Bauer, Martin and Eibl, Sebastian and Godenschwager, Christian and Kohl, Nils and Kuron, Michael and Rettinger, Christoph and Schornbaum, Florian and Schwarzmeier, Christoph and Th{\"o}nnes, Dominik and K{\"o}stler, Harald and others},
journal={Computers \& Mathematics with Applications},
year={2020},
publisher={Elsevier},
doi={10.1016/j.camwa.2020.01.007}
}
@article{bauer2020lbmpy,
title={lbmpy: A flexible code generation toolkit for highly efficient lattice Boltzmann simulations},
author={Bauer, Martin and K{\"o}stler, Harald and R{\"u}de, Ulrich},