Viewers: Buffer allocation failure trying to do MPR for a large series

[fedorov]

Here's a large series that takes very very long time to download, and causes MRP failure:

https://viewer.imaging.datacommons.cancer.gov/viewer/1.3.6.1.4.1.14519.5.2.1.1706.4009.243406849348906151042089406192?seriesInstanceUID=1.3.6.1.4.1.14519.5.2.1.1706.4009.304054433668574201838767925472

Is this the expected behavior for this specific dataset? When the series is too large, is it possible to disable MPR button?

[pieper]

yes, it's 3000 images, so it makes sense to me that it's too large.

We may not be able to know the exact allocation limit in advance, but we could certainly detect this error and give a more helpful message. Ideally offering an alternative viewing option (e.g. download to slicer or similar).

I would bump this one to IDC:priorirty.

[fedorov]

Here's a legacy converted enhanced MF version of the same series, just in case: https://idc-sandbox-000.firebaseapp.com/projects/idc-tcia/locations/us/datasets/afshin_results_00_idc_tcia_mvp_wave0/dicomStores/MULTIFRAME/study/1.3.6.1.4.1.14519.5.2.1.1706.4009.243406849348906151042089406192?seriesInstanceUID=1.3.6.1.4.1.43046.3.1.9.5060456482850075494393251866013736567025

[pieper]

Here's the same study in the sandbox in case that helps:

https://idc-sandbox-000.firebaseapp.com/projects/idc-dev-etl/locations/us-central1/datasets/idc-tcia/dicomStores/idc-tcia/study/1.3.6.1.4.1.14519.5.2.1.1706.4009.243406849348906151042089406192

[pieper]

Related to #2223

[igoroctaviano]

@pieper @fedorov This PR adds a more helpful notification: https://github.com/OHIF/Viewers/pull/2246.

...also it adds a new option to the notification service which allows us to define an action (button), as suggested by Steve, we can use this action option to define a new button that will trigger something like: download to slicer. If that's the case, we should align whats the correct behavior.

[pieper]

thanks @igoroctaviano - on our next prioritization call let's discuss what actions would make the most sense for cases like this. Thinking about this now I realize in the past we haven't wanted to offer the download option so maybe the message should just say that the dataset is too big to display in MPR and the button should return to the default view.