Skip to content

Commit 7926159

Browse files
skalarproduktraumgitbook-bot
authored andcommitted
GITBOOK-20: No subject
1 parent 616167c commit 7926159

File tree

3 files changed

+11
-14
lines changed

3 files changed

+11
-14
lines changed

basics/volumetric-data.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,19 @@ Let's start with our trusty ImageJ toolbar and an empty sciview scene.
44

55
![](../.gitbook/assets/imagej-empty-sciview.png)
66

7-
Now open the script editor by first clicking on the ImageJ toolbar then pressing "\[". Download and open this script in the sceipt editor to generate a 3D image volume that we can use
7+
Now open the script editor by first clicking on the ImageJ toolbar then pressing "\[". Download and open this script in the script editor to generate a 3D image volume that we can use.
88

99
![](../.gitbook/assets/open-generate-test-volume-script.png)
1010

11-
Now press "Run" or Ctrl + r
11+
Now press "Run" or Ctrl + R
1212

1313
![](../.gitbook/assets/generate-test-volume-output.png)
1414

1515
You can close the script editor, then "Add volume" in sciview.
1616

1717
![](../.gitbook/assets/add-volume.png)
1818

19-
Then you will get a dialog, where you can change the resolution of your volume's voxels \(for example, if you are using confocal microscopy data your z-resolution will be much larger\)
19+
Then you will get a dialog where you can change the resolution of your volume's voxels (for example, if you are using confocal microscopy data, your z-resolution will be much larger)
2020

2121
![](../.gitbook/assets/add-volume-dialog.png)
2222

@@ -32,7 +32,7 @@ Start recording a video
3232

3333
![](../.gitbook/assets/start-recording-video.png)
3434

35-
After some time, stop recording the videos
35+
After some time, stop recording the video
3636

3737
![](../.gitbook/assets/stop-recording-video.png)
3838

@@ -69,4 +69,3 @@ You'll get a volume that looks like this
6969
Now press play and enjoy
7070

7171
![](../.gitbook/assets/play-demo-timeseries.png)
72-

complex-data/segmentations.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ We will explore this demo using IntelliJ, partially because the benefit of auto-
44

55
![](../.gitbook/assets/select-ShowSegmentationDemo-source-tree.png)
66

7-
This demo begins with a demo image. The details of how this image is generated aren't important, but it creates a tuneable number of spheres in random positions within a `(100,100,100)` image \(aka RandomAccessibleInterval\).
7+
This demo begins with a demo image. The details of how this image is generated aren't important, but it creates a tuneable number of spheres in random positions within a `(100,100,100)` image (aka RandomAccessibleInterval).
88

99
![](../.gitbook/assets/generated-image-source.png)
1010

@@ -14,9 +14,9 @@ We then display this image as a volume in sciview
1414

1515
![](../.gitbook/assets/generated-volume.png)
1616

17-
Now comes a key step, we perform what is called a "Connected Components Analysis" \(aka CCA\), which assigns all connected pixels to a specific label. Each of these labels represents a segmentation.
17+
Now comes a key step, we perform what is called a "Connected Components Analysis" (aka CCA), which assigns all connected pixels to a specific label. Each of these labels represents a segmentation.
1818

19-
Note one nuance of this is that if 2 of our randomly generated spheres overlap, they will be treated as being connected.
19+
Note: one nuance of this is that if 2 of our randomly generated spheres overlap, they will be treated as being connected.
2020

2121
An alternative would have been to use the pixel values of the image to create each `LabelRegion`. However, in practice that is not a luxury that an image analyst has.
2222

@@ -27,4 +27,3 @@ The next thing to do is to create meshes for each segmentation label that we hav
2727
![](../.gitbook/assets/create-meshes-source.png)
2828

2929
![](../.gitbook/assets/display-segmentation-meshes.png)
30-

vr-and-ar/vr-and-ar.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,14 @@ sciview works with all VR headsets that are supported by SteamVR, including:
1111
* Oculus Rift S
1212
* HTC Vive, HTC Vive Pro, HTC Vive Pro Eye
1313
* Valve Index
14-
* Windows Mixed Reality headsets \(such as the Samsung Odyssey\)
14+
* Windows Mixed Reality headsets (such as the Samsung Odyssey)
1515

1616
In addition, we have alpha-quality support for the Microsoft Hololens. Support for this AR headset will be extended in the future. For the moment and in the remainder of this article here, we concentrate on VR headsets.
1717

18-
In order to be able to use VR headsets for rendering in sciview, especially when rendering volumetric data, a relatively powerful computer is recommended. Our recommendation there would be to have at least 16-32 GB of RAM, and a GPU capable of fast VR rendering at high resolutions, such as a Geforce RTX 2080 or a AMD Radeon RX5700.
18+
In order to be able to use VR headsets for rendering in sciview, especially when rendering volumetric data, a relatively powerful computer is recommended. Our recommendation there would be to have at least 16-32 GB of RAM, and a GPU capable of fast VR rendering at high resolutions, such as a Geforce RTX 2080 or an AMD Radeon RX5700.
1919

20-
sciview relies on [SteamVR/OpenVR](https://store.steampowered.com/app/250820/SteamVR/) for rendering to your VR headset. You can follow the [setup guide for the HTC Vive](https://support.steampowered.com/steamvr/HTC_Vive/) for setting it up, or use the one for your specific headset. Note that if you use a Windows Mixed Reality headset, you need to have [Windows Mixed Reality for SteamVR](https://store.steampowered.com/app/719950/Windows_Mixed_Reality_for_SteamVR/) installed in addition to SteamVR itself.
20+
sciview relies on [SteamVR/OpenVR](https://store.steampowered.com/app/250820/SteamVR/) for rendering to your VR headset. You can follow the [setup guide for the HTC Vive](https://support.steampowered.com/steamvr/HTC\_Vive/) for setting it up, or use the one for your specific headset. Note that if you use a Windows Mixed Reality headset, you need to have [Windows Mixed Reality for SteamVR](https://store.steampowered.com/app/719950/Windows\_Mixed\_Reality\_for\_SteamVR/) installed in addition to SteamVR itself.
2121

2222
## Rendering to your VR headset in sciview
2323

24-
To activate rendering to an attached VR headset, choose `View`> `Render to OpenVR HMD` in sciview's menu bar. If not already open, SteamVR will start and the current scene will appear in your VR headset.
25-
24+
To activate rendering to an attached VR headset, choose `View`> `Render to OpenVR HMD` in sciview's menu bar. If not already open, SteamVR will start and the current scene will appear in your VR headset.

0 commit comments

Comments
 (0)