Oliver Schulz

I've added test timers to this PR (should be useful in general), let's see where all the time is spent.

Tests on Julia v1.9 keep failing with out-of-memory, not sure why (and why only when using multithreading). Docs failures should be fixed by #341.

> ubuntu x64 is still significantly slower than the rest.. Yes, massively - but I haven't the faintest intuition on why, it looks really strange.

How long does it run locally, on two core, x86-64, in comparison? Maybe the GitHub x86-64 runners are just in higher demand and more heavily oversubscribed?

I'd mostly want column-mode reading and writing, along the lines of ```julia using Tables, PropertyFunctions # Select columns of interest, e.g. using `PropertyFunctions.PropSelFunction` (we can support multiple ways to do...

> sounds like you want 2.b Yes, that would be my main way of using it. I assume for-loops with smart buffering will work anyway as well. And we can...

@fhagemann there are a bunch of errors "invalid local link/image: path pointing to a file outside of build directory in src/api.md" now with Documenter v1, not sure if Documenter has...

> I‘m a bit concerned about the fact that the docs now take longer than the tests Yes, that's no good. I just don't know why ...

@fhagemann can we add a short test for this to CI without adding to much testing time?

Hi @Padniuk , using "CdZnTe" should work - in principle. We do have it in https://github.com/JuliaPhysics/SolidStateDetectors.jl/blob/main/src/MaterialProperties/MaterialProperties.jl though I think it's not been carefully validated yet. And material-specific mobility values aren't...