[Paraview] VTK Writer

2012-05-06 Thread Luis Martinez
Hi all, I have a pvbatch script that worked in version 3.12. It uses plot over line and writes out CSV data. Now I get the following error in version 3.14: Is this a bug or am I supposed to call the writer differently in 3.14? Thanks! Tony ERROR: In /build/buildd/paraview-3.14.1/ParaView

Re: [Paraview] VTK Writer

2012-05-10 Thread Utkarsh Ayachit
Your script looks reasonable to me. I'll check it out. Utkarsh On Sun, May 6, 2012 at 2:44 PM, Luis Martinez wrote: > Hi all, > > I have a pvbatch script that worked in version 3.12. It uses plot over line > and writes out CSV data.  Now I get the following error in version 3.14: > > Is this a b

Re: [Paraview] VTK Writer

2012-05-10 Thread Yumin Yuan
Is this your own csv writer? if yes, did you have hints for the writer in your xml config file .. This is something I found out that I have to do for my writer plugin with 3.14. Yumin On Thu, May 10, 2012 at 2:14 PM, Utkarsh Ayachit wrote: > Your script looks

Re: [Paraview] VTK Writer

2012-05-10 Thread Mohamad M. Nasr-Azadani
Luis, I had similar problem with some writers. It was very strange and sporadic (it occurred both when I used *.vtu and *.csv writers). I kind of got the feeling that most of the times it appeared when I ran PV in parallel so I could solve it by running PV in serial mode. But as I said, I am not 1

Re: [Paraview] VTK Writer

2012-05-11 Thread Utkarsh Ayachit
There definitely seems to be a bug in the WriterFactory which fails to return valid readers when running through Python. We are looking into it. Utkarsh On Thu, May 10, 2012 at 10:38 PM, Mohamad M. Nasr-Azadani wrote: > Luis, > > I had similar problem with some writers. > It was very strange and

Re: [Paraview] VTK Writer

2012-05-11 Thread Luis Martinez
Hi all, I was able to get it to work in 3.14 by doing: PlotOverLine1.UpdatePipeline() before creating the writer. Thanks, Tony > Date: Fri, 11 May 2012 09:18:29 -0400 > Subject: Re: [Paraview] VTK Writer > From: utkarsh.ayac...@kitware.com > To: mmn...@gmail.com &

Re: [Paraview] VTK Writer

2012-05-14 Thread Sebastien Jourdain
ne() > > before creating the writer. > > Thanks, > > Tony > > > >> Date: Fri, 11 May 2012 09:18:29 -0400 > >> Subject: Re: [Paraview] VTK Writer >> From: utkarsh.ayac...@kitware.com >> To: mmn...@gmail.com >> CC: lamtmar...@hotmail.c

Re: [Paraview] VTK Writer

2012-05-28 Thread Paul Edwards
I've just noticed that none of my writer plugins are working from the GUI. They appear but when trying to write I get the following output: Failed to create writer for: "/path/to/file.mytype" ERROR: In /ParaView/ParaViewCore/ServerManager/vtkSMWriterFactory.cxx, line 374 vtkSMWriterFactory (0x8b

Re: [Paraview] VTK Writer

2012-05-28 Thread Sebastien Jourdain
Hi Paul, can you be more explicit in what you mean by: > I thought the type just went in the pqXML file. Thanks, Seb On Mon, May 28, 2012 at 11:45 AM, Paul Edwards wrote: > I've just noticed that none of my writer plugins are working from the GUI. >  They appear but when trying to write I get

Re: [Paraview] VTK Writer

2012-05-28 Thread Paul Edwards
Sorry, by pqXML, I meant the XML file for the GUI plugin. On May 28, 2012 5:55 PM, "Sebastien Jourdain" < sebastien.jourd...@kitware.com> wrote: > Hi Paul, > > can you be more explicit in what you mean by: > > > I thought the type just went in the pqXML file. > > Thanks, > > Seb > > On Mon, May 2

Re: [Paraview] VTK Writer

2012-05-29 Thread Sebastien Jourdain
Hum, the GUI XML should be fine. Did you try to add those hint in the XML itself to see if that solve the issue or not ? Please let us know, as it looks like a bug to me. Seb On Mon, May 28, 2012 at 5:09 PM, Paul Edwards wrote: > Sorry, by pqXML, I meant the XML file for the GUI plugin. > > On

Re: [Paraview] VTK Writer

2012-06-19 Thread Sebastien Jourdain
I've just push a fixed in next. You can follow the bug here: http://www.paraview.org/Bug/view.php?id=13250 Thanks for reporting issues, Seb On Tue, May 29, 2012 at 8:46 AM, Sebastien Jourdain wrote: > Hum, the GUI XML should be fine. Did you try to add those hint in the > XML itself to see if