Hannah Robarts

Hi Gemma, I can't think of any places where this would cause problems in Processors. There are some places where we add empty dimensions to the array for the processing...

I've made a simplified version of this with just the change to where dxchange and olefile are imported: https://github.com/TomographicImaging/CIL/pull/2149 We can look at updating the readers tests separately, possibly using...

Moved the environment files to a separate repo https://github.com/TomographicImaging/Build-scripts/pull/1] This PR just has checks for skimage before running tests

Tested skipping skimage using: - Cil_env - On linux: Ran 1003 tests in 115.496s OK (skipped=283) - skipped skimage and other stuff - On windows: Ran 1003 tests in 169.757s...

I looked at some different methods for random number generation 1. Previous method Using `numpy.random.seed()` and `numpy.random.random()` directly. Cons: doesn't let us choose the data type 2. Calling `numpy.random.Generator()` in...

> Thanks Hannah, just a quick few comments, mainly on the documentation. I think most comments relate to all three files - image, acquisition and vector geometry Thanks @MargaretDuff I...

Discussion in dev meeting - Use out=allocate(empty) then rng.random(out=out). To be decided: moving the random functionality to fill and just call fill from geometry.allocate? How do we want to handle...

After discussion with @MargaretDuff - Noticed we can currently use geometry.allocate with an array because it just passes whatever is in value to fill - Perhaps most logical usage would...

We could use the new cil_test_env.yml file in #2102 for testing with dxchange and olefile and remove them from the meta.yaml?

Environment files moved to https://github.com/TomographicImaging/Build-scripts/pull/1