Margaret Duff
Margaret Duff
Thanks @manchester-jhellier - I think this is complex, because for some algorithms e.g. PDHG we might not ever evaluate the individual functions on the current iterate during the update. However,...
Hey @manchester-jhellier - thank-you for this - it looks really interesting! A demonstration example could be something on the spheres data (which is small and *should* be quick to run)...
Thanks @manchester-jhellier!
Thanks @manchester-jhellier - This is something we have talked about a lot recently. Our sister package SIRF, does indeed have a save method for data containers. Definitely something we need...
We will investigate this but in the meantime we should at least change the warning
Discussed with developers today: - We would like to try a general wrapping of tigre algorithms e.g. tigre.algo( name, initial, image_geometry, data, niter, **kwargs) which then converts the geometry, data...
Discussed with developers: - We prefer option 2, it works with all current tigre algorithms and it is clearer that it is Tigre's algorithm and the credit goes to them...
@gfardell - I was having another think about this - we discussed writing the wrapper as a processor but to force the code to have an `init`, `set_input` and `get_output`...
Thanks @lauramurgatroyd - I am happy with those changes if it passes all the tests.
So in #1802 we changed BlockOperator direct (and adjoint) methods to return a DataContainer in the case it would previously return a (1,1) BlockDataContainer. We also changed the range (and...