[Paraview] [Xdmf] Xdmf time series loads as Multi-block Dataset

[John Biddiscombe]

Eric

I just tried xdmf for the first time in a couple of weeks an yes. It's 
completely stuffed. I get a multiblock dataset with 800 blocks, each 
being one timestep - instead of a single (or possibly multi-block) 
dataset with time varying stuff.

I Can see looking at Jerry's changes on immediate probable cause, but 
I'd better read through the email he sent a few days/week back and 
review the changes. I see what Jerry has tried to do - create a 
multiblock xdmf structure and just fetch the correct grid when you 
request a timestep - thus giving us what we want. But there's a flaw in 
the logic when the actual output dataset is generated - so that it 
creates a multiblock one instead of the type givenm by the Nth (=time) 
dataset inside it when we are fetching a time step which is not composite.

I need this to work, so I'll be looking at it soon. Ig Jerry reads this 
before I fix it, then feel free to step in with the correct patch :)

JB
> Hey all,
>
> Maybe I'm behind on my Xdmf XML format again, but my files that a  
> month or two ago loaded a time series of unstructured grids now loads  
> into ParaView CVS as a Multi-block Dataset with one block for each  
> time step at each time point.
>
> Let's say I have 1200 Polyvertex time steps in my file. I can (slowly)  
> step through the animation of my grid, but at each time point the  
> progress bar is cycling through a bunch of work, and each time point  
> lists (in the Information tab Data Hierarchy pane) a Multi-block  
> Dataset made up of 1200 Unstructured Grids. Clicking on each of these  
> blocks reveals that only the "current" time step block has Data Arrays  
> associated with the grid. So, at each time step of the animation, the  
> process seems very slow because 1200 blocks are being loaded, only one  
> of which actually has real data in it. (The Time pane at the bottom of  
> the Information tab always lists the correct time indices and values  
> for the whole series.)
>
> Maybe this is just a change in the way time series are dealt with, but  
> it is much slower with my data sets, and it made more sense to me to  
> have each time step able to be represented as a simple grid, if  
> desired. (I have been using a self-modified vtkXdmfReader.cxx file for  
> a while, so I'm not sure when this multi-block issue would have  
> appeared.)
>
> Thanks,
> -Eric
>
> ------------------------------------------------------
> Eric E Monson
> Duke Visualization Technology Group
>
>
>
> _______________________________________________
> Xdmf mailing list
> Xdmf at lists.kitware.com
> https://www.kitware.com/cgi-bin/mailman/listinfo/xdmf
>   


-- 
John Biddiscombe,                            email:biddisco @ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82