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.
Clean indexing
See discussion at https://i10git.cs.fau.de/hyteg/hog/-/merge_requests/33#note_34256. There are currently two issues with the indexing: - Indexing functions depend on the level and quantities like `num_microedges_per_edge`. It is the responsibility of the kernel wrapper to pass these in to the kernel function *if* needed. Also all these quantities can be derived from one another. Passing two or more, means they can be "out of sync". - The type annotations are wrong. I propose to pass the level and the width, i.e. the number of micro vertices per macro edge, and nothing else to the kernels. The width might not necessarily be $2^l+1$ if the coarsest grid has more than four vertices. Therefore, the indexing shall not use the level at all, everything must be computed from the width. The level number exists so that the kernel can use it to call into HyTeG functions which might need the level to access the right data.
issue