[Paraview] slightly puzzled by paraview extract block behavior (UNCLASSIFIED)

[Andy Bauer]

If you check the output on the server you'll probably see the error I got.
Since the client is waiting for the server to finish the error doesn't pop
up on the client.

If your file is shareable, maybe you could add that to the bug tracker
since they might be different and I'd hate to assume we fixed your bug when
we only verified that we fixed my bug.

On Mon, Sep 15, 2014 at 5:06 PM, Stephens, Michael M ERDC-RDE-ITL-MS <
Michael.M.Stephens at erdc.dren.mil> wrote:

>  Classification: UNCLASSIFIED
> Caveats: FOUO
>
> this just in…..
>
>
>
> using the same data you are ( ParaViewdata: naca.bin.case, to eliminate
> one difference at least)
>
>
>
> when I tried 16 procs on the server side the server seems to be hung.
> didn’t crash the server (not yet at least)
>
> but it might as well have because the client is frozen waiting on the
> server. the server is accumulating run time but nothing else.
>
>
>
> -m
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* Monday, September 15, 2014 4:01 PM
>
> *To:* Stephens, Michael M ERDC-RDE-ITL-MS
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] slightly puzzled by paraview extract block
> behavior (UNCLASSIFIED)
>
>
>
> Hmm, well I have no idea if we're hitting the same bug or not but it seems
> like too much of a coincidence that this is happening for both of us at 14
> procs but not 13. I created a mantis issue at
> http://www.paraview.org/Bug/view.php?id=14996. Feel free to add to it if
> you can share your Ensight file.
>
> Regards,
> Andy
>
>
>
> On Mon, Sep 15, 2014 at 4:53 PM, Stephens, Michael M ERDC-RDE-ITL-MS <
> Michael.M.Stephens at erdc.dren.mil> wrote:
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
> in all cases for the ensight data we are working with, there is no READ
> error.
>
> there is no error reported at all either for reading or extract block
> operations.
>
>
>
> the extract block silently fails to pass the variable data for larger core
> counts on the data we are working on. geometry seems okay.
>
>
>
> btw, I am not very fluent in my understanding of the ensight formats (case
> files or otherwise)
>
>
>
> -m
>
>
>
> *From:* Andy Bauer [mailto:andy.bauer at kitware.com]
> *Sent:* Monday, September 15, 2014 3:23 PM
> *To:* Stephens, Michael M ERDC-RDE-ITL-MS
> *Cc:* paraview at paraview.org
> *Subject:* Re: [Paraview] slightly puzzled by paraview extract block
> behavior (UNCLASSIFIED)
>
>
>
> Hey Mike,
>
> I'm getting something funky when reading an Ensight file with 14 processes
> as well that I don't see with 2 or 13 processes (I didn't bother trying
> with other amounts). The error I get is:
> ERROR: In
> /home/acbauer/CODE/ParaView/ParaView-v4.1.0/VTK/Common/DataModel/vtkDataSet.cxx,
> line 414
> vtkStructuredGrid (0xa70560): Point array DENS with 1 components, only has
> -325 tuples but there are 0 points
>
> This is just for loading in the file though and not even using the extract
> block filter. Are you getting a similar error?
>
> I'm getting the error with the naca.bin.case at
> http://www.paraview.org/gitweb?p=ParaViewData.git;a=tree;f=Data/EnSight;h=fc6cbe6fc7851e2f3bae520f4cf4b933ab963c93;hb=HEAD.
>
>
> Best,
>
> Andy
>
>
>
> On Mon, Sep 15, 2014 at 3:54 PM, Stephens, Michael M ERDC-RDE-ITL-MS <
> Michael.M.Stephens at erdc.dren.mil> wrote:
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
> had someone ask me for help with a problem they were having with paraview
> v4.1.0 in server/client mode.
>
>
>
> steps are: i) read in an ensight case file, ii) use Extract Block filter
> to yank out a particular block,  iii) color extracted block with various
> variables.
>
> simple enough.
>
>
>
> let me say up front that the data is pretty small (order of 100k points,
> 450k cells).
>
> we ran this using a varying number of procs in a single node.
>
>
>
> when the number of procs got to be 14 or greater (16 cores in the server
> nodes) the extract block step lost the data variables.
>
> the geometry was correct still but none of the data variables survived the
> operation.
>
>
>
> I’ll stipulate that it makes little sense to use more than one proc for
> data this small.
>
>
>
> but why does the extract block not still work?
>
>
>
> slightly puzzled.
>
>
>
> -m
>
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: FOUO
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20140915/def3f8c6/attachment.html>