[bug?] loadWell loads grid of images at highest resolution

[manzt]

This is something that slipped past me previously, but it seems that loadWell (previously loadOmeWell) loads a grid of images at the highest resolution. This design choice leads to a lot of data-transfer and slow loading times. Is this the desired behavior?

Ideally the grid could handle multiple multiscale images, but in the mean time should we have some heuristic for which level to choose?

cc: @will-moore

[will-moore]

Yes, it was the intended behaviour since in the examples I've worked with so far, the number of Images in a Well has been relatively small and the images not very big, so the full resolution is more useful than a thumbnail. It was also slightly simpler to load the highest resolution since it doesn't require you to load the resolutions info for a sample image (as we do for the Plate).
But yes, this could certainly be improved to pick a suitable resolution based on the size and number of the Well images.