Skip to content

Latest commit

 

History

History
57 lines (35 loc) · 2.92 KB

README.md

File metadata and controls

57 lines (35 loc) · 2.92 KB
Raw

Back to Projects List

Using VolView with data in Google Storage buckets / IDC buckets

Key Investigators

  • Andrey Fedorov (Brigham and Women’s Hospital, USA)
  • Forrest Li (Kitware, USA)
  • Stephen Aylward (Kitware, USA)

Project Description

VolView is an open source radiological viewer developed by Kitware that excels in 3D visualization. Currently, this viewer can be used to visualize files uploaded into the browser.

NCI Imaging Data Commons is a cloud-based repository of cancer imaging data, which among other features provides free access to the DICOM files curated in Google Storage public buckets.

While IDC integrates OHIF and Slim viewers, the instances of the viewers maintained by IDC can only be used to visualize data in IDC. Users that want to visualize analysis results they produce in OHIF or Slim need to deploy their own instances of the viewers. That process is documented, but involves many steps and can be too difficult for many users. Furthermore, OHIF Viewer v2 used in IDC does not have any functionality to support 3D visualization.

In this project we want to investigate the use of existing VolView instance maintained by Kitware at https://volview.kitware.com/ to visualize data in public Google Storage buckets. This will allow:

  1. 3D visualization of public data in IDC.
  2. Not only "zero footprint", but more importantly "zero deployment" and "zero maintenance" viewer that can be used by IDC users to visualize analysis results.

Objective

  1. Investigate ability of VolView to pull data from Google Storage public buckets - in IDC and/or from user projects.
  2. Investigate representation of the manifest to be used to define VolView input.

Approach and Plan

  1. Experiment with CORS settings on a public "test" bucket.
  2. Define minimum necessary settings for CORS configuration.
  3. Coordinate with GCP support and other GCP experts as needed.

Progress and Next Steps

  1. Set up public bucket, so far changes to CORS do not seem to have effect, but maybe we did not wait long enough...
  2. ...
  3. ...

Illustrations

Background and References