afed075d Forces the compiler to convert a char* to a string rather than a bool.

When using operator<< on a char*, the compiler chooses operator<<(bool)
(standard conversion) rather than operator<<(const string&) (user defined
conversion). We add a operator<<(const char*) to force the correct conversion.

Change-Id: I6f3dedcb36c41b82047dcf41bc20da9c1ec6e6b8

14b1a6e2 Add new rendering class API based on vtkPanel class

Change-Id: I7cef5d9c9514491ba5aba608a40dac59703bbac5

cebeddb1 Set the z-spacing in a TIFF to match x-spacing

5139f277 Catalyst web

Improve query help in composite UI
8 results per page

Change-Id: Ie6d8131f99bb6910b3a491cb4c92390eb374239b

06685ac2 Fixed vtkXdmfReader for parallel structured data.

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

05ad8270 Fixed crash in the empty input test.

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

87291c64 Improve ComputeScalarRange when we have a single component.
219b75b9 Correct ComputeScalarRange when dealing with multiple components.
074e1fe1 Update DataArray and DataArrayTemplate to use vtkTypeTraits.
a84e734b Update ComputeVectorRange based on gerrit feedback.
90289d7e Move all free functions in vtkDataArray into an anonymous namespace.
9f1773eb Improve the performance of vtkDataArray::ComputeVectorRange.
83b4764e Improve the performance of vtkDataArray::ComputeScalarRange.

37afe252 COMP: Fix a few compiler warnings
0769d8f7 ENH: MPI structured data extraction filters
ef1611f7 ENH: RectilinearGrid implicit connectivity support
8a4e1cf1 ENH: Use vtkImageData in implicit connectivity
296ace04 ENH: Update extract structured data filters
0165b0a1 COMP: Remove HyperTreeGridGeometry::UpdateExtent()
8c347eef COMP: Correct ParallelMPI module test dependencies
3517e2a0 Fixed issues in the group filter.
a4944a46 Fixed contour filters
2354c78d Fixed multiple issues with resample/probe filters.
16e20f26 Filters should silently handle empty input
40031835 ExtractSelection was not managing pieces corretly. Fixed.
ece82eef Removed unnecessary reference to extent translator
19e69143 Cleaned up extent translators.
ac6f1854 Moved key.
747b780a Updated filters and sources to work with new pipeline logic.
...

Change-Id: I840a8add196181be90b79b6f53ab3683209149e1

This commit introduces new filters, vtkPExtractGrid, vtkPExtractVOI
and vtkPExtractRectilinearGrid. Each filter, extends the corresponding
serial filter, i.e., vtkExtractGrid, vtkExtractVOI and
vtkExtractRectilinearGrid, respectively. The parallel versions of the
filter add proper handling for distributed datasets. When sub-sampling,
a gap across partitions may be introducted. The filters use the
vtkStructuredImplicitConnectivity class to communicate the data across
process boundaries and resolve the gap.

Change-Id: I2b2a5ecd5841adceee4e30aecd30d485ecfff5df

Added support for vtkRectilinearGrid type in the structured
implicity connectivity class. Also, extended the test to
check for correctness of the new functionality. Further,
updated RectilinearGrid partitioner such that it can either leave a
gap between partitions or not. Also, refactored and improved the
implementation.

Change-Id: I658e2798bd9720a7baafd7eb1eed3f1e8befafe0

Modified the vtkStructuredImplicitConnectivity class to
populate a vtkImageData instead of vtkUniformGrid. That way
it can be used with either class since vtkImageData is the
parent class of vtkUniformGrid.

Change-Id: I38190d740c43f44ce66f744692e6f07ac0d0f92e

This commit updates the extract/sub-sample structured data filters
to reflect the changes of refactoring the piece and extent in VTK.
Namely, vtkExtractGrid, vtkExtractVOI and vtkExtractRectilinearGrid,
which operate on vtkStructuredGrid, vtkImageData, and vtkRectilinearGrid
respectively, are updated.

These datatypes, albeit different, they share common functionality. To
avoid replicating essentially the same code in all of these three classes,
a helper class, called vtkExtractStructuredGridHelper, is introduced. This
new class is part of VTK's vtkCommonDataModel module since it needs to be
used by both the vtkImagingCore and vtkFiltersExtraction module.

One minor caveat, is that Imaging algorithms/tests require that the origin
of the image to be retained and that the output extent is w.r.t.
to the input extent, when there is no sub-sampling. For that reason,
when there is no sub-sampling vtkExtractVOI, will yield an output extent
that is with respect to the origin. All other filters re-number the
output extent starting from zero. The output extent is always re-numbered
when the data is sub-sampled.

Change-Id: I26fe5a115032333db9814987a6c9dc949e51ef52

UpdateExtent() is no longer compatible with the pipeline changes
introduced in this branch.

Change-Id: I364576e245c944803a0e7c674902d9194c3e4ede

Parallel XML writers have been moved to a new module
vtkIOParalleXML (see 7355859). Tests in the ParallelMPI
module use the Parallel XML multi-block writer, hence they
now need to depend on vtkIOParallelXML, instead of
vtkIOParallel. Fixed that.

Change-Id: I5490cd9d9b5bbaeb7f1c29826f002ef97515dc4e

The group filter was not dealing with extents properly. It
needed to properly ask for the whole extent from inputs (which
was done using an extent translator in the past) and it needed
to remove whole extent from the output (the default is to copy
from 1st input).

Change-Id: Ib44282f7f48aa60c7fad9fa6a5cceeb50e9b2e54

Change-Id: Ibbeb24c5f4ff4dc6ba160295ef9de0455988885d

The main issue was in asking the right update extent from
the input. Also fixed a number of bugs in the resample filter.

Change-Id: Id2a4a9989baaff6b5f51d20e5c298c676a220d86

Change-Id: I707f0bff212922f42801622298c12456c0ed6f75

Change-Id: Ife54f3e32daf790321d638669c569aed254c45d2

Change-Id: I74925cc4dbba114bebd3ae90268c193a048c6e33

- 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

Note that this change slightly breaks backward compatibility.
The filter now processes all points even if they are on a ghost
region. This means that this filter will produce ghost polygons
that need to be stripped downstream. This is in line with the
"filters should work with what they have" attitude the new
changes enforce. This makes pipeline and filter logic much
simpler.

Change-Id: I77738480eaf716ec74095f9573c0cfc403769037

Change-Id: I80d4dbda38c7a6d83d6ba3fadeb81cce1154a1b1

Was trying to read the extent into an array of size 3 instead
of 6. Doh!

Change-Id: Ic8bb2872782c86739ddf8119b3d44edb35e42e06

To work with the new pipeline changes.

Change-Id: Ic5c8ac86026999f79924d8e61b10fbcb18286bb8

The origin was not offset properly in cases where extent
had to be adjusted. This is all due to the fact that the
legacy writer always writes extents starting at 0.

Change-Id: Id37f21d7c99d2ecdf6285d2870bf87e10b534a7a

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

86cfbf4d Catalyst Web - Composite improvement