You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A useful feature to implement would be allowing users to simulate a batch of images simultaneously.
In my view, the user will have to pass a list of' Samples' to the Simulation class. Then, using the same simulation settings (e.g., parameters, optical config, detector, ..., otherwise things would become way more involved), the simulation will be performed at the same time for the entire batch.
This feature would become extremely handy in case the user would need to simulate multiple images. Indeed, the current solution is to simulate images iteratively, which is quite inefficient (although some things like the PSF are cached). At the same time, from a preliminary check, implementation appears to be rather straightforward.
@tlambert03 please let me know your take on this. I will make a draft PR with a few comments pointing to the parts of the code that will need to be changed in case we decide to proceed. Moreover, if you agree, I am happy to try to implement this!
The text was updated successfully, but these errors were encountered:
Do you suggest calling the new axis B (as batch) or S (as sample)? Personally, I'd say S is more appropriate. B is, I guess, more the Deep Learning way ...
A useful feature to implement would be allowing users to simulate a batch of images simultaneously.
In my view, the user will have to pass a list of' Samples' to the
Simulation
class. Then, using the same simulation settings (e.g., parameters, optical config, detector, ..., otherwise things would become way more involved), the simulation will be performed at the same time for the entire batch.This feature would become extremely handy in case the user would need to simulate multiple images. Indeed, the current solution is to simulate images iteratively, which is quite inefficient (although some things like the PSF are cached). At the same time, from a preliminary check, implementation appears to be rather straightforward.
@tlambert03 please let me know your take on this. I will make a draft PR with a few comments pointing to the parts of the code that will need to be changed in case we decide to proceed. Moreover, if you agree, I am happy to try to implement this!
The text was updated successfully, but these errors were encountered: