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
The management of stacks and channels needs to be restructured.
The following requirements should be fulfilled:
Dynamic channel loading/unloading without restarting the application. It would be a huge improvement for the user experience if the results of segmentation or background correction were loaded on the fly without having to restart the application and reload all data.
Memory efficiency: use memmaps or virtual channels where possible. Image stacks are large files; holding them in memory and performing image processing (e.g. background correction) can be too much even for recent workstation machines.
Class hierarchy / API: Provide reasonable base classes for stacks/channels, including an elaborate API, for easy subclassing (e.g. to implement new file format readers).
The text was updated successfully, but these errors were encountered:
A starting point could be the BaseStack class from src/stack/base.py in b3459af.
It is intended to provide all API methods used in the application. Actual data should be kept by subclasses thereof. There should be a subclass for image data held in memory as a numpy array and a subclass for image data held on disk in a numpy memmap. Image loaders should create one of these classes, depending on available memory. For image file formats that can well be used as memmap for reading on the fly, specific subclasses of BaseStack may be created.
The management of stacks and channels needs to be restructured.
The following requirements should be fulfilled:
The text was updated successfully, but these errors were encountered: