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.
Field class should remember its entire memory layout
Currently, the `Field` class only remembers the order of its spatial dimensions in its `layout` property, but forgets about its index dimensions. As a consequence, whether a field was created with `fzyx` or `zyxf` layout specification cannot be determined later on. This should be fixed, since the order of all dimensions can be crucial information for a runtime system. ## Proposition - Deprecate and later remove the `layout` property (it has always had a misleading name). - Introduce something like a `spatial_axes_order` with the same semantics, meaning it holds the iteration order of the spatial dimensions. The `spatial_axes_order` can translate directly to the loop order (for CPU) or thread index translation order (for GPU). - In addition, introduce the more general `axes_order` property which describes the linearization order of all dimensions, spatial and index. This information is required when inferring and checking mappings of fields onto array data structures, such as `std::mdspan` in `pystencils-sfg`, or waLBerla fields.
issue