Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-06-14 Thread Jens
Hi, Miguel Fosas send an other patch assigne to the related bug http://www.itk.org/Bug/view.php?id=10775#c20932 Instead of XdmfConstString Value=0;, he moves the variable in the case-section. Greetings Jens --- XdmfDataItem.cxx2010-06-07 18:11:50.954700131 +0200 +++

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-06-14 Thread Dave Partyka
Hi All, I have applied the new fix to Xdmf in commit cd802a3e4c0c13b4697518363535562f758a6d48 and updated ParaView to point to the latest Xdmf. Let me know if there are more problems. On Mon, Jun 14, 2010 at 9:13 AM, Jens jens-de...@gmx.de wrote: Hi, Miguel Fosas send an other patch assigne

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-31 Thread Dave Partyka
Hi Ken, Kenji and Jens, I pulled the fix to UpdateInformationUniform that Ken committed into ParaView a few weeks ago. I just now also applied the fix to UpdateInformationFunction and pulled the change into ParaView as well. I apologize for some of the confusion. Since the transition to Git,

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-29 Thread Kenji Takizawa
Dear Ken, and dear Utkarsh, I sent an email for the bug fix. But Kenneth applied it to different location. Instead of line 148 (which is in UpdateInformationFunction), it was applied to 172 (which is in UpdateInformationUniform). So I would like to inform you this again. I believe this issue is

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Jens
Hi Utkarsh, thank you for that hint. I can see the bounding box now ... But somehow it does not refresh the whole pipeline. What do I have to do, that all parts of pipeline are updated before I write the image. Any idea? Greetings Jens Utkarsh Ayachit schrieb: Jens Here's an updated

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Utkarsh Ayachit
Jens, Is the non-refreshed part of the pipeline visible in the view? Utkarsh On Fri, May 28, 2010 at 3:23 AM, Jens jens-de...@gmx.de wrote: Hi Utkarsh, thank you for that hint. I can see the bounding box now ... But somehow it does not refresh the whole pipeline. What do I have to do,

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Jens
Hi Utkarsh, if I reload the state in paraview-gui it does not refresh ether. I have to walk through the pipeline (bottom to top) and call Apply. Greetings Jens Utkarsh Ayachit schrieb: Jens, Is the non-refreshed part of the pipeline visible in the view? Utkarsh On Fri, May 28, 2010

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Utkarsh Ayachit
Jens, It would be great if you could post a state to reproduce this issue. Utkarsh On Fri, May 28, 2010 at 1:31 PM, Jens jens-de...@gmx.de wrote: Hi Utkarsh, if I reload the state in paraview-gui it does not refresh ether. I have to walk through the pipeline (bottom to top) and call Apply.

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Jens
Hi Utkarsh, The problem is related to bug 10775 (http://public.kitware.com/Bug/view.php?id=10775) and hyperslabs in XDMF. I attached an example which should reproduce the problems I discribe now: hyperslab on its own: pv 3.6.2: loading test.xmf-dataset u_without_hyperslab works fine pv 3.8.0:

Re: [Paraview] pvbatch + LoadState('..') +XDMF = empty image

2010-05-28 Thread Utkarsh Ayachit
Jens, I'd recommend not relying on Xdmf state loading or Python API in 3.6 (or before) since that was broken. It has since been fixed for 3.8. I have requested the ARL/Xdmf folks to take a look at the hyperslab issue. I'll keep you posted. Once that segfault is fixed, state loading should not be