Exodus Writer doesn't respect the block ids from vtkModelMetadata explicitly supplied by user.
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The Exodus writer internally increments block ids to avoid a block id of 0. This change was introduced in revision 1.38. By internally incrementing the block ids the block ids no longer match those given in the vtkModelMetadata explicitly supplied by a user.
It is very important that the information in the vtkModelMetadata supplied by the user be respected. Changing block ids to avoid a block id of 0 should probably be done outside of the writer.