Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
Staggered kernel optimizations ignore range checks
In the 1.3 line, function `remove_conditionals_in_staggered_kernel()` elides range check conditionals and stores values from the grid into local variables. This leads to out-of-bonds accesses to initialize variables that are unused. With `-O3` the compiler eliminates these unused variables, but in debug builds with `-O0` these variables are preserved and lead to segmentation faults. This only affects CPU kernels, GPU kernels don't apply this optimization. Commit [jngrad/pystencils@`dfd203a3`](https://i10git.cs.fau.de/jngrad/pystencils/-/commit/dfd203a3f6318f5fb4cfa09f9f8c12bb45463bd7) from branch `staggered` proposes a stop-gap solution to give users an opportunity to not apply the optimization. I don't really like how an element from a dict passed by reference is popped, because this mutates the user-provided parameter dict, and don't think this is in a state suitable for a merge. I would argue for the removal of the optimization because it looks unsafe to me, but then the testsuite would have to be adapted accordingly. Unfortunately, I'm currently in a coding sprint to release the next major ESPResSo version, and cannot spend more time on this issue. We have adapted our workflows to pip install pystencils from the `staggered` branch, so this issue no longer affects us. Considering that many resources are now allocated to the 2.0 line where this optimization was removed, it is also debatable whether it's still worth pursuing a bugfix for the 1.3.7 version. This bug report is for future reference and can be closed at your earliest convenience.
issue