Add changelog

Documentation/release/9.1.md

@@ -414,7 +414,7 @@ VTK_LAGRANGE_HEXAHEDRON                  VTK_LAGRANGE_HEXAHEDRON
   names using a `/regionName/` prefix for non-default regions.
 
 [fides]: https://gitlab.kitware.com/vtk/fides
-[ioss]: http://gsjaardema.github.io/seacas
+[ioss]: https://sandialabs.github.io/seacas-docs
 [open-mining-format]: https://omf.readthedocs.io/en/stable/index.html
 [openvdb]: https://www.openvdb.org
 

Documentation/release/dev/ioss-writer-completion-of-implementation.md

+## vtkIOSSWriter: Completion of Implementation
+
+`vtkIOSSWriter` is a writer for the Exodus file format that has now been completely implemented.
+`vtkIOSSWriter` is implemented using the [IOSS library](https://sandialabs.github.io/seacas-docs).
+The input can be a `vtkPartitionedDataSetCollection`, `vtkPartitionedDataSet`, or `vtkDataSet`.
+It supports the following entity types: Node/Edge/Face/Element blocks, and Node/Edge/Face/Element/Side sets. If the
+input of the writer originated from `vtkIOSSReader`, the entity types can be automatically deduced. Otherwise,
+`SetAssemblyName` and `AddSelector` can be used to specify which block belong in which entity type. If no selector has
+been defined, and the input does not originate from IOSS, then all blocks will be treated as Element Blocks. The arrays
+(or fields) to be written can be specified using `GetEntityFieldSelection` after `SetChooseFieldsToWrite` has been set
+to true. A subset of the timesteps to be written can be selected using `SetTimeStepRange` and `SetTimeStepStride`. Ghost
+cells can be removed using `SetRemoveGhosts`. If the input has been transformed, e.g. using Clip, the original ids of
+blocks can be preserved using `SetPreserveOriginalIds`. The Quality assurance and information records can be written
+using `SetWriteQAAndInformationRecords`. `Global IDs` are created assuming uniqueness for both Node Blocks, i.e. points,
+and Edge/Face/Element blocks, if they are not present, or invalid. `element_side` is needed for Edge/Face/Element/Side
+sets. If it's not present, sets will be skipped. If it's present, but invalid, and there were (old) `Global IDs` that
+were invalid, then they will be used to re-create `element_side`, otherwise, sets will be skipped.
+Finally, `vtkIOSSWriter` is now parallel-aware, therefore, it can be used in parallel.