How about adding an ITK processing step in the email handler somewhere around https://github.com/OpenImaging/miqa/blob/master/server/miqa_server/email.py#L46 to resample the image to 512x512 before appending it to the HTML?

That's an option. But I'm also wondering if we can find api somewhere on the client that would let us generate the image at a specified size. These values could either be 512 x 512 as you suggested, or else exposed to the user as an option as time permits.

Looping in @jimklo in case he has thoughts.

So far I haven't found api in vtk.js that would let us request a screenshot at a specified size.

Regardless of the approach we end up taking in the long run, I think I still have some questions about how this should behave.

1. I assume we want the screenshot to maintain the aspect ratio of the original image? If so, how should we choose an image size? E.g. we could choose to fix the larger dimension of screenshots to certain size, or fix the width to a certain size, and let the other dimension vary with the aspect ratio of the original image.
2. What kind of interpolation (for growing) and what kind of sampling (for shrinking) should we use in resizing?
3. Should the screenshot dimensions be chosen based on the original image resolution (perhaps to avoid excessive interpolation/sampling)?

Per discussion with Kilian & Jim on 4/28 - They indicated that aspect ratio has to be maintained. Their use case is that sometimes images are too large. Images almost/never need to be made larger. We discussed that MIQA (in the longer term) could be configurable somewhere to have default image sizes. In the current version, I believe we can set a fixed, reasonable size (e.g. 512xYYY). I suggest we implement either in the client or server. Looking at the server code, it looks not too hard to add an ITK filter in the Email section of the server code.

@scottwittenburg from Sebastien, we can it on the client side

1. screenshot same size to replace the rw with it

2. hide and resize rw

3. take screenshot

4. resize rw to origin and put it back to its original location

As per our discussions @scottwittenburg will push a PR to vtk.js to address MIQA needs (which also benefits others efforts) and if time remains integrate it in MIQA or hand if off to someone else.

I've reviewed OpenImaging/miqa-phase1#114 in our integration environment. The unless there's some additional setting that needs to be done, this doesn't appear to work quite yet. Via email all images I receive appear to be significantly larger than 512x512 (which is the fixed size hard coded in the PR.

OpenImaging/miqa-phase1#114 is a work in progress, in a sense that it depends on Kitware/vtk-js#1907.

I will follow up on this issue and revert back here

I have created a new issue that clarifies the requirements (#18). Closing this issue in favor of the new one.