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.
Revise and clearly define the treatment of field size/stride symbols
## Background Traditionally, the factory function `Field.create_generic` created each field with its own set of shape and stride symbols, and each of these symbols was exclusive to that field. Many parts of the code, the runtime environment, and integrations, built on top of this assumption being always valid. However, the *pystencils* frontend allows the creation of fields with arbitray shape and stride symbols, which do not even have to be annotated as such (see pycodegen/pystencils!408, where the specially-annotated frontend symbols were removed for exactly this reason). At the moment, the backend still implicitly requires that each field has its own exclusive set of indexing symbols (otherwise `KernelCreationContext.add_field` fails). However, the `Field` class exposes `new_field_with_different_name`, which duplicates a field while changing its name, but not its indexing symbols. So now two fields exist with the same set of indexing symbols, which the backend can't handle. Many problems therefore arise from the fact that indexing symbols enjoy special treatment in pystencils. ## Requirements Allow any symbol of appropriate integer type as an indexing symbol of a field. Only the following restrictions apply: - All indexing symbols of a field must have the same type. The backend must not handle the indexing symbols in any special way, except for checking the above restrictions. The backend must however annotate these symbols with information about their role as array extents and strides. This is a) to have additional information available to check the validity of transformations, and b) to provide that information in the interface of the final product `KernelFunction`, as the runtime system needs to know how to extract these symbols from the input arrays. Document the treatment and restrictions on field indexing symbols in the documentation pages. ## Ideas Remove the backend classes below `PsFieldAssocSymbol`, such that there is only `PsSymbol`. Instead, implement a system of properties that can be attached to `PsSymbol`s, such that any symbol may carry arbitrary additional information relevant to code generation. Create property objects for field shape and strides, and attach them to any symbols fulfilling such a role. Refactor the `KernelParameter` classes: Remove `FieldShapeParam`, `FieldStrideParam` but keep `FieldParameter`; allow one `FieldParameter` to be associated to multiple fields. Attach the shape and stride annotations from the symbol properties to the parameters in an appropriate way. Refactor the `legacy_cpu` and `gpu_cupy` JIT compilers to comply to the changes and introduce any required sanity checks if parameters fulfill multiple roles. Also refactor the code generator bridge of `waLBerla` and the extraction code in `pystencils-sfg` to comply to the changes.
issue