[Paraview] writing block data in parallel for vtk readers

[Cook, Rich]

The code in VisIt is up to date; it’s just Paraview that seems behind the times.  I am not able to completely convince myself of why but I suspect that’s the problem.  The actual error shows up as some sort of VTK error.
— Rich


ERROR: In /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754
vtkPVCompositeDataPipeline (0x252ff00): Algorithm vtkVisItMirandaReader(0x25342b0) returned failure for request: vtkInformation (0x2521130)
  Debug: Off
  Modified Time: 119319
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0




ERROR: In /usr/local/tools/paraview-opengl-4.1.0/src/ParaView-v4.1.0/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 754
vtkPVCompositeDataPipeline (0x252ff00): Algorithm vtkVisItMirandaReader(0x25342b0) returned failure for request: vtkInformation (0x2521130)
  Debug: Off
  Modified Time: 119319
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_DATA_OBJECT
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0




On Sep 10, 2014, at 4:55 PM, Berk Geveci <berk.geveci at kitware.com<mailto:berk.geveci at kitware.com>> wrote:

Hey Rich,

Is this a matter of updating the VisIt bridge or the code in VisIt is old too?

What are the larger runs these folks do? And what is the timeframe?

We are working on ADIOS readers and that may be another option. This is where we currently plan on pushing for large scale IO needs.

HDF5 is certainly another option. So is writing legacy VTK files from each node. I'd guess Silo is another option too.

It depends on the needs and scale at which they will be running.

Best,
-berk

On Mon, Sep 8, 2014 at 7:45 PM, Cook, Rich <cook47 at llnl.gov<mailto:cook47 at llnl.gov>> wrote:
Hi,
I am wondering how to write out a set of VTK files for input into paraview.
The code we are writing from is Miranda, an MPI code, and each processor writes out its subdomain individually.  No ghost zones are written into the files.  Perhaps they could be; I’m not sure about that part.
Sometimes the data is curvilinear but usually rectilinear.
Miranda is included in the VISIT_BRIDGE stuff but what’s in VISIT_BRIDGE for Miranda is old and the newer stuff doesn’t parse any more.
Thanks!

--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605<tel:%28925%29%20423-9605>
☎ (fax) (925) 423-6961<tel:%28925%29%20423-6961>
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)




_______________________________________________
Powered by www.kitware.com<http://www.kitware.com/>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview



--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140911/9d97e010/attachment-0001.html>