-
Notifications
You must be signed in to change notification settings - Fork 17
/
Copy pathinstallation-osx-0.9.8.html
748 lines (600 loc) · 30.8 KB
/
installation-osx-0.9.8.html
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
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
<!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">MacOS 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>
If you are an advanced user and you do not wish to install ParaView (TTK's
main user interface), you
still
have the possibility to install TTK without ParaView support (although we
highly recommend to activate it).<br>
In that case, simply
download TTK as described in section 1, install the dependencies as detailed
in
section 2 and finally, directly jump to section 6 (<i>"Configuring, building
and installing TTK"</i>). <br>
Examples showing how to use TTK libraries from your
own VTK code can be found
<a target="new"
href="https://github.com/topology-tool-kit/ttk/tree/dev/examples/vtk-c%2B%2B"
>on this page</a>.<br><br>
If you are an advanced user and you do not even wish to install VTK, you still
have the possibility to install TTK without VTK support (although we
highly recommend to activate it).<br>
In that case, simply download TTK as described in section 1, install the
<b>optional</b> dependencies as detailed in
section 2 and finally, directly jump to section 6 (<i>"Configuring, building
and
installing TTK"</i>). <br>
Examples showing how to use TTK libraries from your own
C++ code can be found
<a target="new"
href="https://github.com/topology-tool-kit/ttk/tree/dev/examples/c%2B%2B"
>on this page</a>.<br>
<br>
<b>Most users will want to activate TTK's ParaView support.</b><br><br>
This page describes installing TTK 0.9.8 on MacOS, using Mojave 10.14.6 and
ParaView 5.6.1. The key differences from the linux installation involve how
ParaView is compiled, installing certain dependencies, and setting up some of
the paths for MacOS. The following assumes that the target is to compile with
MacOS clang and uses homebrew for dependencies, including python3<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 MacOS: <br>
· <a href="installation-osx-0.9.7.html">TTK 0.9.7
with ParaView 5.6.0 on MacOS Mojave</a>.<br>
· <a href="installation-osx-0.9.7-highsierra.html">TTK 0.9.7
with ParaView 5.6.0 on MacOS High Sierra</a>.<br>
· <a href="installation-osx-0.9.6.html">TTK 0.9.6
with ParaView 5.5.2</a>.<br>
· <a href="installation-osx-0.9.5.html">TTK 0.9.5
with ParaView 5.5.0</a>.<br>
· <a href="installation-osx-0.9.4.html">TTK 0.9.3 (and 0.9.4)
with ParaView 5.4.1</a>.<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.6&type=source&os=Sources&downloadFile=ParaView-v5.6.1.tar.xz"
target="new">
ParaView 5.6.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>
<h4>a) Required Dependencies</h4>
Using <a href="https://brew.sh/">homebrew</a>, install:
<ul>
<li> cmake (tested with 3.15.2) </li>
<li> qt (tested with 5.13.0) </li>
<li> python (tested with 3.7.4)<br/>
Note: We use python3 instead of MacOS's default python2. To map the default executable for python, please add <code>export PATH="/usr/local/opt/python/libexec/bin/:$PATH"</code> to either your <code>~/.bashrc</code>, <code>~/.bash_profile</code>, or other shell startup script.</li>
<li> vtk (tested with 8.2.0_1)<br/>
This required installing certain vtk dependencies, which do install
python2 (so take care), including:
<ul>
<li>pyqt (tested with version 5.10.1_1</li>
<li>sip (tested with version 4.19.8_12)</li>
</ul>
Installing vtk will also install hdf5 as a dependency (that ParaView can make use of).
</ul>
Altogether, this required the following sequence of commands:<br><br>
<code>$ brew install cmake qt python vtk</code><br><br>
<h4>b) Optional Dependencies</h4>
<h5>(i) ffmpeg:</h5>
Using homebrew, one can install optional packages for ParaView features with homebrew:
<ul>
<li> ffmpeg (tested with 4.1.4_1) </li>
</ul>
Using the command: <code>$ brew install ffmpeg</code><br><br>
<h5>(ii) OpenMP:</h5>
Using homebrew, one can also install OpenMP support for TTK with homebrew:
<ul>
<li> libomp (tested with 8.0.1)</li>
</ul>
Using the command: <code>$ brew install libomp</code><br><br>
<h5>(iii) OSPRay:</h5>
And, in addition, one can install OSPRay and it's dependencies using:
<ul>
<li> open-mpi (tested with 4.0.1_2):<br>
<code>$ brew install open-mpi</code> </li>
<li>Download and expand ospray-1.8.5.x86_64.macosx.tar.gz from <a href="http://www.ospray.org/getting_ospray.html">http://www.ospray.org/getting_ospray.html</a> (you will find it under <a href="https://github.com/ospray/OSPRay/releases">Old Releases</a>. Newer versions of ospray are not yet compatible with TTK 0.9.8's CMake structure), to install:
<ul>
<li>Copy lib/cmake and lib/libospray* to /opt/local/lib</li>
<li>Copy include/* to /opt/local/include</li>
<li>Copy scripts to /opt/local/share/OSPRay-1.8.5</li>
<li>Copy bin and doc to /Applications/OSPRay</li>
</ul>
You may need to create some of the destination directories before copying. The above steps manually do the work that the *.dmg file does.
</li>
<!--
<li>Download and expand ospray-1.8.5.x86_64 from <a href="http://www.ospray.org/getting_ospray.html">http://www.ospray.org/getting_ospray.html</a>, to install:
<ul>
<li>Copy the files in Applications to /Applications</li>
<li>Copy the files in opt to /opt, including local/include, local/lib, and local/share</li>
</ul>
This .dmg file does not manually copy anything, but rather just presents you with the files to copy on your own.
</li>
-->
<li>Download and unpack embree-3.5.2.x86_64.pkg from <a href="https://embree.github.io/downloads.html">https://embree.github.io/downloads.html</a> (this installs in /opt/local and /Applications).</li>
<li>Download and unpack tbb2019_20190605oss_mac.tgz from <a
href="https://github.com/01org/tbb/releases">https://github.com/01org/tbb/releases</a>. After expanding the .tgz, to install:
<ul>
<li>Copy lib/libtbb* to /opt/local/lib</li>
<li>Copy cmake/* to /opt/local/lib/cmake/tbb</li>
<li>Copy include/tbb to /opt/local/include</li>
</ul>
You may need to create some of the destination directories before copying.</li>
</ul>
After doing all of the above, you'll likely want to make sure that your command line 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>.<br><br>
<h5>(iv) TTK optional dependencies:</h5>
Finally, in order to enjoy the complete set of TTK features, we also recommend installing the following, optional TTK dependencies:
<ul>
<li><a target="new" href="http://eigen.tuxfamily.org/">eigen</a> (for scalar field design) tested with version 3.3.7 on homebrew:<br>
<code>$ brew install eigen</code></li>
<li><a target="new" href="https://www.graphviz.org/">graphviz</a> (for graph drawing features) tested with version 2.40.1_1 on homebrew:<br>
<code>$ brew install graphviz</code></li>
<li><a target="new" href="https://scikit-learn.org/stable/index.html">scikit-learn</a> for Python3 (for data reduction features, version 0.19.0 or later). Support is still experimental. We tested with version 0.21.3, installed for python3 with pip:<br>
<code>$ pip install -U scikit-learn</code></li>
<li><a target="new" href="https://github.com/yixuan/spectra/archive/v0.8.1.tar.gz">Spectra</a> (for the computation of the eigenfunctions of the Laplace-Beltrami operator) tested with version 0.8.1 and <a href="https://spectralib.org/">installed from source (see instructions)</a>.</li>
<li><a href="https://www.sqlite.org/" target="new">sqlite</a> (for cinema query features), tested with version 3.29.0 on homebrew:<br>
<code>$ brew install sqlite</code></li>
<li><a href="https://github.com/LLNL/zfp/archive/master.zip" target="new">ZFP</a> (for advanced compression support, version 0.5.4 or later) tested with version 0.5.5 and <a href="https://github.com/LLNL/zfp">installed from source (see instructions)</a>,</li>
<li><a href="https://zlib.net/" target="new">zlib</a> (for further compression support) tested with version 1.2.11 on homebrew:<br>
<code>$ brew install zlib</code></li>
</ul>
</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.6.1.tar.gz ~/ttk/</code><br>
<code>$ mv ~/Downloads/ttk-0.9.8.tar.gz ~/ttk/</code><br>
<code>$ cd ~/ttk</code><br>
<code>$ tar xvzf ParaView-v5.6.1.tar.gz</code><br>
<code>$ tar xvzf ttk-0.9.8.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.6.1.tar.gz</code><br>
<code>$ rm ttk-0.9.8.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.8/paraview/patch</code><br>
<code>$ ./patch-paraview-5.6.1.sh ~/ttk/ParaView-v5.6.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.6.1/</code><br>
<code>$ mkdir build</code><br>
<code>$ cd build</code><br>
<code>$ ccmake ..</code> (on homebrew cmake there is no <code>cmake-gui</code>,
although you can install this separately from <a
href="https://cmake.org/download/">https://cmake.org/download/</a>)<br><br>
Then, press 'c' to configure and we'll edit some CMake flags (you may
have to press 't' to find them):<br>
<code> · CMAKE_BUILD_TYPE=Release</code><br>
<code> · PARAVIEW_ENABLE_PYTHON=ON</code><br>
<code> · VTK_PYTHON_VERSION=3</code><br>
<code> · VTK_SMP_IMPLEMENTATION_TYPE=Sequential</code> (the default)<br>
<br>
You can also enable optional pieces, including:
<h5>(i) ffmpeg:</h5>
<code> · PARAVIEW_ENABLE_FFMPEG=ON</code><br>
<br>
<h5>(ii) OpenMP as the SMP implementation:</h5>
At this time, we do not recommend building ParaView 5.6.1 with OpenMP,
even though TTK can take advantage of OpenMP for some of its features.
For parallelism in ParaView, please use TBB.<br>
<br>
<!--
<code> · VTK_SMP_IMPLEMENTATION_TYPE=OpenMP</code> (changed from the default
"Sequential")<br>
Note, after hitting 'c' to configure, cmake will require you to set additional flags, e.g. <code>OpenMP_CXX_FLAGS</code>, <code>OpenMP_CXX_LIBRARY</code>, <code>OpenMP_C_FLAGS</code>, <code>OpenMP_C_LIBRARY</code>. If you are interested in using OpenMP, we do not recommend using ccmake, but instead use the cmake command below.<br>
<br>
-->
<h5>(iii) OSPRay (which requires TBB):</h5>
<code> · PARAVIEW_USE_OSPRAY=ON</code><br>
<code> · OSPRAY_INSTALL_DIR=/opt/local/lib</code> (this variable will show up and need to be set after setting <code>PARAVIEW_USE_OSPRAY=ON</code> and hitting 'c' to reconfigure.)<br>
<br>
<h5>(iv) TBB as the SMP implementation (which isn't necessary, but if you do not want to use OpenMP and you've installed OSPRay, then you have TBB too):</h5>
<code> · VTK_SMP_IMPLEMENTATION_TYPE=TBB</code> (changed from the default
"Sequential")<br>
Note, hitting 'c' to configure, cmake will also set <code>VTKm_ENABLE_TBB=ON</code> and should find all include dirs and libraries for TBB in /opt/local if you've installed it correctly.<br>
<br>
After specifying the above options, press 'c' to configure (wait a minute) and then press 't' for advanced mode to double check the above paths and/or fill in any flags that did not appear the first time. You may need to press 'c' again, which fills in some more paths. Once cmake is finished configuring, you should finalize everything by pressing 'g' to generate and exit.<br><br>
<br><br>
If you prefer to just run <code>cmake</code> as opposed to <code>ccmake</code> or <code>cmake-gui</code>, the following summarizes five possible installations:
<h5>Basic (No Optional Dependencies)</h5>
<code>$ cmake \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DPARAVIEW_ENABLE_PYTHON=ON \<br>
-DVTK_PYTHON_VERSION=3 \<br>
..
</code><br>
<h5>(i) Sequential + ffmpeg</h5>
<code>$ cmake \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DPARAVIEW_ENABLE_PYTHON=ON \<br>
-DVTK_PYTHON_VERSION=3 \<br>
-DPARAVIEW_ENABLE_FFMPEG=ON \<br>
-DVTK_SMP_IMPLEMENTATION_TYPE=Sequential \<br>
..
</code><br>
<!--
<h5>(iii) OpenMP + ffmpeg</h5>
<code>$ cmake \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DPARAVIEW_ENABLE_PYTHON=ON \<br>
-DPARAVIEW_ENABLE_FFMPEG=ON \<br>
-DVTK_SMP_IMPLEMENTATION_TYPE=OpenMP \<br>
-DOpenMP_CXX_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include" \<br>
-DOpenMP_CXX_LIB_NAMES=omp \<br>
-DOpenMP_C_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include" \<br>
-DOpenMP_C_LIB_NAMES=omp \<br>
-DOpenMP_omp_LIBRARY=/usr/local/opt/libomp/lib/libomp.dylib \<br>
..
</code><br>
-->
<h5>(i),(iii),(iv) TBB + ffmpeg + OSPRay</h5>
<code>$ cmake \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DPARAVIEW_ENABLE_PYTHON=ON \<br>
-DVTK_PYTHON_VERSION=3 \<br>
-DPARAVIEW_ENABLE_FFMPEG=ON \<br>
-DVTK_SMP_IMPLEMENTATION_TYPE=TBB \<br>
-DPARAVIEW_USE_OSPRAY=ON \<br>
-DOSPRAY_INSTALL_DIR=/opt/local/lib \<br>
..
</code><br>
<!--
<h5>(v) OpenMP + ffmpeg + OSPRay</h5>
<code>$ cmake \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DPARAVIEW_ENABLE_PYTHON=ON \<br>
-DPARAVIEW_ENABLE_FFMPEG=ON \<br>
-DVTK_SMP_IMPLEMENTATION_TYPE=OpenMP \<br>
-DOpenMP_CXX_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include" \<br>
-DOpenMP_CXX_LIB_NAMES=omp \<br>
-DOpenMP_C_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include" \<br>
-DOpenMP_C_LIB_NAMES=omp \<br>
-DOpenMP_omp_LIBRARY=/usr/local/opt/libomp/lib/libomp.dylib \<br>
-DPARAVIEW_USE_OSPRAY=ON \<br>
-DOSPRAY_INSTALL_DIR=/opt/local/lib \<br>
..
</code><br>
-->
<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>. <br><br>
Finally, to enable ParaView and pvpython to find the TTK plugins we will build, we recommend setting the environment variable <code>PV_PLUGIN_PATH</code> to be the location where you choose to install TTK. Note that this is different from past installations where we manually installed TTK in the build directory. Instead, these instructions will assume that you will install TTK's plugins in <code>/usr/local/lib/plugins</code> (the cmake variable <code>TTK_INSTALL_PLUGIN_DIR</code> will be set accordingly in the next step).<br><br>
To set this environment variable permanently, we recommend editing whatever file you normally configure these in (e.g. <code>~/.bash_profile</code>) and adding the line:<br><br>
<code>export PV_PLUGIN_PATH="/usr/local/lib/plugins"</code><br><br>
Note that, by default, our installation of ParaView will search for plugins in <code>~/ttk/ParaView-v5.6.1/build/bin/paraview.app/Contents/MacOS/plugins</code>. And, by default, our installation of pvpython will search fo plugins in <code>~/ttk/ParaView-v5.6.1/build/bin/plugins</code>. Setting <code>PV_PLUGIN_PATH</code> overrides this so that both can search for TTK in a common location. Users may want to choose to use a different location that <code>/usr/local/lib/plugins</code>, although this path is consistent with where the Linux installation of TTK installs them.<br><br>
For more information, see <a href="https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Using_Plugins">https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Using_Plugins</a>.
</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.8/</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.6.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-8.2</code>). Next, change:<br><br>
<code> · CMAKE_BUILD_TYPE=Release</code><br>
<code> · CMAKE_INSTALL_PREFIX=~/ttk/ttk-0.9.8/ttk_install</code
><br>
(this is where standalone apps and
other TTK components are installed)<br>
<code> · TTK_INSTALL_PLUGIN_DIR=/usr/local/lib/plugins</code><br>
(this is where ParaView plugins are installed)<br>
<code> · PYTHON_NUMPY_INCLUDE_DIR=/usr/local/lib/python3.7/site-packages/numpy/core/include</code><br>
(this should be where
homebrew's python3 installs numpy, which our CMake script does not yet
detect)<br>
<br>
If you are an advanced user and you do not wish to activate TTK's ParaView
support, set the CMake variable <code>TTK_BUILD_PARAVIEW_PLUGINS</code> to
<code>OFF</code>.
Examples showing how to use TTK libraries from your
own VTK code can be found
<a target="new"
href="https://github.com/topology-tool-kit/ttk/tree/dev/examples/vtk-c%2B%2B"
>on this page</a>.<br>
Press 'c' to reconfigure (again takes a few seconds) and then press 'g' to
generate.<br><br>
If you are an advanced user and you do not even wish to activate TTK's VTK
support, set the CMake variable
<code>TTK_BUILD_VTK_WRAPPERS</code> to <code>OFF</code>.
Examples showing how to use TTK libraries from your own
C++ code can be found
<a target="new"
href="https://github.com/topology-tool-kit/ttk/tree/dev/examples/c%2B%2B"
>on this page</a>.<br>
Press 'c' to reconfigure (again takes a few seconds) and then press 'g' to
generate.<br><br>
<!--Note that you can enable building certain 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.). -->
Note that if you are working with optional dependencies, you may also need to set certain CMake variables, including:
<ul>
<li>eigen should be automatically detected.</li>
<li>graphviz should be automatically detected.</li>
<li>scikit-learn is disabled by default on MacOS, but can be enabled by setting <code>TTK_ENABLE_SCIKIT_LEARN</code> to <code>ON</code>.</li>
<li>Depending on where you installed it, to enable Spectra set the variable <code>SPECTRA_INCLUDE_DIR</code> to the <code>include</code> subdirectory of where you installed Spectra.</li>
<li>sqlite should be automatically detected.</li>
<li>Depending on where you installed it, you may have to set <code>ZFP_DIR</code> to the directory where you built ZFP.</li>
<li>zlib should be automatically detected.</li>
</ul>
<br>
Finally, if you'd like to try out OpenMP (again, experimental), you would
add:<br>
<code> · TTK_ENABLE_OPENMP=ON</code><br>
<code> · OpenMP_CXX_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include"</code><br>
<code> · OpenMP_CXX_LIB_NAMES=omp</code><br>
<code> · OpenMP_omp_LIBRARY=/usr/local/opt/libomp/lib/libomp.dylib</code><br>
<br>
Press 'c' to reconfigure (again takes a few seconds) and then press 'g' to
generate.<br><br>
If you prefer to just run <code>cmake</code> as opposed to <code>ccmake</code>
or <code>cmake-gui</code>, the following summarizes the two possible
installations:
<h5>(i) Basic TTK</h5>
<code>$ cmake \<br>
-DParaView_DIR=~/ttk/ParaView-v5.6.1/build/ \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DCMAKE_INSTALL_PREFIX=~/ttk/ttk-0.9.8/ttk_install \<br>
-DTTK_INSTALL_PLUGIN_DIR=/usr/local/lib/plugins \<br>
-DPYTHON_NUMPY_INCLUDE_DIR=/usr/local/lib/python3.7/site-packages/numpy/core/include \<br>
..
</code><br>
<h5>(ii) TTK + OpenMP</h5>
<code>$ cmake \<br>
-DParaView_DIR=~/ttk/ParaView-v5.6.1/build/ \<br>
-DCMAKE_BUILD_TYPE=Release \<br>
-DCMAKE_INSTALL_PREFIX=~/ttk/ttk-0.9.8/ttk_install \<br>
-DTTK_INSTALL_PLUGIN_DIR=/usr/local/lib/plugins \<br>
-DPYTHON_NUMPY_INCLUDE_DIR=/usr/local/lib/python3.7/site-packages/numpy/core/include \<br>
-DTTK_ENABLE_OPENMP=ON \<br>
-DOpenMP_CXX_FLAGS="-Xclang -fopenmp -I/usr/local/opt/libomp/include" \<br>
-DOpenMP_CXX_LIB_NAMES=omp \<br>
-DOpenMP_omp_LIBRARY=/usr/local/opt/libomp/lib/libomp.dylib \<br>
..
</code><br>
<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_INSTALL_PLUGIN_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.8/paraview/patch/data</code><br>
<code>$ mkdir -p ~/ttk/ParaView-v5.6.1/build/bin/paraview.app/Contents/share/paraview-5.6/examples</code><br>
<code>$ cp * ~/ttk/ParaView-v5.6.1/build/bin/paraview.app/Contents/share/paraview-5.6/examples</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.6.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:[email protected]">
[email protected]</a><br>
Updated on August 21, 2019.</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>