Edoardo Pasca
Edoardo Pasca
We discussed that the SuperBuild code could be copied into the VM at creation time, similarly to how it is done in Docker.
Hi @evenrose could you please share the whole error stack? It seems it's complaining that `name` is `None`, but we cannot see where it comes from. Thanks
Did you activate the conda environment where you installed CIL, before running @gfardell 's code?
I have avoided to add the `backend` into the geometry, because it is not really where it belongs. However when methods such as `allocate` is called, one needs to specify...
I'll test with MaGeZ as soon as I can.
I think our unit tests do not test for inplace algebric operation as `+=`. These should be added in the [DataContainerAlgebraTests](https://github.com/SyneRBI/SIRF/blob/0ba22c9b5d8b6c2f008e0b1e1846c059703a88c3/src/common/Utilities.py#L1032) class and then they'll run for all data container...
In CIL we started using `as_array` because only then we could have access to a numpy array for a number of tasks, such as regularisation. The consequences of the warning...
It's been years we've been using `as_array`.
Maybe the `dtype` problem is due to `numpy.take` https://github.com/TomographicImaging/CIL/blob/5d569dc054759a8c137ca72611fc7be07be6080e/Wrappers/Python/cil/framework/data_container.py#L179 However, according to numpy's docs for both [1.26](https://numpy.org/doc/1.26/reference/generated/numpy.take.html) and [2.0](https://numpy.org/doc/2.0/reference/generated/numpy.take.html) > the returned array has the same type as [the input]...
superseded by #1332