[lammps-users] error with atc output file in paraview

Dear lampps community,

my version of lampps is 07-Apr-2010, so it's the latest stable release right now. I am facing the following problem: The output file created with the command:
fix_modify AtC transfer output [name] [frequency] tensor_components
from the atc-package crashes the visualization software Paraview.
The version of Paraview I'm using is the latest stable release: 3.8.0. I tried this one on an i386 and a x86 linux architecture, both have the same problem. I attached 1 output file from the atc example simulation bar1d_ttm to this e-mail for anybody who would like to try it himself. In the input file I simply added the command mentioned above. It is possible to open the file, but when going to the next frame I get the following output and Paraview crashes:

ERROR: In /home/kitware/ParaView-3-8/ParaView-3.8/ParaView/Servers/Filters/vtkEnSightReader2.cxx, line 308
vtkEnSightGoldBinaryReader2 (0x8da1cb0): error reading geometry file

ERROR: In /home/kitware/ParaView-3-8/ParaView-3.8/ParaView/VTK/Filtering/vtkExecutive.cxx, line 757
vtkCompositeDataPipeline (0x8d92b80): Algorithm vtkEnSightGoldBinaryReader2(0x8da1cb0) returned failure for request: vtkInformation (0x8cbec88)
  Debug: Off
  Modified Time: 128298
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0
  FROM_OUTPUT_PORT: 0

I'm not sure whether this is an error of the output file or from Paraview. So I wrote an e-mail to the developers of Paraview, too. In case I get a response, I will add it here. Does anybody in this community have an idea how to solve this problem?.

Thanks for your suggestions in advance.
Sincerely Yours
M.Busse

Simulation1.rar (28.8 KB)

I'll let the ATC package folks respond to this.

Steve

2010/5/23 "Matthias Bartholomäus Immanuel Buße" <[email protected]......>:

Hi Matthias, I can view your results in paraview 3.6 on my mac with no problem. I have not "upgraded" to paraview 3.8, but I will try and let you know how it goes.
best,
Jeremy