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.
Refactor codegen and JIT frontend modules
This issue lays out an ongoing plan to refactor the layout and API exposure of the code generation and JIT frontend. ## Codegen Frontend: `pystencils.codegen` Module All code generation-related user-facing APIs shall be consolidated into a new `pystencils.codegen` module. This includes `target`, `config`, `kernelcreation`, `kernelfunction`, and symbol properties. ## JIT Module All JIT-related functionality shall be consolidated in the new `pystencils.jit` module. This module shall in the future be home to a newly implemented, object-oriented JIT compiler for CPU targets. ## Code Generator Configuration The code generator configuration system shall be refactored along the same lines as in pycodegen/pystencils-sfg!2. The various options and option groups shall be cleaned up. All options shall be implemented using the Option descriptor, including proper validation. Incremental configuration shall become the standard, since it is more concise, more flexible, and requires fewer imports: ```Python cfg = ps.make_config() cfg.target = ps.Target.X86_AVX512 cfg.cpu.openmp.enable = True cfg.cpu.vectorize = "auto" ``` This was previously not reliably possible since all validation took place in `__post_init__`, and options set incrementally at a later point were never validated.
issue