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: Frontispiece/MATLAB_installation.md
+21-12Lines changed: 21 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Installation Instructions for MATLAB
11
11
-[Requirements](#requirements-1)
12
12
-[Simple Instructions](#simple-instructions-1)
13
13
-[Step by Step Instructions](#step-by-step-instructions1)
14
-
14
+
-[Advanced](#advanced)
15
15
*****
16
16
17
17
## Windows
@@ -20,24 +20,24 @@ Installation Instructions for MATLAB
20
20
21
21
1. MATLAB
22
22
2. Visual Studio (Community or Profesional)
23
-
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.0](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
23
+
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.5](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
24
24
4. CUDA Toolkit (9.2 or newer)
25
25
26
26
Tested on
27
27
28
28
| Software | Version |
29
29
| ------------- |:-------------:|
30
30
|**Windows**| 7, 8, 10.|
31
-
|**MATLAB**| 2014b 2016b 2017a 2018b|
32
-
|**CUDA**|9.2 10|
33
-
|**Visual Studio**| 2010 2013 2015|
31
+
|**MATLAB**|Any MATLAB >2016b|
32
+
|**CUDA**|Any CUDA 9.2>|
33
+
|**Visual Studio**| 2010 2013 2015 2019 2022|
34
34
35
35
36
36
37
37
### Simple Instructions
38
38
39
-
1. Install MATLAB, Visual Studio and CUDA
40
-
2. Rename either `mex_CUDA_win64_MVS2013.xml` (Visual Studio 2013 or older) or `mex_CUDA_win64_MVS2015.xml`(Visual Studio 2015 or newer) to `mex_CUDA_win64.xml`
39
+
1. Install MATLAB, Visual Studio and CUDA (Remember to install C++ when isntalling Visual Studio!)
40
+
2. Rename the XML file corresponding to the Visual Studio you have. e.g. `mex_CUDA_win64_MVS2015.xml`(Visual Studio 2015/2017) to `mex_CUDA_win64.xml`
41
41
3. Run `Compile.m`
42
42
43
43
A succesfull installation should be able to execute the script at `TIGRE/MATLAB/Demos/d03_generateData.m` without errors.
@@ -129,9 +129,9 @@ Tested on
129
129
130
130
| Software | Version |
131
131
| ------------- |:-------------:|
132
-
|**Ubuntu**| 16.04 17.10|
133
-
|**MATLAB**|2017a 2018b|
134
-
|**CUDA**|9.2 10.0|
132
+
|**Ubuntu**|Any ubuntu 16.04>|
133
+
|**MATLAB**|Any MATLAB 2016b>|
134
+
|**CUDA**|Any Cuda 0.2>|
135
135
|**gcc**| 6.4.0 7.2.0|
136
136
137
137
### Simple Instructions
@@ -141,7 +141,7 @@ Tested on
141
141
142
142
A succesfull installation should be able to execute the script at `TIGRE/MATLAB/Demos/d03_generateData.m` without errors.
143
143
144
-
### Step by Step Instructions:<sup>1</sup>
144
+
### Step by Step Instructions:
145
145
146
146
1. Install MATLAB
147
147
@@ -181,4 +181,13 @@ If none of this works, please contact the authors at [tigre.toolbox@gmail.com](m
181
181
182
182
****
183
183
184
-
<sup>1</sup> Testing by the TIGRE team in Linux is limited, thus the step by step instructions are less detailed than expected. Please do [contact us](mailto:ander.biguri@gmail.com) if you are having trouble or would like to contribute to the instructions.
184
+
## Advanced
185
+
186
+
If you are doing reconstruction of large datasets, and you want to use swap memory, you will need to deactivate TIGREs pinned memory feature at compile time. This will allow you to use swap memory, but it will make the operators in TIGRE slower, as pinned memory is used for simultaneous memory and compute.
187
+
188
+
189
+
You can do this by calling the `Compile.m` file from the MATLAB command line as `Compile --no_pinned_memory`.
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.0](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
23
+
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.5](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
11
24
4. CUDA Toolkit
12
25
13
26
Tested on
14
27
15
28
| Software | Version |
16
29
| ------------- |:-------------:|
17
30
|**Windows**| 10 |
18
-
|**Python**| 3.7 3.8 |
19
-
|**CUDA**|10.1 |
31
+
|**Python**| 3.7 3.8 3.9 3.10|
32
+
|**CUDA**|9.2>|
20
33
|**MSVC**| 19.24 |
21
34
22
35
### Simple Instructions
@@ -63,19 +76,19 @@ A succesfull installation should be able to execute the script at `TIGRE/Python/
63
76
64
77
### Requirements:
65
78
66
-
1. Python 2/Python 3
79
+
1. Python 3
67
80
2. gcc
68
-
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.0](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
81
+
3. A CUDA capable GPU from NVIDIA with [compute capability greater or equal to 3.5](https://en.wikipedia.org/wiki/CUDA#GPUs_supported)
69
82
4. CUDA Toolkit
70
83
71
84
72
85
Tested on
73
86
74
87
| Software | Version |
75
88
| ------------- |:-------------:|
76
-
|**Ubuntu**| 16.04 17.10|
77
-
|**Python**|2.7 3.7 |
78
-
|**CUDA**|8.0 9.2 10.1 10.2|
89
+
|**Ubuntu**| 16.04>|
90
+
|**Python**|3.7-3.10|
91
+
|**CUDA**| 9.2>|
79
92
|**gcc**| 7.6.0|
80
93
81
94
### Simple Instructions
@@ -90,14 +103,17 @@ A succesfull installation should be able to execute the script at `TIGRE/Python/
90
103
91
104
For Ubuntu
92
105
93
-
1. Install python and pip (you can use 2 or 3, example show for 2)
106
+
1. Install python and pip
107
+
108
+
Recommended to do it via [Anaconda3](https://docs.anaconda.com/free/anaconda/install/linux/)
94
109
95
110
```
96
111
sudo apt update
97
112
sudo apt upgrade
98
-
sudo apt install python2.7 python-pip
113
+
sudo apt install python3.10 python-pip
99
114
```
100
115
116
+
101
117
2. Install CUDA
102
118
103
119
Installing CUDA in linux (specially one with a GUI) can be a challenge. Please follow [NVIDIAs instructions](https://developer.download.nvidia.com/compute/cuda/10.0/Prod/docs/sidebar/CUDA_Installation_Guide_Linux.pdf) carefully.\
**NOTE:** pre-commit may also be manually invoked against *all* files (staged and unstaged) using the `pre-commit run --all-files`. However, some changes made to Python's TIGRE codebase by `black` have been manually reverted for readability reasons and should not be committed in their blackened state.
204
+
205
+
## Advanced
206
+
207
+
If you are doing reconstruction of large datasets, and you want to use swap memory, you will need to deactivate TIGREs pinned memory feature at compile time. This will allow you to use swap memory, but it will make the operators in TIGRE slower, as pinned memory is used for simultaneous memory and compute.
208
+
209
+
You can do this by calling the `stup.py` with the flag `--no_pinned_memory`.
0 commit comments