MantisBT - ParaView
View Issue Details
0014235ParaView(No Category)public2013-08-15 12:472016-08-12 09:59
Philip Cardiff 
Kitware Robot 
normalminorhave not tried
closedmoved 
4.0 
 
TBD
incorrect functionality
0014235: Cannot load decomposed OpenFOAM model containing globalFaceZones
If you try to view a decomposed OpenFOAM model which contains globalFaceZones (for example $FOAM_TUTORIALS/incompressible/icoDyMFoam/mixerGgi), you get a warning about the number of faces in 'faces' and 'owner' not matching.
the globalFaceZones add faces to 'face' but they do not have owners, so I imagine it should be fine to ignore these extra faces.

The warning/errror is:

Warning: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/IO/Geometry/vtkOpenFOAMReader.cxx, line 4725
vtkOpenFOAMReaderPrivate (0x114a3bec0): Numbers of faces in faces 668 and owner 614 does not match


ERROR: In /Users/kitware/Dashboards/MyTests/NightlyMaster/ParaViewSuperbuild-Release/paraview/src/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754
vtkCompositeDataPipeline (0x114a3b2e0): Algorithm vtkOpenFOAMReader(0x114a3ab70) returned failure for request: vtkInformation (0x1149edb30)
  Debug: Off
  Modified Time: 120621
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  FORWARD_DIRECTION: 0
  FROM_OUTPUT_PORT: 0
  ALGORITHM_AFTER_FORWARD: 1

Best regards,
Philip
No tags attached.
Issue History
2013-08-15 12:47Philip CardiffNew Issue
2013-08-15 12:49Philip CardiffNote Added: 0031465
2016-08-12 09:59Kitware RobotNote Added: 0038436
2016-08-12 09:59Kitware RobotStatusbacklog => closed
2016-08-12 09:59Kitware RobotResolutionopen => moved
2016-08-12 09:59Kitware RobotAssigned To => Kitware Robot

Notes
(0031465)
Philip Cardiff   
2013-08-15 12:49   
Just to clarify,
this problems occurs with the built-in ParaView OpenFOAM reader - I have not tried the plugin reader distributed with OpenFOAM.

Philip
(0038436)
Kitware Robot   
2016-08-12 09:59   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.