Mantis issue http://www.paraview.org/Bug/view.php?id=10528

Kitware Robot authored Mar 08, 2016 and Dan Lipsa committed Mar 08, 2016

Code extracted from:

    https://gitlab.kitware.com/third-party/proj.git

at commit 41bdf05361007f8c5186f3df9944d86bb273ed13 (for/vtk).

The XMLUnstructuredDataReader had no way of querying thenumber
of pieces in the file.

The XMLUnstructuredDataWriter was not correctly reporting progress
when writing pieces. It reported 100% progress after the first
piece.

Added the 'old' WriteCellsAppended method back to vtkXMLUnstructuredDataWriter, that now internally uses the new WriteCellsAppended method with NULL for the faces and faceOffsets paramters.

Reverted unnecessary changes in vtkXMLWriter.cxx

Jamil Appa authored Aug 07, 2015 and Menno Deij - van Rijswijk committed Aug 10, 2015

Integrated patch by Jamil Appa from
http://public.kitware.com/pipermail/vtk-developers/2012-October/027837.html
to fix bug 13382, see http://www.paraview.org/Bug/view.php?id=13382

Fixes #15558.

If data does not have ghosts or blanking, the previous version is used.

This works for vtkXMLStructuredDataWriter and vtkXMLUnstructuredDataWriter.

Not sure if the analyzer is right, but setting
the ivar to null after delete is safe and simple.

Change-Id: I0ac894f12312e7722e9f5b23d6e69a86cf47894e

Change-Id: Id76d3bc545a64675a0820cb1d9b45c61a51efc6a

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
...

subclasses of vtkXMLWriter should now call OpenStream & CloseStream
as opposed to OpenFile & CloseFile.

Change-Id: I39ccdc711d07e96763fc941b5fcd80b1da6b38c5

Also, use vtkTypeTemplate in vtkArrayIteratorTemplate to allow
safe down-casting.

Change-Id: I352491a52df8320c711f112feb911c91c5e77e11

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

Use size_t for memory buffer sizes and vtkTypeInt64 for file positions
and offsets exposed in header files.  Use vtkTypeUInt64 for sizing and
indexing of whole data.  The latter will be necessary to read small
portions of data requiring 64-bit indexes on 32-bit architectures.
Use std::streampos for stream seek operations but avoid exposing it
in header files because its type can vary on some platforms depending
on preprocessor definitions for large file support.

Change-Id: I5c6eb335fb2415de652f012fbf34e2f2952e443a

The header is private to XML writer implementations.  Name and place it
accordingly.

Change-Id: I3b35f249059246eb526ef06c5039fc435d80f2b1

VTK Developers authored Apr 09, 2012 and Brad King committed Apr 09, 2012

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>

VTK Developers authored Apr 09, 2012 and Brad King committed Apr 09, 2012

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>

Mark Olesen authored May 19, 2010 and Brad King committed May 20, 2010

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.

BUG: remove vtkDeformPointSet and vtkExtractPolyhedralMesh as well as related tests. Fixed some bugs that broke VTK tests.

ENH: 1) Removed temporary vtkXMLPolyhedronMeshReader/Writer, and moved the functionality into vtkXMLUnstructuredGridReader/Writer. 2) Reused old InsertNextCell APIs, and added code to support insertion of a polyhedron cell using a nonstandard input cell array format.

Mark Olesen authored Apr 23, 2010 and Brad King committed Apr 23, 2010

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.

* 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.

BUG: When writing multiple files with the same reader, offset manager should be initialized before each write

BUG: Writers (readers only) should not set UPDATE_TIME_INDEX, this would in some case cause reexecution of filters.

ENH: Add blocker to avoid people including vtkOffsetManager. Also add documention on why the filter execution may not work when handling pieces and timesteps at the same time