When loading a virtual Image remotely from the N5 plugin there is not status as to how long it's loading will take. When read in a virtual stack each chunk is read from the S3 endpoint that is required for the current slice, and if it reads more data than required it will, buffering the read slice.
The order of slice presentation is as follows:
User navigates to new slice
ImageJ ask the ImagePlus class to pull up this slice
Cached Cell Image asks its reader for the next grid (chunk) available that can surmount to a slice
The N5S3Reader uses the S3 API to stream the chunks that would be appropriate for that slice into memory
So the key moment to help display a progress bar would be in the S3 API, where the number of bytes read compared to total bytes needed can be compared. There can already be a method to do this, but I may need to implement it myself.
When loading a virtual Image remotely from the N5 plugin there is not status as to how long it's loading will take. When read in a virtual stack each chunk is read from the S3 endpoint that is required for the current slice, and if it reads more data than required it will, buffering the read slice.
The order of slice presentation is as follows:
So the key moment to help display a progress bar would be in the S3 API, where the number of bytes read compared to total bytes needed can be compared. There can already be a method to do this, but I may need to implement it myself.