ExodusReader->D3->CellToPoint Error with bad GlobalNodeId's
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
If you open a split exodus dataset with bad globalNodeId's (duplicated among files), then Run D3, and finally apply CellToPoint, the result is a "sparse" dataset.
Turning off the GlobalNodeId aray in the Exodus reader results in a valid D3 display, but CellToPoint is still messed up.
Basically instead of seeing a nice box, you see a shredded box.