ENH: Remove the need to manually regenerate the hill data.

Improved thedocumentation and deprecated GenerateTheHills() in
vtkParametricRandomHills.

This change removes the need for the user to manually regenerate the
 centers of the hills, standard deviations and amplitudes whenever the
 parameters change.

Previously, if any parameters changed, then the user had to manually
 call GenerateTheHills() this meant that when using ParaView, only the
 number of hills could be changed. This change will allow all the
 parameters to be changed when using ParaView.

Change-Id: I6e8be04238591c8d435284e5eec2203ebd599dfa
Signed-off-by: Andrew Maclean <andrew.amaclean@gmail.com>
Clean and uniformize vtkPoints & vtkPoints2D.

MTime is now also modified on Initialize, Reset and SetNumberOfPoints.
This allows a recomputation of bounding box when the point set
content drastically change. Initial boundary is also now set
as undefined instead of [0-1].

Change-Id: Idd1d8d3c68f0e09ddcef8a6f9db2622512f2643a
Changed to make tests run serially, async nature was causing collisions.

Change-Id: I8349471e8773eb27fb1e6c2344cba316543677a3
Merge topic 'pvweb-fix-lookup-table-usage' into master

7f92da11 Changed to make tests run serially, async nature was causing collisions.
Refactor GetRange to compute all ranges at the same time.

Instead of only computing a single components range when requested, we
now compute all the component ranges and cache all the values. This
improves the total runtime by 1.5x to 3x.

Computing the range for a multiple component array of type: float with a length of 10000000 and with 3 components
original: 0.028544 seconds
new:      0.018013 seconds
Computing the range for a multiple component array of type: double with a length of 10000000 and with 3 components
original: 0.042368 seconds
new:      0.019447 seconds
Computing the range for a multiple component array of type: int with a length of 10000000 and with 3 components
original: 0.03528 seconds
new:      0.023454 seconds
Computing the range for a multiple component array of type: vtkIdType with a length of 10000000 and with 3 components
original: 0.050991 seconds
new:      0.024635 seconds
Computing the range for a multiple component array of type: float with a length of 10000000 and with 9 components
original: 0.186394 seconds
new:      0.112901 seconds
Computing the range for a multiple component array of type: double with a length of 10000000 and with 9 components
original: 0.375575 seconds
new:      0.114103 seconds
Computing the range for a multiple component array of type: int with a length of 10000000 and with 9 components
original: 0.200056 seconds
new:      0.141547 seconds
Computing the range for a multiple component array of type: vtkIdType with a length of 10000000 and with 9 components
original: 0.369794 seconds
new:      0.144766 seconds

Change-Id: Ia3da45b323d2d9daf0b0c428140cc5faef6db185
Merge topic 'faster_ComputeScalarRange' into master

196bbe8a Refactor GetRange to compute all ranges at the same time.
Fixed no newline at end of file warnings.

Change-Id: I03328a13a1f948c24a2c65ed3fa58fdcae3e46e5
Merge topic 'clean_and_update_vtkPointsXX' into master

cb93b88d Clean and uniformize vtkPoints & vtkPoints2D.
Merge topic 'ensemble-warning-fix' into master

0f703d2a Fixed no newline at end of file warnings.
Merge topic 'fix_ParametricHills_for_ParaView' into master

da505148 ENH: Remove the need to manually regenerate the hill data.