GitLab

Change-Id: I80d4dbda38c7a6d83d6ba3fadeb81cce1154a1b1

To work with the new pipeline changes.

Change-Id: Ic5c8ac86026999f79924d8e61b10fbcb18286bb8

The XML readers and writers, both parallel and serial, now work
with the pipeline changes. Now, all writers work with pieces
even though the structured ones can handle asking for a sub-
extent.

Change-Id: I9f757ba12a3b9fb84e141506dacadad608eb8b99

Refactoring the way VTK goes between piece and structured
extents. Before, extent translators were used when the pipeline
moved from structured to unstructured data converting piece
request to extent request. This caused many problems with filters
that altered extents, mainly a lot of redundant IO due to
repartitioning of different extents. This became extremely
cumbersome to manage when running distributed. The new behavior
pushes the extent translation all to way to the readers and
only when readers are able to read a subset. This works much
better. The only downside is that filters need to be able to
handle data extents different than update extents. Most filters
can do this but many imaging filters cannot. Those that are
needed in parallel will have to be updated.

As part of this work, I also removed MAXIMUM_NUMBER_OF_PIECES
and added CAN_HANDLE_PIECE_REQUEST. MAXIMUM_NUMBER_OF_PIECES had
reduced to being a boolean. 1 for serial sources, -1 for parallel
...

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: I6546ff164baca86afb1a73b896dd10b1bce2c005

Change-Id: I5f19b101063e1a25d4f5db5c4356ce5efffbd90d

Change-Id: If92879d67d11dfc5965ef42a8c173539801b3c98

Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

Change-Id: I7fccf57a0bfaa524d31f18d3e74449ca5990087a

FindNetCDF.cmake adapted from
  https://github.com/jedbrown/cmake-modules/blob/master/FindNetCDF.cmake

Change-Id: I5e790941624e4ab9a37f46687a18a3fd046be6de

Now that the XML shader stuff is gone the vtkIOImage library isn't
needed either.

Change-Id: I64adeabd461c5adfb3793450576460aa477bfab7

Since commit 6383648d (COMP: Set CMake Policy CMP0022 to NEW,
2013-09-11) we tell CMake >= 2.8.12 to use the INTERFACE_LINK_LIBRARIES
property to define the link interface of libraries.  Populate it for
vtkNetCDF_cxx libraries by using target_link_libraries with LINK_PUBLIC.

Also fix the vtkIOParallel module implementation to link to
vtkNetCDF_cxx because its sources include netcdf headers.

Change-Id: I2541a05f30311fca4094cfebd2b8fc618fa0eb5e

Note both the change from "" to <> and from the C to
the C++ header name.

Change-Id: I2c547e12b34b7a2dfc99e2b00af56d85e5c63104

Add to the Testing/Data directory ExternalData content links mirroring
the content and layout we use from the VTKData/Data directory.

Add a CMake/vtkLegacyData.cmake module, included from CMakeLists.txt and
Testing/External/CMakeLists.txt, to call ExternalData_Expand_Arguments
for all data directories added from VTKData/Data.  This will bulk-fetch
all test input data currently used by tests of any module, enabled or
not.  We can make the DATA{} references more granular later.

Add a VTK_TEST_DATA_DIR variable to refer to the directory we tell the
ExternalData module to populate the real data files.  Replace references
to VTK_DATA_ROOT in test command lines (after -D) with references to
VTK_TEST_DATA_DIR.  Drop the VTK_DATA_ROOT CMake option and stop using
the VTKData repository.

Remove the TESTING_DATA option from the vtk_add_test_cxx API and remove
the VTK_DATA_ROOT option from the vtk_add_test_mpi API since all test
input data are now handled through ExternalData and Testing/Data content
links.

Change-Id: Id02490b76ea2e161b9038188264a4830485039d8

Add a Testing/Data directory with ExternalData content links mirroring
the content and layout we use from the VTKLargeData/Data directory.
Add a VTK_USE_LARGE_DATA option to enable tests using such data.

Call ExternalData_Expand_Arguments in */*/Testing/Cxx/CMakeLists.txt for
tests that reference these data files in order to tell the ExternalData
module to populate a ExternalData/Testing/Data directory in the build
tree.  Pass the ExternalData/Testing directory in the build tree as the
"-D" data directory option to tests using these data so that they can
find the files where ExternalData puts them at build time.

In the vtk_add_test_* API replace the LARGE_DATA options with a new
TESTING_DATA option to indicate that a test uses the directory
ExternalData/Testing/Data populated by ExternalData from the
Testing/Data source directory.

Drop VTK_LARGE_DATA_ROOT and stop using the VTKLargeData repository.
Drop references to VTKLargeData from test ...

Baseline images are now referenced by ExternalData content links stored
directly in each module source tree.  Drop the old VTKData baseline
subdirectory name from the vtk_add_test_* signatures.

Change-Id: I5bdc7a5bf87fc7c8fa77dcd50b79f2f54d6eba31

Change-Id: I7c6ab523d022f28256bb9d29e23ebacbcf6eafdd

Use keyword options VTK_DATA_ROOT and VTK_LARGE_DATA_ROOT to indicate
the source of data for the MPI test, if any.

Change-Id: I170b4dcb88984df5ec0bba46fa6587e0aeea63f3

Use shell code:

 git grep -Elz '\<add_test_(mpi|python|tcl)' |
 xargs -0 sed -ri 's/\<add_test_(mpi|python|tcl)/vtk_add_test_\1/g'

Change-Id: I6d076e2483209a83231fb1c96053f0389a3fcdf2

A test should run without VTK_DATA_ROOT unless it needs input data
from VTK_DATA_ROOT. Tests that have image baselines should still run
unless they need input data.

rtImage.tcl is modified to skip baseline comparisons if VTK_DATA_ROOT
is not defined.

CMakeLists.txt files are converted to use add_test_tcl macro for
consistency.

CMakeLists.txt files are changed to isolate tests that need input
data.

This was tested as follows:
1) configured a build with VTK_DATA_ROOT undefine
   ctest -R Tcl-
   154 tests passed
2) configured a build with VTK_DATA_ROOT defined
   ctest -R Tcl-
   390 tests passed

This means that 390-154 = 236 tcl tests require input data

Change-Id: I9067a3e3e2a710ddf353f0181cc7b22a85b5ef10

Kenneth Moreland authored Aug 22, 2012 and Utkarsh Ayachit committed Jan 08, 2013

This is in preparation for implementing the ability to read in multiple
modes and combine them together.  Currently, only one mode is passed and
one mode looked at.

Change-Id: I2a75ac235024aad89365e63c95a05dd65ca0c6dd

Change-Id: If9121110e4350b577eb430df9dac4736a5428c24

vtkModelMetadata is no longer used by VTK. The old Exodus reader
used to produce it but it is now gone. So there is no reason why
filters need to support it. I moved it to Exodus rather than
removing it because the Exodus writer still uses it and I didn't
want to make significant changes to the writer at this point.

Change-Id: Ic1492ff1c41e8252aaf870107f97e12e68ff7820

Note: these tests were not a part of pre-modular-vtk and have been especially
converted for vtk-modular in order to have the complete set of python tests for
each tcl test. The likelyhood of them failing is high and more work may be
needed to get them to work.

Change-Id: Iac82a32eddc1da9042450ced177258a364e5b07b

Adding new classes vtkXMLUniformGridAMRDataWriter /
vtkXMLPUniformGridAMRDataWriter based on vtkXMLHierarchicalBoxDataWriter /
vtkXMLPHierarchicalBoxDataWriter to write all types of AMR datasets in VTK XML
format. vtkXMLHierarchicalBoxDataWriter and vtkXMLPHierarchicalBoxDataWriter are
now simply empty subclasses for backwards compatibility.

The XML file format had to be extended to write enough meta-data to support
loading of Overlapping AMR datasets correctly. Consequently, the version number
was updated to 1.1.

Adding vtkXMLUniformGridAMRReader for reading VTK XML files for AMR datasets
(overlapping and nonoverlapping). Also added a new test TestAMRXMLIO.
vtkXMLUniformGridAMRReader reader v1.1. For older versions, added a converter
vtkXMLHierarchicalBoxDataFileConverter (and a test) that converts the xml to the
new format. vtkXMLUniformGridAMRReader provides appropriate meta-data in
RequestInformation() pass, similar to other AMR reader such as Flash/Enzo.

vtkXMLGenericDataObjectReader has been updated to use
vtkXMLUniformGridAMRReader for reading all types of AMR datasets.

Change-Id: I3f143c266562f039a57a745835728c5750c8e463

There is now a serial and a parallel version of the WindBladeReader.
The parallel version also doesn't depend on MPI being initialized
in order to work. If this happens, then the parallel version
delegates the work to it's parent class, the serial version.
Also, the object factory is set to create the proper version
from vtkWindBladeReader::New(); as desired so that users
can use that. The tests are also passing but the parallel test
still only uses a single process to run.

Change-Id: Iec9955b6cb69c1448593adbbab3a11357ea990dd

Change-Id: I701799d5f43b9e20185cc5f1ad2d363d520ba75c

Add optional test macro arguments to allow for some of the tests to
depend on VTK_LARGE_DATA_ROOT and for most of the tests to have
their correct images in an pre-modularized vtkdata directory layout.
NOTE: This requires some VTKDATA file movement because old tests
have names like tname.cxx.png and this assumes tname.png.

Also make TestParallelRendering return some sort of pass/fail result.

Change-Id: Id76a92ac1d7f5eedb15baff91e6849b590961d5e

This is a convenience so that you don't have to
downcast the composite dataset iterator returned
by `NewIterator()` to call methods like `VisitOnlyLeavesOff()`
or `TraverseSubTreeOff()`.

Change-Id: Ibe53476e1d040ccdb29b27bbdf5090bfbe40168c

Cleaning up vtkAppendCompositeDataLeaves including cleaning up the
documentation. Also added support for handling image-data which makes it
possible to use this filter for AMR datasets.

Change-Id: I9bea06e7b4bf427607846132c629ee56241cf9a7

The two parameters in vtkCompositeDataIterator, TraverseSubTree and
VisitOnlyLeaves, only make sense in the child class
vtkDataObjectTreeIterator, so they are moved there.

For callers, if it just calls VisitOnlyLeavesOn() then we just yank
the call since this is the default behavior anyways; otherwise, we
down cast the iterator to vtkDataObjectIterator in order to call these
functions.

Change-Id: Idbf44426bd1e281219309a824f603bd796b711b1

Previous change cause many complication errors because Rendering
no longer automatically brings in IO modules. Manually added IO
dependencies where it makes senses and removed the IO dependency
otherwise.

Change-Id: I4412112d9644e18a32e4285b1f34b161b06e1184

Change-Id: I5a4d9135520eb63ae2d369b6f43856804ac9552c

The main motivation for the changes is to improve the efficiency
of AMR data structures by replacing the data set containers and meta
data representation with new data structures.

First, the meta data associated with the AMR data is moved from
vtkInformation to a new class vtkAMRInformation so that they do not
have to be deep copied. Related changes also include:

- Before, when the LOAD_REQUESTED_BLOCKS() key is not set, the reader
  would recompute AMR meta data based on the requested blocks.  This
  is no longer done: meta data always represents what is on file.
  The reason is to avoid the sensitive meta data computation that
  depends on connectivitiy of the requested blocks.

- Processor ranks are no longer stored in the meta data. Filters
  can easily generate them by using
  vtkAMRUtilities::DistributeProcessInformation

- There used to be two types of 1D indices used to reference blocks in
  an AMR: vtkOverlappingAMR::GetFlatIndex and
  vtkOverlappingAMR...

The StandAlone + Rendering groups should contain what was in VTK
before modularization without turning on additional flags.

The StandAlone group is a special group of all modules that need no
external dependencies, such as Boost, MPI, etc. It does include
modules that rely on third party libraries VTK can build (by
default). It DOES NOT include modules that depend on OpenGL. Those
modules are in the Rendering group.

Several modules that meet the above criteria for membership in the
StandAlone group did not specify their membership via the GROUPS
StandAlone property. Also, several modules were missing from the
Rendering group.

This topic was verified by building the VTK Wiki Examples:
http://www.vtk.org/Wiki/VTK/Examples/Cxx against an installed VTK that
was built with only the StandAlone and Rendering properties enabled.

Change-Id: I8bbca22f44c087b0cbe9ff92ee2819a292b43da5

Change-Id: I48195f3bfc7588e95a4839fe7e16bc8381c795a4

Change-Id: I48603a3a19c0b3ad37315bf01815945faa6fc4fb

The ParallelIso test requires MPI so should really be part of
of a module that has this requirment. It tests the MPI image
reader so fits nicely in the vtkIOMPIImage module.

Change-Id: If09dee8a92507a8fd8b231aaf807fa2f14c48a9d

Move "{IO/Parallel => Parallel/MPI}/Testing/Tcl/TestPProbe.tcl" because
the test depends on pvtk which exists only when the vtkParallelMPI
module is enabled.  Teach prtImageTest.tcl to use "package require vtk"
just as was done for rtImageTest.tcl by commit f095f7ee (Added in some
Tcl rendering tests, 2012-04-11).  Add Parallel/MPI Tcl test
infrastructure and include TestPProbe.  Remove TestPProbe from its old
test location in IO/Parallel.

Change-Id: I49c2a72762a5094e44c8ad964a309ca97cec8ca4