[Paraview] CoProcessing question

[Moreland, Kenneth]

John,

I don't have any experience with that, but I think Nathan Fabian telling me he tried that and it didn't work.  I don't remember why.

-Ken


On 7/28/10 3:25 PM, "Biddiscombe, John A." <biddisco at cscs.ch> wrote:

Hold on a minute. Everything you said is quite right and I'm with you 100% - Except. Suppose the pipeline places piece numbers in each update request - which are converted to structured extents (can't remember exactly where in the executive this will happen, but it will somewhere) - then the reader (or in this case coprocessing library) produces pieces of data which in our case, will not be the right pieces. We set the extents accordingly on out imagedata and just past the results out. When the pipeline downstream receives all these pieces, it will probably ignore the updateextent that was requested and use the real extent on the actual dataobjects. No? yes?

It might work. Anyway. I'll try out some pieces and see what gives. Ideally the coprocessing library will need a way of modifying the extents. I'll see if there's a way of managing it. (I'll also see what the TableExtentTranslator thingy does, though it may be the reverse of what we want).


   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmorel at sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20100728/dea386e3/attachment.htm>