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.
Vectorization warning issues
There seem to be some vectorization issues. First, we have a very simple 1D-Kernel [example.py](/uploads/b0bf171fcabe7894ba8c38cb6f526436/test.py), which should not have any issues. And yet I receive the warning: ``` pystencils/cpu/vectorization.py:127: UserWarning: Could not vectorize loop because of non-consecutive memory access warnings.warn("Could not vectorize loop because of non-consecutive memory access") ``` The second [example2.py](/uploads/92f7f12c046dc87449b910262861ff7e/test1.py) has the field `y` on both lhs and rhs side of the assignment. However, the stencil-access pattern is the same und thus now non-consecutive memory access should be present. Yet I receive the warning. The third [example3.py](/uploads/92a997c2a76293d8742dc65cb8903d68/test2.py) has non-consecutive memory access and the warning is correct. It is possible that I misunderstood something with the vectoriziation.
issue