Change-Id: I4fcd40fdfb1b714c26486562d49715015445ea8f

Change-Id: Ieaac07aa6ad89fd964f2215be790ee2f05978c5e

An LS-Dyna simulation may have time-varying nodal coordinates.
In this case, the initial, static coordinates are ignored since
they are overwritten by the deflected coordinates as each timestep
is read. However, it is apparently possible to configure LS-Dyna
not to write the deflected coordinates. In which case, we *must*
read the static coordinate data since that is all that's present.
Do so.

Change-Id: I4db3af4bbd0948212f179a620bde3bc0fefe23b3

This was true for the OpenGL2 variant, but not OpenGL. This caused
the IO/Export tests to fail as they could not safe down cast the
actor in the prop collection. Also removed unneeded includes etc
from the parent class.

Change-Id: I1acd77e84df3d4a1362223bbc1581b626731c3da

This method returns NULL when there are no more objects, but it was
also resulting in NULL if the safe down cast failed. This could lead
to early termination when there is a mixture of different actors and
the context is not the first.

Change-Id: Ia1a13e0be1c89d41fb767c0c99aa064d977f9231

Silences warnings from MPI headers.

Change-Id: I3d0b24a95ea90c89b112534cb65b333c0007fa5f

This adds dependencies to tests that were missed in the initial move
for vtkRenderingContext2D.

Change-Id: If816a2a15ca02bca8c5f736872d4166b90f73bcf

This moves the logic for object factory override generation to a
central function, and removes lots of copy/paste code in our CMake.
Also removed/retired the OpenGL2 object factory stomping variation
as it is no longer needed and could produce unwanted side effects.

Change-Id: I4a5ee2db76f73d57eded1d9a9240cefc4918cd74

These tests should work with either backend, and were inadvertently
merged with a hard dependency on OpenGL2 backend.

Change-Id: I25356b499d2317143db37e3fa59b04c5b1c53710

These can only build with the OpenGL backend.

Change-Id: I7f95de24b0ad064a7ebe04b028cd9808857b35e4

Change-Id: I07b6148b2184941740f02106e4b8462af3a1a92e

There is no way to specify the z-spacing, and it seems more logical
to default to something matching the x-spacing rather than defaulting
to 1.0. This will of course result in 1.0 when nothing is specified
in the file.

Change-Id: I6e1f9e4f2f294844a6ed84ba1aa439399f5eb957

Readers are no longer passed a sub-extent if they say
they support piece requests. Added extent splitting logic.

Change-Id: If245a347cc71b300f9deca6bf66a559f922cc96d

Also fixed style (indentation) in some classes.

Change-Id: I163842fe6f13885595f687307a3f7b77d883efa7

- Removed unused extent translator subclasses
- Removed unnecessary refereces to the extent translator
- Moved extent translator into Common/ExecutionModel

Change-Id: Idc53dd66891297b1f6a06ea3eb1baf394cb24b20

It made more sense to have both CAN_PRODUCE_SUB_EXTENT and
CAN_HANDLE_PIECE_REQUEST in vtkAlgorithm.

Change-Id: Ie64bb3e7c8417113bfb7f677c10d8feb5fdddc39

Change-Id: Id76d3bc545a64675a0820cb1d9b45c61a51efc6a

Change-Id: I24bf3b0959bf6e22543bb526b26d9fda14ab4c20

Change-Id: I80d4dbda38c7a6d83d6ba3fadeb81cce1154a1b1

To work with the new pipeline changes.

Change-Id: Ic5c8ac86026999f79924d8e61b10fbcb18286bb8

Change-Id: I7e5c55259159752882c8ae056e08f9bec12b3c02

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
sources. I removed it and added a CAN_HANDLE_PIECE_REQUEST instead.
This key, produced by a source, tells the executive that a source is
able to handle piece request. It is a source only key produced in
RequestInformation and is not propagated downstream. If this key is
not present, the executive will only execute the source for piece 0
to produce the entire data. It is then up to the user to add a filter
that splits the data for other piece requests. The only exception to
this is when CAN_PRODUCE_SUB_EXTENT is present, in which case the
executive will split using an extent translator AT THE source - not
downstream.

Conflicts:
	Filters/FlowPaths/vtkParticleTracerBase.cxx

Change-Id: I8db4040289ff87331adeecded4a738313d9b52df

This dependency has to be stated explicitly.  This error wasn't caught
immediately because, on most sytems, vtkzlib is linked transitively via
vtktiff and vtkpng.

Change-Id: I36408557a7eed266fe05cdc891fc75dc1259502e

Change-Id: I721d91a75a04f485a34aeed9fa04b154d892b1f8

This patch adds support for reading and writing NIFTI files, as well
as full access to the NIFTI header.  Versions 1 and 2 of the NIFTI
header are supported, and the reader can also be used to read Analyze 7.5
files, though the only Analyze header elements that are supported are the
ones that overlap with NIFTI.  Automatic compression and expansion for
gzipped files is also provided whenever the filename ends with a .gz
extension.

Change-Id: Iead3afb1a65d8c01aa52f3ca55c6da2f08703375

The first fix is that some zeiss images set PlanarConfig to "SEPARATE"
(i.e. separate color planes) even when NumberOfSamples is 1.  When the
number of samples is one, the PlanarConfig can be safely ignored.

The second fix is that ReadVolume assumed that the number of slices was
always equal to NumberOfPages, which was in conflict with ExecuteInformation
which set the number of slices to SubFiles if SubFiles > 0 (cf line 505).
This caused a crash, because ReadVolume was reading more data than the
reader had allocated space for.

Change-Id: I822e45a53c210b5edebfe8ce27443fe1434110ba

Fixed issued with unigrid enzo datasets. The reader
was calculating number of levels to be 0, which was
leading to a segfault. Added code to detect unigrid
datasets and fixed the issue by setting the number
of levels to 1.

Change-Id: Ie9f1fbe8c3c38c69e5761b357256be9531ed10f3

There was an off-by-one error in the setting of the extent.

Change-Id: I1818184845a11bc7cbf560e4bfb270a943c8a8ac

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

If we have simple, single component, tightly-packed images then
copy them directly into the allocated buffer. If we are clipping, use
memcpy to just copy the subset requested. This is primarily aimed at
accelerating the load times for TIFF volumes. Thanks to Robert
Maynard for the suggested simplications in the templated image
function.

Change-Id: I6c3b10a019fc892b1e1bbbce32841e7f946eb995

Change-Id: I6546ff164baca86afb1a73b896dd10b1bce2c005

Change-Id: I5f19b101063e1a25d4f5db5c4356ce5efffbd90d

Change-Id: If92879d67d11dfc5965ef42a8c173539801b3c98

Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

Change-Id: Ie3a7d94877dd70b82bc86b20816980013956c9ef

As Robert Maynard pointed out we already control for this in the
CanRead function, and so there is no need to repeatedly verify this
on every volume or tile read.

Change-Id: I47247928503c3e070a3905950fd726a2392c281a

Updating progress per page seems to give reasonable updates.

Change-Id: I142f5e18fad8294df2367d82bea171567c005fa5

Fairly big refactoring of the TIFF reader, use templated methods in
many more places, avoid loss of type after it is determined, added
support for reading in 32 bit float TIFFs.

Change-Id: I4abf61179461acfa04c2c17c4e6d20467587c984