Cell to point on exodus block ids
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
If I open a 16 file exodus dataset on 4 nodes, run D3, then run CellToPoint. The resulting cellToPoint dataset has something wrong with it. The field that I'm converting from cell data to point data resides on a single processor after running D3, and the cell field has a single value. After running CellToPoint, the point field has a long streak in it at a value not present in the initial cell field. The Cell Field has a data range of [2,2]. The resulting Point field has a data range of of [1,2].
The bug is present regardless of whether D3 is run or not, but in the use case where this comes up, D3 is used to eliminate process and file boundary issues.