One of the major benefits of building SCICO on top of JAX is the ability to run the same code on CPU and GPU, but some SCICO functionality only works on a CPU. The relevant restrictions are currently not clearly indicated in either the API docs or the usage examples. All functions/classes that are CPU-only should be clearly indicated as such, and alternatives identified where available (e.g. astra-toolbox instead of svmbir).
bwohlberg
commented
2 years ago
One of the major benefits of building SCICO on top of JAX is the ability to run the same code on CPU and GPU, but some SCICO functionality only works on a CPU. The relevant restrictions are currently not clearly indicated in either the API docs or the usage examples. All functions/classes that are CPU-only should be clearly indicated as such, and alternatives identified where available (e.g.
astra-toolboxinstead ofsvmbir).