vtkCompositeTransferFunctionItem was using `screenBounds` for x
coordinate instead of `dataBounds` for the line which case cause
paraview/paraview#18941. Fixed that.

some fixes some suppressions some comments

The dynamic analysis tests have uncovered a number of floating point
exceptions, mainly divide by zero. This MR enables floating point
exceptions if tests are built with a debug build type and the
compiler is a gnu compiler.

Safety guards have been added to classes that exhibited exceptions.

TestAdjustLowerBoundForLogPlot.cxx - Tried to take log10 of negative number

TestlinePlotDouble - inf and nan used in test. Disable exceptions

vtkChart.cxx - guards to protect against zero divide

vtkChartBox.cxx - guards to protect against zero divide

vtkInteractiveArea.cxx - trying to take log10 of negative number

vtkPiecewisePointHandleItem.cxx - protect against degenerate lines

vtkAMRSliceFilter.cxx - protect against zero length vector

vtkLagrangianBasicIntegrationModel.cxx - guards to protect against zero divide

UnitTestMultiThreshold - disable exceptions for one test that uses Nan()

vtkIntersectionPolyDataFilter.cxx - guard acos range

vtkPCAStatistics.cxx - guards to protect against zero divide

vtkCubeAxesActor.cxx - guard against log10(0.0)

vtkColorTransferFunction.cxx - guard to protect against zero divide

TestGPURayCastIsosurface.cxx - disable exceptions, possible driver issue

vtkDendrogramItem.cxx - check for degenrate line

vtkDendrogramItem.h - comparison doesn't meet irreflexive requirements

Some cppcheck issues and suppress a dynamic analysis issue

try to clean up some cppcheck issues

This adds a title on scatter plot matrix. It already had the method to set but the title was never drawn
This also add a test for it.

There were surprisingly few.  The benefit is that when additional enums are added, a warning will point you to consider every switch statement.

Fixes issue exposed by !4835.

vtkChartMatrix was setting sizes with negative widths/heights on
internal plots. This was happening during ParaView test playback.
Fixing vtkChartMatrix to avoid setting invalid sizes, prefer empty sizes
instead.

Added a few more assert checks in vtkContextClip and
vtkOpenGLContextDevice2D to catch such issues earlier.

vtkChartBox: replaced a retained, returned pointer with a stored
value.

vtkChartXY: Added check for range[0] == range[1] and avoid division by zero.

vtkFunctionParser: Added check for division of a vector by 0.0.

vtkUnstructuredGridQuadricDecimation: first time through loop,
lasterror is 0.0. Avoid division by zero by checking for 0.0.

vtkChartBox: replaced a retained, returned pointer with a stored
value.

vtkChartXY: Added check for range[0] == range[1] and avoid division by zero.

vtkFunctionParser: Added check for division of a vector by 0.0.

vtkUnstructuredGridQuadricDecimation: first time through loop,
lasterror is 0.0. Avoid division by zero by checking for 0.0.

vtkOpenGLContextDevice2D now respects tile-scale/tile-viewport in
`vtkOpenGLContextDevice2D::SetClip`. This addresses
paraview/paraview#18365.

Had to update TestChartUnicode baseline to get it passing.

vtkMath::Round converts double to int, as opposed to long.  Both can be lossy, but the former much more so.

Replaced some uses with std::round(), some with std::lround().

Eliminated the long->int truncation as much as possible, but kept it in many instances.

The new design for the VTK logo has been around for some time; this
patch set updates the testing data to match the new design.

Thanks to Steve Jordan and Dave DeMarle, the new VTK logos are now
available at:
https://www.vtk.org/download/

Related to !4334.

Beyond a certain zoom level, axes grid lines disappear.
This was due to a restriction of a maximum of 200
grid lines. This restriction has been removed.

The implementation of vtkChartXY::RecalculatePlotBounds() works with
either the scaled or unscaled bounds, depending on whether scaling is
enabled on the axis. However, the logic for handling the
AdjustLowerBoundForLogPlot flag was not correctly handling the case
where the bounds were log scaled.

To address this issue, the implementation now uses some logic to
determine whether log scaling is enabled and adjusts the bounds of the
plot accordingly.

Added a test for this feature as well.

PrintSelf() should print the member names and values. vtkAxis was
doing something different.

Make the following methods in vtkAxis virtual so users can customize vtkAxis:

GenerateSimpleLabel(), GenerateSprintfLabel(), GenerateLabelFormat(), GenerateLogSpacedLinearTicks()

This was originally proposed by a post on

http://vtk.1045678.n5.nabble.com/Request-Make-certain-methods-related-to-tick-labels-in-vtkAxis-virtual-td5744594.html

with the purpose of allowing the user to use customized axis labels, e.g. for displaying dates or times.

Apart from making the above methods virtual it is also required that the user can set the customized axis in a chart.
Hence further modifications were necessary in vtkChart, vtkChartXY and vtkChartXYZ to replace the axis created in the chart
by the customized axis.

Further a change was made to vtkAxis to allow the axis title to be switched off.

Found via `codespell -q 3 -I ../vtk-whitelist-words.txt --skip="./ThirdParty,./Utilities"`

Fix paraview/paraview#18076

Found via `codespell`

The rest of the test uses vtkNew, be consistent within the test. Removed
a C-style cast that was not needed.

Try to quickly clean up the dashboards

Ken Martin authored 6 years ago and Brad King committed 6 years ago

make image difference symmetric to catch some
failures that were slipping through. This exposed
a number of valid images that were no longer
correct and needed to be replaced.