Change-Id: I10a54acbd076e055d8071414f2fff1ebafe1653d

Fix the way how the bags are computed. They are now performed at
50 and 99% of the distribution.
Functional bag plots also create a median serie which is the
median line of all input series. Outliers series are also
tagged with an "_outlier" extension in their name.

Change-Id: I990428c9b79278be9be725491232b3e9d69190b0

Fix the problem with the position of Y axis: long labels were trunked.
This position was fixed, it is not flexible depending the size of the labels.

Add new functions to the chart API to allow manipulation of series
by id (vs by name).
Add support for manual plot labels setting.
Enhance the boxplot displacement, it now correctly follow the mouse
without ugly jumps.

Change-Id: I400cd064616f7b93415e17db9749d709ea2f7345

Use precomputed table of densities to avoid precision differences
on some machines.
Also remove unuseful normalization step in the plot and algorithm.

Change-Id: Ifb28b82b276ee93b66f4ddf8f4375f7b3b465b94

Change-Id: Ic5c728d45d447fac2678401394717d261dd91d48

Add a new plot type to draw functional bag plots.

Add vtkExtractFunctionalBagPlot filter to generate the two 2
components columns needed to fee a functional bag plot.

Add a TransposeTable filter to transpose tables, options allow
to create a new column containing initial row names, and use such
a column to name the new columns.

Change-Id: If7fedd9b99038ab7924f5e9b170ed72bd02f9189

Add a new type of plot to draw 'bag plots', a bivariate generalization
of the univariate boxplot.
Add a new statistic filter to compute the Highest Density Regions
that can be used to compute a density field used to draw the bag plot.

Add support for the case where the bag is reduced to 2 points.

Change-Id: I16852a46bacc3d74a72c001114cef9b287765c9d

The vtkContextMouseEvent object isn't really designed to be used
outside of the mouse events/interactors. When using them all variables
should be set. Ensure positions that happen to not be used in this
particular test are initialized (this is all normally taken care of
when real mouse events are received).

Change-Id: I12ba843845e42dddb7e2ddb5ef05492b79f10786

The parallel coordinates did not correctly handle double precision
input, added support to vtkPlotParallelCoordinates and created a
new test to verify it. Also some very minor clean up in the other
test, and fixed variable naming for consistency.

Change-Id: I4d688857dcfe86b044b8284789e7873f698d8820

* New test in Charts/Core to color the new class vtkCategoryLegend

* New tests to cover the continuous & categorical heatmaps now
  available from vtkHeatmapItem

Change-Id: I06fa49c65e85ad421d5a360920a679379e77be89

Change-Id: I6087a7f769cd93ef20dda035e7aeb4d745f9c82b

This adds a new interaction mode to vtkChart which zooms the
X and Y axis based on the X and Y movement of the mouse. This
is similar to the zoom mechanism in matplotlib.

This also adds some documentation for the mouse actions enum in
vtkChart along with a test for the new ZOOM_AXIS mode.

Change-Id: If6c923607a3bf86ec8f6bc16188d1e49a260ba95

The bad point detection was incorrectly detecting large double values
as bad, use templated code that works with the original type and a set
to ensure a sorted, unique list of bad points is generated. Modified
the test to use a second corner and one series that is very large to
test the functionality.

Change-Id: I08322a0b3fd728e496d2d5f1f1901054afe4eb7d

This commit consolidates the logic between all vtkControlPointsItem subclasses
to consistently notify rest of the world that the control points were modified.
Previously, commit 1509669d tried to do the same with
vtkControlPointsItem::PointsModifiedEvent, however vtkCompositeControlPointsItem
wasn't firing those consistently resulting in the BUG #14283.

While attempting to fix that, I noticed that vtkControlPointsItem has
StartChanges()/EndChanges() methods that could be used for a similar purpose:
notify the world that control points are being changed. Hence, remved the
PointsModifiedEvent, instead fixing the code to consistently use
StartChanges()/EndChanges() calls.

Fixed StartChanges/EndChanges to fire the event on the vtkControlPointsItem
(along with tranfer function, as it was previously) and added logic to avoid
duplicable firing of events due nested calls to StartChanges/EndChanges.

Change-Id: I144e775cbdfbc9c1334cfc2b02609b37dda8cae7

Windows displays 3 figures after e rather than just what is needed.

Change-Id: I3cf2209fb19c8f5f50001451dedf4e3d05009930

This accounts for both under and overflow. Added a test requiring the
origin shift in order to correctly render points. The odd artifact is
the labels on the X axis (all 1) due to the number of significant
figures displayed.

Change-Id: I6247a00ce84c7d2012cde692e24b717a174c2752

Change-Id: I5d9b4ca87539172df2ee58730035bfdf7afdbde3

Added awareness of the scaling factor to the vtkPlotBar class, and a
test to exercise this functionality (with mixed plotting of points, line
and bar).

Change-Id: I55e157012e2618d5d59986ef828f80036188f4c7

Change-Id: Ifd7a5e7daf636d6e0cc8a8ff96aa85be84b24e7d

Change-Id: I34ebfd9381302754da3ef808748b34dbdcabf8cc

Set the necessary attributes to create a sample buffer for the
OpenGL context of the vtkCocoaRenderWindow.  This allows VTK to
do anti-aliased rendering in the window.  However, multisampling
is turned off by default on OS X because it causes rendering
problems on some Mac models.

Change-Id: I0ff8073e38d8a63e637cfe4e7146e2d1327d65eb

Cleaning up issues with the context-items related to tranfer function editor.

+ Added support for log-mapped color-transfer function. We ensure that when
  using log-scale, the color transfer function widget also enter log-space.

+ vtkPiecewiseControlPointsItem had a bug resulting it deleting of end points
  even when told otherwise. Fixed that.

+ Added new event vtkControlPointsItem::PointsModifiedEvent which if fired when
  control points are changed making it easier for application to do something
  when the points are changed.

+ Improved the usability by adding ability to label control points.

Change-Id: If02bc1139f6ccb3d7c2198b07d10491f902bafda

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

The VTKData repository no longer holds Baseline directories so drop
references to such directories from the VTK source tree:

* Replace the default -V in CMake/vtkTestingRenderingDriver.cmake with a
  value that will fail but indicate what to do.  All current uses of
  this module have an explicit -V so the default should never be used.

* Drop a few leftover Baseline directory references from comments in
  "*/*/Testing/*/CMakeLists.txt".

* Remove boilerplate duplicate test command-line examples (that
  reference Baseline directories) from *.py tests and leave an updated
  example in "Wrapping/Python/README.txt".  The command-line example
  convention was added long before the modern CTest infrastructure
  and is no longer needed anyway.

Change-Id: I3001e99b3cc8c2717107e61b3b7f988caeb49cab

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

Convert some direct add_test calls to use the helper functions instead.

Change-Id: I4f6b92e24804885c6b1449b21ae8efffd22ffdbf

Refactor */*/Testing/Cxx/CMakeLists.txt to use the vtk_add_test_cxx
function instead of direct add_test calls.

Change-Id: I73dee627fa87a399c48b409af046b116fc75a0fd

This commit provides an interface for querying the
range of values taken on by a vtkPlot's X- and Y-axis
inputs.

This can be used to determine whether log-scaling
is appropriate for each axis of the plot. It is part
of a fix to ParaView bug 13899.

Change-Id: Ia0449ca496dd935fb4ca25dc5dd2b691d2f89d93

This commit introduces a new chart selection mode to the charts, based
on plots rather than rows. The default remains row-based selection,
where a selection in one plot causes all corresponding points in the
same row of the table to be selected in other plot objects. This
behavior was improved slightly to iterate through and accumulate
selections in all plots (rather than just using that of the last plot
which resulted in confusing behavior).

The plot based selection keeps any selection specific to a plot. The
vtkPlot object that originated a selection is stored in the PROP
property of the vtkSelectionNode, with the SOURCE property being used to
store the table the selection is on. The vtkSelection object will have a
vtkSelectionNode object for each plot with a selection on it. All of the
normal selection combination rules are applied per-plot.

The rectangle and polygon selection mode code was refactored to reduce
the amount of code duplication necessary. Two tests were introduced
allowing interactive use of the chart with row or plot based selection
using polygon selection (left mouse) or rectangle selection (right
mouse).

Change-Id: Ib739ec620b7094bcf4940767000e8620c432e341

Fixed by adding 'static' and/or 'const' to several
variables that had neither.

Removed one obsolete comment too.

Change-Id: I8775c9a1fa8d9cc75b28619216bbe7f901117a0f

This change is to address ParaView bugs 13876, 13877, and 13899.
It removes LogScaleReasonable and the associated logic which was
contributing to nonsensical ranges for logarithmic axes.

This patch also adds methods {Get,Set}Unscaled{Minimum,Maximum,Range}()
so that fixed ranges may be specified in the same coordinate
system as the source data. The versions of these methods without
"Unscaled" in their names expect log-values to be passed or
returned when LogScale is true, which is difficult for user-interface
code to track.

Additional changes are required to address the test case of
ParaView bug 13899. With these changes, the minimum and maximum
limit values are properly transformed when switching to and from
log-scaled axes.

Plots that rely on axes to determine scaling are fixed
to refer to the active scaling (GetLogScaleActive) instead of
the desired scaling (GetLogScale)..

Change-Id: I1a4a3882bbeab2484145f4a75a6430cf6a0cea42

Just added 'static' in front of many private functions.

Change-Id: I892a46d684e00a44e7f84a7343e2cf5690f07eed

Modified python test to verify functionality

Change-Id: I855c853fc4b56d958108e49977432fd0b52e462e

Modified a test to verify functionality, and fixed the PaintLegend
method to use the appropriate color for the separate series in the
stacked plot.

Change-Id: I2d38aaa93b33e329736266bcbb90b44b273f49e7

Some tests that used OpenGL classes did not include OpenGL headers.
This worked by coincidence on systems where gl.h was in system path.
Didn't work on the Mac.

Change-Id: If13ef3605b239ddf8d345b82d374841e50d30601

Reduced the number of points generated, and use an opaque pen.

Change-Id: I29f436434cc79b6baa7feb01e8bc2b1bc7dafe1d

TestColorTransferFunction has been failing for almost 4 months on some
window platforms. Increase the error tolerance to pass the test.

Change-Id: I70618273fb840379ed001b562a76f5bacb233c38

This makes it easier for external applications attempting to use
vtkTestingObjectFactory since they don't require the
vtkTestingRendering_SOURCE_DIR to set anymore (which won't even when the
vtkTestingRendering module has been successfully imported.

Change-Id: I14795bbe0f9d71d41da14c970ba49bdb8e11a913

The remove() command is documented as discouraged and replaced by the
list(REMOVE_ITEM) command which has been around since CMake 2.6.0.

Change-Id: Ibd5a95ef9dc81eb09a28a344ef009d7f1511abf6