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: README.md
+20-26Lines changed: 20 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,4 @@
1
-
SlicerVirtualReality
2
-
====================
1
+
# SlicerVirtualReality
3
2
4
3
Extension for 3D slicer that enables user to interact with the 3D scene using virtual reality.
5
4
@@ -9,6 +8,8 @@ The extension works with all OpenVR-compatible headsets, such as [HTC Vive](#set
9
8
10
9
[](https://www.youtube.com/watch?v=F_UBoE4FaoY)
11
10
11
+
## Features
12
+
12
13
Features include:
13
14
- View all content of any of the 3D viewers in Slicer, anytime, by a single click.
14
15
- Show volumes as 2D image slices or volume rendering, render surfaces, points, etc.
@@ -22,9 +23,6 @@ Features include:
22
23
23
24
Feature set of the extension is continuously improved. You can give us feedback and propose ideas for improvements by submitting them on the [issue tracker](https://github.com/KitwareMedical/SlicerVirtualReality/issues).
24
25
25
-
Usage
26
-
-----
27
-
28
26
## Setup
29
27
30
28
**Platform support:** Currently the extension only works on Windows computers. Linux support is experimental: [Steam VR has limited support on linux](https://github.com/ValveSoftware/SteamVR-for-Linux/blob/master/README.md) and the Slicer extension is built for Linux but not tested. The extension is not available on macOS, as currently there are no virtual reality headsets available for macOS. If you wish to use Virtual Reality extension on Linux or macOS and you have virtual reality capable hardware and Steam VR works well on your computer then add a comment in the issue tracker ([macOS](https://github.com/KitwareMedical/SlicerVirtualReality/issues/3) / [Linux](https://github.com/KitwareMedical/SlicerVirtualReality/issues/57)).
@@ -72,10 +70,10 @@ Controls:
72
70
- Touchpad forward: fly forward
73
71
- Touchpad backwad: fly backward
74
72
75
-
Notes:
76
-
- Flying direction is specified by the orientation of the controller.
77
-
- Speed is proportional to distance of the fingertip from the touchpad center.
78
-
- Maximum speed is configurable in Virtual Reality module.
73
+
> [!NOTE]
74
+
> - Flying direction is specified by the orientation of the controller.
75
+
> - Speed is proportional to distance of the fingertip from the touchpad center.
76
+
> - Maximum speed is configurable in Virtual Reality module.
79
77
80
78
### Transform entire scene
81
79
@@ -86,9 +84,9 @@ Controls: while keeping grip button depressed on both controllers
86
84
- Translate controllers in parallel up/down/left/right/forward/backward: translate the entire scene
87
85
- Pivot controllers around: rotate the entire scene
88
86
89
-
Notes:
90
-
- Object positions in the scene are not modified.
91
-
- Controllers must be outside of all selectable objects when grip buttons are pressed.
87
+
> [!NOTE]
88
+
> - Object positions in the scene are not modified.
89
+
> - Controllers must be outside of all selectable objects when grip buttons are pressed.
92
90
93
91
### Transform objects
94
92
@@ -99,12 +97,12 @@ Controls: press grip button when a controller is inside a selectable object
99
97
- Translate controllers in parallel up/down/left/right/forward/backward: translate all objects
100
98
- Move controller
101
99
102
-
Notes:
103
-
- When you grab and move object, a parent transform is automatically created for it (if it has not been under a transform already) and that transform is modified.
104
-
- To move a group of objects together, assign the same parent transform to them. You can do that in _Data_ module's _Transform hierarchy_ tab by drag-and-dropping objects under the same transform (or by double-clicking in the _Applied Transform_ column in _Data_ module's _Transform hierarchy_ tab and selecting a transform; or by selecting a transform in _Transforms_ module and applying it to all the nodes that must move together).
105
-
- Either left or right controller can be used to grab an object. Each controller can be used to grab an object and move independently.
106
-
- By default all objects are selectable. An object can be made non-selectable (thus non-movable) in Data module / Subject hierarchy tab, right-clicking on the node and unchecking "Toggle Selectable".
107
-
- Moving of segmentation nodes is slow. If you want to move segmentations using controllers then export them to model nodes (in _Data_ module, right-click on the segmentation node and choose _Export visible segments to models_) and transform the model nodes.
100
+
> [!NOTE]
101
+
> - When you grab and move object, a parent transform is automatically created for it (if it has not been under a transform already) and that transform is modified.
102
+
> - To move a group of objects together, assign the same parent transform to them. You can do that in _Data_ module's _Transform hierarchy_ tab by drag-and-dropping objects under the same transform (or by double-clicking in the _Applied Transform_ column in _Data_ module's _Transform hierarchy_ tab and selecting a transform; or by selecting a transform in _Transforms_ module and applying it to all the nodes that must move together).
103
+
> - Either left or right controller can be used to grab an object. Each controller can be used to grab an object and move independently.
104
+
> - By default all objects are selectable. An object can be made non-selectable (thus non-movable) in Data module / Subject hierarchy tab, right-clicking on the node and unchecking "Toggle Selectable".
105
+
> - Moving of segmentation nodes is slow. If you want to move segmentations using controllers then export them to model nodes (in _Data_ module, right-click on the segmentation node and choose _Export visible segments to models_) and transform the model nodes.
108
106
109
107
## Other features
110
108
@@ -167,26 +165,22 @@ If you are certain that you have found a software bug and no similar issue has b
167
165
168
166
Please do not use "VR" acronym (you can spell out "virtual reality" instead), because "VR" may mean "volume rendering" just as well as "virtual reality" - you can even do volume rendering in virtual reality in Slicer - and so it becomes confusing very quickly.
169
167
170
-
For developers
171
-
--------------
168
+
## For developers
172
169
173
170
Information for developers is available in the [Developer Guide](DeveloperGuide.md).
- VASST Lab (Robarts Research Insitute): Adam Rankin
182
178
183
-
How to cite
184
-
-----------
179
+
## How to cite
185
180
186
181
Pinter, C., Lasso, A., Choueib, S., Asselin, M., Fillion-Robin, J. C., Vimort, J. B., Martin, K., Jolley, M. A. & Fichtinger, G. (2020). SlicerVR for Medical Intervention Training and Planning in Immersive Virtual Reality. IEEE Transactions on Medical Robotics and Bionics, vol. 2, no. 2, pp. 108-117, May 2020, doi: 10.1109/TMRB.2020.2983199
0 commit comments