D3 incorrectly resolving global ids
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Oops! While fixing bug #5019 (closed) I must have accidentally exposed another bug with vtkMergeCells. Now when running D3 on meshes with global ids, the ids are sometimes merged. The following shows off the bug:
- Connect to a server with 2 processes.
- Load disk_out_ref with the Global Node Ids array on.
- Run through D3. You will see several cells missing.