You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/authentication.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ VolView itself does not specify any given authentication mechanism to use. How y
4
4
5
5
## VolView behind Login Portal
6
6
7
-
The easiest approach to securing a VolView instance is to host VolView behind an authentication portal. This will secure access to VolView, and allow VolView to automatically use existing user credentials to request protected data. Often the credentials are stored in a cookie.
7
+
The easiest approach to securing a VolView instance is to host VolView behind an authentication portal. This will secure access to VolView, and allow VolView to automatically use existing user credentials to request protected data. Often the credentials are stored in a cookie.
8
8
9
9
## OAuth Tokens via URL
10
10
@@ -26,4 +26,4 @@ The token URL is expected to return the access token as plaintext, i.e. `text/pl
26
26
By default, VolView will make a `GET` request to the token URL. If another type of request is needed, you can configure it via the `tokenUrlMethod` parameter. For example, to make a `POST` request: `https:/example.com/VolView/?tokenUrl=https://example.com/userToken&tokenUrlMethod=POST`.
27
27
28
28
> [!NOTE]
29
-
> This requires CORS to be properly configured for the token URL endpoint. See the [CORS](/cors) documentation for more info.
29
+
> This requires CORS to be properly configured for the token URL endpoint. See the [CORS](/cors) documentation for more info.
Copy file name to clipboardExpand all lines: docs/cors.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,4 +26,4 @@ server {
26
26
27
27
## CORS proxy
28
28
29
-
If you do not control the data server, you can use a CORS proxy. A CORS proxy is a lightweight proxy server that is configured to attach CORS headers to responses originating from the data server.
29
+
If you do not control the data server, you can use a CORS proxy. A CORS proxy is a lightweight proxy server that is configured to attach CORS headers to responses originating from the data server.
Copy file name to clipboardExpand all lines: docs/deploying_volview.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Deploying VolView is straightforward: just take the locally built files in `dist
5
5
As a local example, running `npx serve dist/` will spin up a static file server (running on <http://localhost:3000>) that reads the locally built files from `dist/`.
6
6
7
7
> [!NOTE]
8
-
> Using `npx serve` is *not* a recommended way to deploy VolView. It is only used to demonstrate how easy it can be to deploy VolView in simple scenarios.
8
+
> Using `npx serve` is _not_ a recommended way to deploy VolView. It is only used to demonstrate how easy it can be to deploy VolView in simple scenarios.
9
9
10
10
## Managed Hosting (S3, GCP, etc.)
11
11
@@ -17,7 +17,7 @@ Please refer to your desired server's documentation on how to serve static files
17
17
18
18
### Apache example config
19
19
20
-
In this apache2 example, the `dist/*` files are located under `/var/www/VolView`, and the domain is `example.com`. This does *not* configure TLS.
20
+
In this apache2 example, the `dist/*` files are located under `/var/www/VolView`, and the domain is `example.com`. This does _not_ configure TLS.
21
21
22
22
```
23
23
<VirtualHost *:80>
@@ -28,7 +28,7 @@ In this apache2 example, the `dist/*` files are located under `/var/www/VolView`
28
28
29
29
### Nginx example config
30
30
31
-
In this nginx example, the `dist/*` files are located under `/var/www/VolView`, and the domain is `example.com`. This does *not* configure TLS.
31
+
In this nginx example, the `dist/*` files are located under `/var/www/VolView`, and the domain is `example.com`. This does _not_ configure TLS.
Copy file name to clipboardExpand all lines: docs/index.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,33 +8,34 @@ VolView is an open source radiological viewer developed for clinical professiona
8
8
9
9
Major features of VolView include:
10
10
11
-
1.**Cinematic Volume Rendering**: Create beautiful renderings and gain new insights into your data with only a few clicks. VolView provides three cinematic volume rendering modes and intuitive controls for each. We've also provides simple ways to control lighting and multiple presets to get you started.
11
+
1.**Cinematic Volume Rendering**: Create beautiful renderings and gain new insights into your data with only a few clicks. VolView provides three cinematic volume rendering modes and intuitive controls for each. We've also provides simple ways to control lighting and multiple presets to get you started.
12
12
13
-
2.**Drag-and-Drop DICOM**: Drag DICOM images onto VolView, and they will be quickly parsed and presented as thumbnails. Click on a thumbnail, and the data is quickly loaded and presented as 2D slices and a 3D cinematic volume rendering.
13
+
2.**Drag-and-Drop DICOM**: Drag DICOM images onto VolView, and they will be quickly parsed and presented as thumbnails. Click on a thumbnail, and the data is quickly loaded and presented as 2D slices and a 3D cinematic volume rendering.
14
14
15
-
3.**Annotations and Measures**: We have provided a small set of tools for painting, measuring, and cropping, and we are actively working to expand that toolset. If you have suggestions for new tools or for improving VolView in general, please leave feedback at our [Issue Tracker](https://github.com/Kitware/VolView/issues).
15
+
3.**Annotations and Measures**: We have provided a small set of tools for painting, measuring, and cropping, and we are actively working to expand that toolset. If you have suggestions for new tools or for improving VolView in general, please leave feedback at our [Issue Tracker](https://github.com/Kitware/VolView/issues).
16
16
17
-
4.**Simple, Scalable, and Secure**: Simply visit a website to install VolView. Once it is running, all data handling, processing, and visualization occurs on your machine. Data you load into VolView never leaves your machine. And VolView is designed to run on any web browser: from the one on your phone to the one running on your most powerful workstations. It will take advantage of local GPU resources to accelerate its rendering processes, but if none is available, it will still generate the same high quality renderings, albeit a bit slower.
17
+
4.**Simple, Scalable, and Secure**: Simply visit a website to install VolView. Once it is running, all data handling, processing, and visualization occurs on your machine. Data you load into VolView never leaves your machine. And VolView is designed to run on any web browser: from the one on your phone to the one running on your most powerful workstations. It will take advantage of local GPU resources to accelerate its rendering processes, but if none is available, it will still generate the same high quality renderings, albeit a bit slower.
18
18
19
-
5.**Foundation for the Future**: VolView is meant to serve as a foundation for your future projects and products. It is open-source and free for commercial and academic use. You may modify it yourself, or Kitware can help you customize it to support client-server workflows, provide streamlined interfaces and tools, and carry your brand.
19
+
5.**Foundation for the Future**: VolView is meant to serve as a foundation for your future projects and products. It is open-source and free for commercial and academic use. You may modify it yourself, or Kitware can help you customize it to support client-server workflows, provide streamlined interfaces and tools, and carry your brand.
20
20
21
-
VolView is **not FDA approved for any purpose**, but Kitware can work with you to create a custom version of VolView and submit it for FDA approval. For more information, contact [kitware@kitware.com](mailto:kitware@kitware.com).
21
+
VolView is **not FDA approved for any purpose**, but Kitware can work with you to create a custom version of VolView and submit it for FDA approval. For more information, contact [kitware@kitware.com](mailto:kitware@kitware.com).
22
22
23
23
## History
24
24
25
25
VolView version 1.1 was released on Sept. 21, 1999 to provide clinical professionals with an intuitive interface to industry-leading volume rendering capabilities. Built using [VTK](https://vtk.org), it was extremely innovative at the time. It provided interactive volume renderings that did not require dedicated systems purchased for big-name medical device manufacturers. It supported Windows 95/98/NT, Sun, Silicon Graphics and Linux environments, and it provided custom level-of-detail and composite rendering techniques. That version of VolView thrived for over a decade, with the last release in June of 2011. In 2011, open source radiological viewers had become commonplace (many also built using VTK), and we pivoted our attention to 3D Slicer as an advance, community-support, extensible platform for research and clinical application development.
26
26
27
-
We have released VolView 4.0 in 2022 to again advance the radiological image visualization field. Built using the javascript version of VTK (i.e., [vtk.js](https://kitware.github.io/vtk-js/index.html)), VolView 4.0 runs in web browsers and provides cinematic volume rendering capabilities that are only broadly available in dedicated systems sold by big-name medical device manufacturers. We look forward to continuing to use the VolView platform for medical image visualization innovation, with plans to support WebXR for holographic and AR/VR devices as well as companion libraries for advance image analysis (e.g., [itk.wasm](https://github.com/InsightSoftwareConsortium/itk-wasm)) and AI algorithms (e.g., via [MONAI](https://monai.io)).
27
+
We have released VolView 4.0 in 2022 to again advance the radiological image visualization field. Built using the javascript version of VTK (i.e., [vtk.js](https://kitware.github.io/vtk-js/index.html)), VolView 4.0 runs in web browsers and provides cinematic volume rendering capabilities that are only broadly available in dedicated systems sold by big-name medical device manufacturers. We look forward to continuing to use the VolView platform for medical image visualization innovation, with plans to support WebXR for holographic and AR/VR devices as well as companion libraries for advance image analysis (e.g., [itk.wasm](https://github.com/InsightSoftwareConsortium/itk-wasm)) and AI algorithms (e.g., via [MONAI](https://monai.io)).
28
28
29
29
## Roadmap
30
30
31
31
Details and progress on our roadmap are tracked in the VolView issue tracker on Github: https://github.com/Kitware/VolView/issues
32
32
33
33
Our next major release is planned for March, 2023, and it will support:
34
-
* DICOM Web
35
-
* DICOM SEG, RT, and SR reading and writing
36
-
* ITK for image processing
37
-
* Deep learning inference for image analysis
34
+
35
+
- DICOM Web
36
+
- DICOM SEG, RT, and SR reading and writing
37
+
- ITK for image processing
38
+
- Deep learning inference for image analysis
38
39
39
40
## Citation
40
41
@@ -50,14 +51,13 @@ This work was funded, in part, by the NIH via NIBIB and NIGMS R01EB021396, NIBIB
50
51
51
52
## Related Work
52
53
53
-
Learn about our related works at the following links:
54
-
* Glance: General purpose scientific visualization in web browsers
55
-
*https://kitware.github.io/glance/index.html
56
-
* 3D Slicer: Desktop (C++ and Python), extensible radiological viewer
57
-
*https://slicer.org
58
-
* trame: Python framework for quickly creating web application involving server-side rendering and computation.
59
-
*https://kitware.github.io/trame/index.html
60
-
* itk.wasm: Web-assembly version of ITK for in-browser image segmentation and registration, with outstanding DICOM support.
0 commit comments