GitLab

Co-authored-by: Yuanxin Liu <leo.liu@kitware.com>
Co-authored-by: Berk Geveci <berk.geveci@kitware.com>

 -The semantics of each unsigned char in the ghost arrays changes:
  Instead of storing a numeric value representing how far a cell is
  from the boundary, it is now a bit field specified by
  vtkDataSetAttributes::CellGhostTypes and
  vtkDataSetAttributes::PointGhostTypes.  The bit field is consistent
  with VisIt specs.

- Previously, filters strip all ghost cells they request from upstream
  before finalizing the output. This is no longer done.

- vtkUniform grids previously supported blanking through member arrays
  vtkUniformGrid::CellVisibility and
  vtkUniformGrid::PointVisibility. These arrays are removed and the
  blanking functionality are supported through the new ghost arrays
  instead.

- the "vtkGhostLevel" arrays for cell and point data are renamed to
  vtkDataSetAttributes::GhostArrayName() ("vtkGhostType").

- the version for VTK Legacy files is increased to 4.0 and the version for
  VTK XML files is increased to 2.0. When reading older files we
  convert vtkGhostLevels array to vtkGhostType.

Change-Id: Id5b760ed9b3842284daf45ea1551f2759301efb3

In other words, changed from the C to the C++ header name.
Did this only in .cxx files, and not in ThirdParty.

Change-Id: I81e2b2c7f2db00e98b37d507232fbc84022e8d8f

Exclude ThirdParty, Utilities/MetaIO, and Utilities/KWSys as these
are maintained outside VTK.

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>
Co-Author: Brad King <brad.king@kitware.com>

Move source files from their former monolithic VTK location to their new
location in modular VTK without modification.  This preserves enough
information for "git blame -M" and "git log --follow" to connect
modularized VTK files to their original location and history.

Co-Author: Marcus D. Hanwell <marcus.hanwell@kitware.com>
Co-Author: Chris Harris <chris.harris@kitware.com>
Co-Author: Brad King <brad.king@kitware.com>
Co-Author: Nikhil Shetty <nikhil.shetty@kitware.com>

The CVS $Revision$ keyword replacement will no longer maintain these
macros automatically.  They were used only to implement CollectRevisions
and vtkObjectBase::PrintRevisions, an API that was never used.

Automated as follows:

  pass 0:
  catch templates
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'

  pass 1:
  main changes
  ---------------
  $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
    echo "$file" 1>&2
    perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
  done
  $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
    echo "$file" 1>&2
    perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
  done

  pass 2:
  verify
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'

Fixed multi-line vtkCxxRevisionMacro and templates by hand.

The CVS $Revision$ keyword replacement will no longer maintain these
macros automatically.  They were used only to implement CollectRevisions
and vtkObjectBase::PrintRevisions, an API that was never used.

Automated as follows:

  pass 0:
  catch templates
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro' | grep '<'

  pass 1:
  main changes
  ---------------
  $ git grep -l '^vtkCxxRevisionMacro' | while read file; do
    echo "$file" 1>&2
    perl -i -ne 'print unless (/^vtkCxxRevisionMacro/ and /\)/)' $file
  done
  $ git grep -l -e 'vtkTypeRevisionMacro(' | while read file; do
    echo "$file" 1>&2
    perl -i -pe 's/vtkTypeRevisionMacro/vtkTypeMacro/g' $file
  done

  pass 2:
  verify
  ---------------
  $ git grep 'vtk\(Cxx\|Type\)RevisionMacro'

Fixed multi-line vtkCxxRevisionMacro and templates by hand.

The readers were accessing their output information and through the executive.
This creates problems when what is passed to ProcessRequest() is different.

* vtkDataArray now has a new superclass-vtkAbstractArray.vtkAbstractArray
provides type-agnostic API to access array elements. vtkDataArray provides
a double API to access values -- such an API is deliberately missing from
vtkAbstractArray, since arrays like string arrays are not castable to doubles.

* vtkAbstractArray has the notion of components/tuples, but does not make
any assumptions about the arragment of these. It's up to the concrete
subclasses how the data is represented in memory.

* vtkFieldData used to provide tuple API to get/set values from data arrays
contained in it. However, now that FieldData can have arrays that are not
vtkDataArrays, this API is not longer valid.
The following are the methods that are no longer available:
double* GetTuple(const vtkIdType);
void SetTuple(const vtkIdType i, const double* tuple);
void GetTuple(const vtkIdType i, double* tuple);
void InsertTuple(const vtkIdType i, const double* tuple);
void InsertNextTuple(cons double*);
double GetComponent(const vtkIdType i, const int j);
void SetComponent(const vtkIdType i, const int j, const double c);
void InsertComponent(const vtkIdType i, const int j, const double c);
However, new API is provided to copy tuples arround from one field data to
another using:
void SetTuple(const vtkIdType i, const vtkIdType j, vtkFieldData* source);
void InsertTuple(const vtkIdType i, const vtkIdType j, vtkFieldData* source);
vtkIdType InsertNextTuple(const vtkIdType j, vtkFieldData* source);

* vtkFieldData provide a vtkDataArray* GetArray(int index) to retrieve arrays
in the field data. This function can will now return a NULL if the array
at the given index is not a data array. It provides
vtkAbstractArray* GetAbstractArray(int index);
to retrieve an array even if it isn't a vtkDataArray.

* Since vtkFieldData can contain arrays that aren't subclasses of
vtkDataArray, so can vtkDataSetAttributes. However, an attribute can only be
a vtkDataArray subclass i.e. one cannot set a vtkStringArray as the SCALARS
array for a Point Data, for example.

* String Array IO is only supported in XML file formats. If deemed important,
support may be added for lecacy file formats.

*** Array Iterators ***
Another addition to the VTK Arrays, is the notion of Array Iterator. A
vtkArrayIterator subclass is be provided for every vtkAbstractArray
subclass. The iterator is a random access iterator. The iterators are not
available in any of the wrapped languages, however, in C++ they can be used to
write templatized code to processes the array values without any implicit type
conversion and consequent loss of precision. vtkArrayIteratorTemplateMacro is
provided to simply switching between different types of the arrays. Examples of
use of this macro and the iterators can be found in
vtkXMLWriter.cxx / vtkXMLDataReader.cxx / vtkXMLStructuredDataReader.cxx.