.ba...@kitware.com ]
>
To: "Ufuk Utku Turuncoglu (BE)" < [ mailto:u.utku.turunco...@be.itu.edu.tr |
u.utku.turunco...@be.itu.edu.tr ] >
Cc: "paraview" < [ mailto:parav...@paraview.org | parav...@paraview.org ] >
Sent: Monday, March 19, 2018 3:51:51 PM
Subj
in
> the place that you indicate, the piece and whole extent is same in the
> files.
>
> Regards,
>
> --ufuk
>
>
> --
> *From: *"Andy Bauer"
> *To: *"Ufuk Utku Turuncoglu (BE)"
> *Cc: *"paraview"
>
n the place that you
indicate, the piece and whole extent is same in the files.
Regards,
--ufuk
From: "Andy Bauer"
To: "Ufuk Utku Turuncoglu (BE)"
Cc: "paraview"
Sent: Monday, March 19, 2018 3:51:51 PM
Subject: Re: [Paraview] structured to unstructured
Hi Ufuk,
It looks like you're already using multi-channel input as you're adding
since you have " g_coprocessorData->AddInput(strarr[i]); " unless that's
always just called once. We're just trying to clarify the "inputs" by
naming them channels -- I'm not sure it makes it easier to understand but
Hi Andy,
Thanks for your help. Yes, each tile has its own grid information. The
problem is that if i set whole extent in the adaptor side and write data
to disk using allinputsgridwrite.py, the whole extent is same with piece
extent. I am not sure what is going on in the background when live
Hi Ufuk,
Currently a multipiece data set always has to be nested under a multiblock
dataset. This definitely seems like an unreasonable limitation on a
structured grid under a multipiece dataset but I suspect we just haven't
had the resources to put into making this work properly. My suggestion
wo
Hi,
I am using MPI parallel code under Catalyst co-processing. In this case, i am
defining data by creating multi-block dataset and putting multi-piece dataset
into the first block (0). In this case, each piece is defined as structured
grid. The problem is that, to create volume rendering, i n
