forked from topology-tool-kit/topology-tool-kit.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathinstallation-osx-0.9.4.html
More file actions
434 lines (335 loc) · 18.1 KB
/
Copy pathinstallation-osx-0.9.4.html
File metadata and controls
434 lines (335 loc) · 18.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="The Topology ToolKit">
<meta name="author" content="The Topology ToolKit">
<meta name="keywords" content="TTK, Topology ToolKit, Topological Data
Analysis, Visualization, Reeb graph, Reeb Space, Morse-Smale complex, contour
tree, persistence diagram, persistence curve, continuous scatterplot, fiber
surface, contour forests, jacobi set, mandatory critical points, topological
simplification, VTK, ParaView, Python" />
<title>TTK - the Topology ToolKit - Topological Data Analysis and
Visualization</title>
<!-- Bootstrap Core CSS -->
<link href="vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet">
<!-- Theme CSS -->
<link href="css/clean-blog.min.css" rel="stylesheet">
<!-- Custom Fonts -->
<link href="vendor/font-awesome/css/font-awesome.min.css" rel="stylesheet" type="text/css">
<link href='https://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic' rel='stylesheet' type='text/css'>
<link href='https://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,300,600,700,800' rel='stylesheet' type='text/css'>
<link rel="apple-touch-icon" sizes="180x180" href="apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="favicon-16x16.png">
<link rel="manifest" href="site.webmanifest">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">
<!-- HTML5 Shim and Respond.js IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/libs/html5shiv/3.7.0/html5shiv.js"></script>
<script src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js"></script>
<![endif]-->
<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','https://www.google-analytics.com/analytics.js','ga'
);
ga('create', 'UA-88087813-1', 'auto');
ga('send', 'pageview');
</script>
<script type="text/javascript">
var _gaq = _gaq || [];
var pluginUrl =
'//www.google-analytics.com/plugins/ga/inpage_linkid.js';
_gaq.push(['_require', 'inpage_linkid', pluginUrl]);
_gaq.push(['_setAccount', 'UA-88087813-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type =
'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl'
: 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(ga, s);
})();
</script>
<!-- End Google Analytics -->
</head>
<body>
<!-- Navigation -->
<nav class="navbar navbar-default navbar-custom navbar-fixed-top">
<div class="container-fluid">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header page-scroll">
<button type="button" class="navbar-toggle"
data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
Menu <i class="fa fa-bars"></i>
</button>
<a class="navbar-brand" href="index.html">
TTK Home</a>
</div>
<!-- Collect the nav links, forms, and other content for toggling
-->
<div class="collapse navbar-collapse"
id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<li>
<a href="gallery.html">Gallery</a>
</li>
<li>
<a href="downloads.html">Downloads</a>
</li>
<li>
<a href="installation.html">Installation</a>
</li>
<li>
<a href="tutorials.html">Tutorials</a>
</li>
<li>
<a href="documentation.html">Documentation</a>
</li>
<li>
<a href="contribute.html">Contribute</a>
</li>
<li>
<a href="contact.html">Contact</a>
</li>
</ul>
</div>
<!-- /.navbar-collapse -->
</div>
<!-- /.container -->
</nav>
<!-- Page Header -->
<!-- Set your background image for this header on the line below. -->
<header class="intro-header"
style="background-image: url('img/morseHills.png'">
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
<div class="page-heading">
<h1>Topology ToolKit</h1>
<hr class="small">
<span class="subheading">OSX Installation</span>
</div>
</div>
</div>
</div>
</header>
<!-- Main Content -->
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
Please find below detailed instructions for the installation of TTK under
MacOS.<br><br>
TTK is also supported on other operating systems:<br>
·
<a href="installation.html">
Linux installation instructions</a> (default target platform);
<br>
·
<a href="installation-windows.html">
Windows installation instructions</a>.<br><br>
This page describes installing TTK 0.9.3 on OSX, using High Sierra 10.13.2 and
ParaView 5.4.1. The key differences from the linux installation involve how
ParaView is compiled, installing certain dependencies, and setting up some of
the paths for OSX. The following assumes that the target is to compile with
OSX clang and uses homebrew for dependencies.<br><br>
Other versions of earlier software packages
may require slight variations in the installation procedure.
For earlier versions of both software packages, you may want to check out
previous versions of our installation notes for OSX: <br>
·
<a href="installation-osx-0.9.2.html">TTK 0.9.2 with ParaView 5.4.0</a>.<br>
<p><h3>1. Downloads</h3>
Note: The instructions for this step are identical to those on linux:<br><br>
TTK builds on top of <a href="http://www.paraview.org"
target="new">ParaView</a> for its main user interface. Thus, you will first
need to download
<a
href="https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.4&type=binary&os=Sources&downloadFile=ParaView-v5.4.1.tar.gz"
target="new">
ParaView 5.4.1's source code</a>.
Note
that TTK plugins for ParaView will only work with a version of ParaView
compiled from source. Thus, if you already installed ParaView with a binary
copy, you may need to un-install it before proceeding.
Next, download TTK from our <a
href="downloads.html">download page</a>.
</p>
<p><h3>2. Installing the dependencies</h3>
Using <a href="https://brew.sh/">homebrew</a>, install:
<ul>
<li> cmake (tested with 3.10.0) </li>
<li> qt5 (tested with 5.10.0) </li>
<li> python (tested with 2.7.14) </li>
<li> vtk (tested with 8.0.1_1) </li>
</ul>
Using the command: <br><br>
<code>$ brew install cmake qt5 python vtk</code><br><br>
<h4>a) Optional Dependencies</h4>
Using homebrew, one can install:
<ul>
<li> ffmpeg (tested with 3.4.1) </li>
<li> hdf5 (tested with 1.10.1_2) </li>
<li> tbb (tested with 2018_U1) -- needed for OSPRay </li>
<li> mpich (tested with 3.2_3) -- needed for OSPRay's execution </li>
</ul>
Using the command (or only parts of it): <code>$ brew install ffmpeg hdf5 tbb mpich</code><br><br>
And, in addition, one can install OSPRay and it's dependencies using:
<ul>
<li>Download and unpack ospray-1.4.2.x86_64.dmg from <a href="http://www.ospray.org/getting_ospray.html">http://www.ospray.org/getting_ospray.html</a> (this installs in /opt/local/lib).</li>
<li>Download and unpack embree-2.17.1.x86_64.dmg from <a href="https://embree.github.io/downloads.html">https://embree.github.io/downloads.html</a> (this installs in /opt/local/lib).</li>
<li>Download and unpack tbb2018_20170919oss_mac.tgz from <a href="https://github.com/01org/tbb/releases">https://github.com/01org/tbb/releases</a>. After expanding the .tar, I created a directory /opt/local/include/tbb and moved the headers there, while I also created a directory /opt/local/lib/tbb and moved the library files there. Why? The homebrew install for tbb doesn't created the *_debug.dylib's. One could also just install TBB entirely from the website and skip the homebrew install, but in theory these versions match</li>
</ul><br>
After doing so, you'll likely want to make sure that your commandline knows about ospray/embree/tbb, the easy fix for this is to add <code>export DYLD_LIBRARY_PATH="/opt/local/lib"</code> to your <code>~/.bashrc</code>.
</p>
<p><h3>3. Preparing the sources</h3>
Note: The instructions for this step are identical to those on linux:<br><br>
Move the tarballs to a working directory (for instance called
<code>~/ttk</code>) and decompress them by entering the following commands in
a terminal (this assumes that you downloaded the tarballs to the
<code>~/Downloads</code> directory):<br><br>
<code>$ mkdir ~/ttk</code><br>
<code>$ mv ~/Downloads/ParaView-v5.4.1.tar.gz ~/ttk/</code><br>
<code>$ mv ~/Downloads/ttk-0.9.3.tar.gz ~/ttk/</code><br>
<code>$ cd ~/ttk</code><br>
<code>$ tar xvzf ParaView-v5.4.1.tar.gz</code><br>
<code>$ tar xvzf ttk-0.9.3.tar.gz</code><br><br>
You can delete the tarballs after the source trees have been decompressed by
entering the following commands:<br><br>
<code>$ rm ParaView-v5.4.1.tar.gz</code><br>
<code>$ rm ttk-0.9.3.tar.gz</code><br><br>
</p>
<p><h3>4. Patching the ParaView source tree</h3>
Note: The instructions for this step are identical to those on linux:<br><br>
In order to enjoy the complete set of TTK features, we
recommend at this stage to patch the ParaView source tree.
This step is
optional.
To proceed, go to
the patch directory and apply it as follows:<br><br>
<code>$ cd ~/ttk/ttk-0.9.3/paraview/patch</code><br>
<code>$ ./patch-paraview-5.4.1.sh
~/ttk/ParaView-v5.4.1/</code><br><br>
</p>
<p><h3>5. Configuring, building and installing ParaView</h3>
<h4>a) Configuration</h4>
To enter the configuration menu of ParaView's build, enter the following commands:<br><br>
<code>$ cd ~/ttk/ParaView-v5.4.1/</code><br>
<code>$ mkdir build</code><br>
<code>$ cd build</code><br>
<code>$ ccmake ..</code> (on OSX there is no <code>cmake-gui</code>)<br><br>
Then, press 'c' to configure and we'll edit some CMake flags:<br><br>
<code> · CMAKE_BUILD_TYPE=Release</code><br>
<code> · PARAVIEW_ENABLE_PYTHON=ON</code><br>
<code> · PARAVIEW_INSTALL_DEVELOPMENT_FILES=OFF</code> (this is unused, should be default)<br>
<code> · PARAVIEW_QT_VERSION=5</code> (Qt4 is deprecated on homebrew, should be default)<br>
<code> · VTK_RENDERING_BACKEND=OpenGL2</code> (should be default)<br>
<code> · VTK_SMP_IMPLEMENTATION_TYPE=Sequential</code><br>
<br>
You can also enable optional pieces, e.g. ffmpeg. I also had hdf5 installed through homebrew, but I don't think it was necessary to change anything in cmake.<br><br>
Note, if you've correctly installed OSPRay for OSX, you can use the following:<br><br>
<code> · PARAVIEW_USE_OSPRAY=ON</code><br>
<code> · VTK_SMP_IMPLEMENTATION_TYPE=TBB</code><br>
<br>
Then, press 'c' to configure (wait a minute) and then press 't' for advanced mode and we'll edit some more CMake flags:<br><br>
<code> · PYTHON_INCLUDE_DIR=/usr/local/Frameworks/Python.framework/Versions/Current/include/python2.7 </code><br>
<code> · PYTHON_LIBRARY=/usr/local/Frameworks/Python.framework/Versions/Current/lib/libpython2.7.dylib </code><br><br>
And if you're doing the optional OSPRay build, also set:<br><br>
<code> · OSPRAY_INSTALL_DIR=/opt/local/lib</code><br><br>
You may also have to set up the paths for the TBB debug *.dylibs stored
in /opt/local/lib (TBB_LIBRARY_DEBUG, TBB_LIBRARY_MALLOC_DEBUG, TBB_MALLOC_LIBRARY_DEBUG, and/or TBB_MALLOC_PROXY_LIBRARY_DEBUG), but on my environment it found those automatically.<br>
<br>
Press 'c' again, which fills in some more paths, and then press 'c' one more time and things should be ready to press 'g' to generate and exit.<br><br>
<h4>b) Build</h4>
Now you can start the compilation process by entering the following command, where <code>N</code> is the number of available cores on your system (this will take a <b>LONG</b> time):<br><br>
<code>$ make -jN</code><br><br>
<h4>c) Installation</h4>
Once the build is finished, we recommend that you do <strong>not</strong> use <code>make install</code>. We will work directly in the build directory for the source tree instead of trying to package up a MacOS .app file in <code>/Applications</code>. We'll need to manually make a directory for this:<br><br>
<code>$ mkdir ~/ttk/ParaView-v5.4.1/build/bin/paraview.app/Contents/MacOS/plugins</code><br>
</p>
<p>
<h3>6. Configuring, building and installing TTK</h3>
<h4><a name="ttkConfig">a)</a> Configuration</h4>
To enter the configuration menu of TTK's build, enter the following commands:<br><br>
<code>$ cd ~/ttk/ttk-0.9.3/</code><br>
<code>$ mkdir ttk_install</code> (for installing standalone apps)<br>
<code>$ mkdir build</code><br>
<code>$ cd build</code><br>
<code>$ ccmake ..</code><br><br>
The configuration window opens. Press 'c' to configure, and you'll see that it cannot yet find ParaView. First, we'll fix this:<br><br>
<code> · ParaView_DIR=~/ttk/ParaView-v5.4.1/build/</code><br><br>
Press 'c' again to configure (you can ignore the warnings). Also note that <code>VTK_DIR</code> should automatically be set to the homebrew installation of VTK (<code>/usr/local/lib/cmake/vtk-7.1</code>). Next, change:<br><br>
<code> · CMAKE_BUILD_TYPE=Release</code><br>
<code> · CMAKE_INSTALL_PREFIX=~/ttk/ttk-0.9.3/ttk_install</code> (this is where standalone apps and other TTK componentns are installed)<br>
<code> · TTK_PLUGIN_INSTALL_DIR=<br>~/ttk/ParaView-v5.4.1/build/bin/paraview.app/Contents/MacOS/plugins"</code> (this is where ParaView plugins are installed)<br>
<br>
Note that you can enable building certian portions of TTK at this time
as well by switching the flags associated with each (e.g. TTK_BUILD_PARAVIEW_PLUGINS, TTK_BUILD_STANDALONE_APPS, etc.).
Press 'c' to reconfigure (again takes a few seconds) and then press 'g' to generate.<br><br>
<h4>b) Build</h4>
Now you can start the compilation process by entering the following command, where <code>N</code> is the number of available cores on your system:<br><br>
<code>$ make -jN</code><br><br>
<h4>c) Installation</h4>
Once the build is finished, enter the following command to install your build of TTK into your ParaView installation:<br><br>
<code>$ make install</code><br><br>
Note that in addition to copying the TTK plugins to your ParaView installation (<code>TTK_PLUGIN_INSTALL_DIR</code>), the above command also installed a collection of standalone TTK programs to <code>CMAKE_INSTALL_PREFIX</code>. These can be used outside of ParaView, either as command line tools or VTK-based graphical user interfaces. To list them:<br><br>
<code>$ ls CMAKE_INSTALL_PREFIX/bin/*Cmd</code><br>
<code>$ ls CMAKE_INSTALL_PREFIX/bin/*Gui</code><br><br>
Replacing <code>CMAKE_INSTALL_PREFIX</code> with what we used above.<br><br>
Finally, to make sure the example data files are included in the right path, you have to manually copy the example data into the ParaView .app as well:<br><br>
<code>$ cd ~/ttk/ttk-0.9.3/paraview/patch/data</code><br>
<code>$ mkdir ~/ttk/ParaView-v5.4.1/build/bin/paraview.app/Contents/data</code><br>
<code>$ cp * ~/ttk/ParaView-v5.4.1/build/bin/paraview.app/Contents/data</code><br>
<br>
</p>
<p>
<h3>7. Checking your TTK installation</h3>
If you applied all the above steps successfully (including step 4), you can now open a terminal and type the following command to load your TTK-patched ParaView:<br><br>
<code>$ cd ~/ttk/ParaView-v5.4.1/build/bin/paraview.app/Contents/MacOS/</code><br><br>
<code>$ ./paraview</code><br><br>
At this point, everything from the standard installation procedure should be accessible. Congrats!
</p>
<p>
Now, please visit our <a href="tutorials.html">tutorial</a> page to watch video
tutorials showing how to use TTK with ParaView with concrete examples and how
to
use it from your own Python or C++ code or how to extend TTK by writing up your
own module!
</p>
</div>
</div>
</div>
<hr>
<!-- Footer -->
<footer>
<div class="container">
<div class="row">
<div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1">
<p class="copyright text-muted">
Contact: <a href="mailto:topology.tool.kit@gmail.com">
topology.tool.kit@gmail.com</a><br>
Updated on January 11, 2018.</p>
</div>
</div>
</div>
</footer>
<!-- jQuery -->
<script src="vendor/jquery/jquery.min.js"></script>
<!-- Bootstrap Core JavaScript -->
<script src="vendor/bootstrap/js/bootstrap.min.js"></script>
<!-- Contact Form JavaScript -->
<script src="js/jqBootstrapValidation.js"></script>
<script src="js/contact_me.js"></script>
<!-- Theme JavaScript -->
<script src="js/clean-blog.min.js"></script>
</body>
</html>