Both projects have are no longer maintained since the creation of VTK-m,
so remove them from the Accelerator directory.

I used perl regex to find any groups that spanned a protected: or
private: access specifier.

generated via:
cd $VTKSRC
perl Utilities/Doxygen/doc_header2doxygen.pl --to ~/tmp/vtkheaders .
cp -r ~/tmp/vtkheaders/* .

The current dependency relationship in vtk is unclear and misleading.
This MR tries to rewrite them based on header files inclusion of headers
and source files in each module. Corner cases are considered and
modules are sorted in alphabetical order to facilitate future reference.
See details in my gitlab python based script project. In future we can continue
using this script to clean the VTK Dependency easily from
time to time.

This is a fix for:
vtk/vtk#14310

Windows applications that run for a long time report that rendered
objects do not change. This is because the modified time on a Windows
system is 32 bits. This causes overflows that defeat the modified time
mechanism. This patch defines a new type, vtkMTimeType that is 64
unsigned integer regardless of the architecture.

A mechanism to provide backward compatibility is introduced. The
preprocessor define "VTK_HAS_MTIME_TYPE" can be used in applications
that must build against VTK versions that use the "unsigned long" type
for MTime's.

Methodology used to find MTime occurences:
1) Identify files as follows:
   git grep "unsigned long" | grep ime | cut -d":" -f1,1 | sort | uniq
2) Hand edit each of those files replacing "unsigned long" with
   "vtkMTimeType" where appropriate.
3) Temporarily change typedef for vtkMTimeType to "double" to detect
   missing conversions

Find/replace of:

;[ ]*//\s*Not implemented[\.]*
to
 VTK_DELETE_FUNCTION;

To catch a few remaining ones missed by previous greps.

Manually reverted changed files in VPIC and KWSys folders, and a couple other of places.

vtk(.*)\(const vtk\1&\);\s*//\s*Not implemented[\.]*
to
vtk\1(const vtk\1\&) VTK_DELETE_FUNCTION;

vtk(.*)\(const vtk\1 &\);\s*//\s*Not implemented[\.]*
to
vtk\1(const vtk\1 \&) VTK_DELETE_FUNCTION;

vtk(.*)\( const vtk\1 & \);\s*//\s*Not implemented[\.]*
to
vtk\1( const vtk\1 \& ) VTK_DELETE_FUNCTION;

vtk(.*)\( const vtk\1& \);\s*//\s*Not implemented[\.]*
to
vtk\1( const vtk\1\& ) VTK_DELETE_FUNCTION;

vtk(.*) \(const vtk\1&\);\s*//\s*Not implemented[\.]*
to
vtk\1 (const vtk\1\&) VTK_DELETE_FUNCTION;

(operator\s*=.*);\s*//\s*Not\s*implemented[\.]*
to
\1 VTK_DELETE_FUNCTION;

After that, this finds basically nothing:

operator.*implemented

then manually reverted changed files in VPIC and KWSys folders.

Made them like others, so that they'll match future greps.

Kitware Robot authored May 24, 2016 and David Gobbi committed May 25, 2016

Perl was used to remove all the BTX and ETX markers from the code.
The specific command that was run on all "vtk*.h" files was this:
    perl -0777 -i -pe 's/(\n* *\/\/ *[BE]TX *\n+)+/\n\n/g'

This regex replaces each BTX/ETX line, plus any leading or trailing
blank lines, with a single blank line.

SafeDownCast performs a series of virtual calls and string comparisons,
which is quite slow, especially when used in worker functions.

vtkArrayDownCast will switch between SafeDownCast and the more
efficient FastDownCast (only available for common vtkAbstractArray
subclasses) depending on whether or not FastDownCast is defined for
the specific array type.

Kitware Robot authored Mar 08, 2016 and Dan Lipsa committed Mar 08, 2016

Code extracted from:

    https://gitlab.kitware.com/third-party/proj.git

at commit 41bdf05361007f8c5186f3df9944d86bb273ed13 (for/vtk).

The way algorithms were updated (made to execute) with
request meta-data (such as update extent) was very error
prone and counter-intuitive. Added new methods to make
updating with meta-data easier. I also deprecated a number
of methods to set request meta-data. This will encourage
developers to migrate to the new API which is less error-
prone.

Some likely copy-paste and were real overruns,
others it was the method declarations that were wrong.

Threw in an assert for good measure.

This makes the python wrappers ignore WRAP_EXCLUDE, and instead use
the new property WRAP_EXCLUDE_PYTHON that excludes fewer classes.
The WRAP_SPECIAL flag, which used to act as a whitelist for python,
has been removed.

Because this change causes classes to be wrapped in python by default,
some third-party VTK packages might break until they modify their own
CMakeLists.txt files to add WRAP_EXCLUDE_PYTHON where necessary.

Change-Id: If625f69914513507151659a3a6161d987ad84591

Used the following command:

find . \( -iname *.h -and -type f \) -exec perl -pi -w -e 's/__vtk(.*)_h/vtk$1_h/g;' {} \;

Fixes many, but not all, clang -Wreserved-id-macro warnings.

Change-Id: I694ff053cb204c70e37b261296f496064d91fc07

Used the following command:

find . \( -iname *.in -and -type f \) -exec perl -pi -w -e 's/__vtk(.*)_h/vtk$1_h/g;' {} \;

Fixes many, but not all, clang -Wreserved-id-macro warnings.

Change-Id: I86db91ad530c203347f2b0dfd29c31f843c3f2b7

Change-Id: I76848acf2f0939f63df6c3194b302eebd6a68009

Did this for cxx files where another vtk include was already
using the "" style.  I find this is more correct, especially
for implementation files.

Change-Id: I632178a9af13991ccba96bfaabf5ccc4bfea3c18

Change-Id: Id4bbf39ead9e18972e831f7323c8369b1bb08e80

Embedded in vtkDaxContour algorithm. Automatically switches to marching
tetrahedra when doing contour on unstructured grid made up of only
tetrahedra.

Change-Id: Ia3cca64666b1c246203b55fbb6b3ec3b5ea0ad5d

The Dax contour filter can now interpolate the values of point fields so
that the output will have field information.

Change-Id: I9bd71d05ce255054d2e5d0390577828c64def259

We want our filter to behave more like the more modern vtkContourFilter
than the old vtkMarchingCubes. Besides, we would like our Dax filter to
handle contouring in cells other than just cubes.

Change-Id: Ic18b1570835797ed042da626ef8364def96e08b5

Change-Id: I4fdb88c0700e5ca73fd6eba087a230c3cbacdba8

This will allow kits to gather all of the required libraries to link
since the modules themselves won't "exist" to link anything when kits
are enabled.

Change-Id: Ic73220c7b97e17a5fbc0aa6c0f7a5e5a61dc6bef

Change-Id: I6b56a2b3f643be8e726b30444c5c103c9d717925

Change-Id: I289624b773f148eb530e58c745f4150297e20170

The superclass still has the problem of only getting the active
scalars rather than the input array. It would be good if this were
fixed. It might be even better if vtkDaxMarchingCubes inherited from
vtkContour instead. This class both handles the input array correctly
and has better implementations of the contour algorithm.

Change-Id: Iac333cb5019b28f7fb4bf2fb62e28b898593491f

In commit cd4fc15a (Rewrite the testing macros, 2014-03-14)
the vtk_test_mpi_executable() helper was introduced to add
MPI tests.  It depends on the vtk_mpi_link() helper in the
vtkMPI module.  Include the latter in all test CMakeLists.txt
files that add MPI tests.

Change-Id: Ifecc7c6b1bf856a8f66905bfb2d69e22b5de3aac

Change-Id: I5f19b101063e1a25d4f5db5c4356ce5efffbd90d

Change-Id: If92879d67d11dfc5965ef42a8c173539801b3c98

Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

Change-Id: If03194e9df8258feb72fa2ed53f263eacd4891d5