Re: [Paraview] NASA OVERFLOW reader

[Berk Geveci]

Hmm. May be a bug. Do you have any example files? Hopefully a small one.
Please send it directly to me. Are these from stock OVERFLOW?

-berk


On Tue, Aug 13, 2013 at 12:28 PM, Michael Robinson <
michael.robin...@kratosdefense.com> wrote:

> **
>
> Berk:
>
> I really appreciate your response, but it is still not working for us.
> We produce 64-bit OVERFLOW grid and q files and are trying to visualize
> them using ParaView 4.0.1.  The grid files are read without any problem.
> However any attempt to read the q files produces errors.
>
> On Windows 32-bit:
>
> ERROR: In
> C:\DBD\pvs-x32\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 754
>
> vtkPVCompositeDataPipeline (1E30E8E8): Algorithm
> vtkMultiBlockPLOT3DReader(14F540E0) returned failure for request:
> vtkInformation (1E361D90)
>
> Debug: Off
>
> Modified Time: 353439
>
> Reference Count: 1
>
> Registered Events: (none)
>
> Request: REQUEST_INFORMATION
>
> FORWARD_DIRECTION: 0
>
> ALGORITHM_AFTER_FORWARD: 1
>
>
>
>
>
>  ERROR: In
> C:\DBD\pvs-x32\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 754
>
> vtkPVCompositeDataPipeline (1E30E8E8): Algorithm
> vtkMultiBlockPLOT3DReader(14F540E0) returned failure for request:
> vtkInformation (1E361D90)
>
> Debug: Off
>
> Modified Time: 353439
>
> Reference Count: 1
>
> Registered Events: (none)
>
> Request: REQUEST_INFORMATION
>
> FORWARD_DIRECTION: 0
>
> ALGORITHM_AFTER_FORWARD: 1
>
> This error occurs immediately after selecting the q file.
>
> If we then persist and hit the "Apply" button, the following error
> message pops up:
>
> ERROR: In
> C:\DBD\pvs-x32\paraview\src\paraview\VTK\Common\ExecutionModel\vtkExecutive.cxx,
> line 754
>
> vtkPVCompositeDataPipeline (1E31A7B0): Algorithm
> vtkMultiBlockPLOT3DReader(143BAE38) returned failure for request:
> vtkInformation (1E36BE90)
>
> Debug: Off
>
> Modified Time: 364288
>
> Reference Count: 1
>
> Registered Events: (none)
>
> Request: REQUEST_INFORMATION
>
> FORWARD_DIRECTION: 0
>
> ALGORITHM_AFTER_FORWARD: 1
>
>
>
>
>
> We get the same type results on Linux 64-bit systems.
>
> Any recommendations would be appreciated!  Thanks!!
>
>
> Michael A. Robinson
>
> Kratos/Digital Fusion
>
> 4904 Research Drive
> Huntsville, AL  35805
>
>
>
>  --
> *From:* Berk Geveci [mailto:berk.gev...@kitware.com]
> *Sent:* Monday, August 12, 2013 6:51 PM
> *To:* Michael Robinson
> *Cc:* paraview@paraview.org
> *Subject:* Re: [Paraview] NASA OVERFLOW reader
>
>  The Plot3D reader in 4.0 can read 32 bit and 64 bit Overflow files. Here
> are the messages I sent to the Overflow mailing list a while ago:
>
>  Hi folks,
>
>  I am happy to report that there is now a robust Plot3D / Overflow reader
> in ParaView that does automatic format detection for binary files. I am
> sorry that it took this long. It was not the easiest reader to write. It
> works with:
>
>  - Overflow files (any number of Q variables)
> - Single and double precision real values
> - C and Fortran output
> - Big and little endian files
> - ASCII and binary files
> - Q file series for unsteady flows
>
>  I also developed a simple meta file format that supports xyz file series
> as well as actual time values for each Q file (which is currently not
> supported without the meta file - this is needed for accurate particle
> advection). I am going to provide some documentation about this in the
> ParaView Wiki soon.
>
>  You can test this out by downloading the development binaries:
>
>  Mac:
> http://open.cdash.org/viewFiles.php?buildid=2873933
> Linux:
> http://open.cdash.org/viewFiles.php?buildid=2873792
> Windows:
> http://open.cdash.org/viewFiles.php?buildid=2873742
>
>  Please give it a try and let me know if you run into issues. If you
> would like to wait for a stable release, ParaView 4.0 is scheduled to be
> released early in May.
>
>  -
>
>  I am happy to announce that ParaView now supports function files. There
> is now support for pretty much the entire original Plot3D spec as well as
> Overflow. Some of the new features are:
>
>  - Overflow files (any number of Q variables)
> - Function files (any number of functions)
>  - Single and double precision real values
> - C and Fortran output
> - Big and little endian files
> - ASCII and binary files
>  - XYZ and/or Q file series for unsteady flows and changing geometry
>  - More robust iblank support
>
>  XYZ file series require the use of a meta-file (p3d extension) as
> described here:
>
>  http://www.vtk.org/doc/nightly/html/classvtkPlot3DMetaReader.html#details
>
>
>
>  Best,
> -berk
>
>
>
> On Thu, Aug 8, 2013 at 11:57 AM, Michael Robinson <
> michael.robin...@kratosdefense.com> wrote:
>
>>
>> Is there a generally available reader for NASA's OVERFLOW CFD code?
>> A plugin perhaps?
>>
>> Michael A. Robinson
>> Kratos/Digital Fusion
>> 4904 Research Drive
>> Huntsville, AL  35805
>> ___
>> Powered by www.kit

[Paraview] Display error

[Kit Chambers]

Hi,

I have just started with ParaView 4.0.1 and keep getting weird behaviour
from the display where by it keeps going yellow. The behaviour is similar
to that mentioned in this email to the list.

http://www.paraview.org/pipermail/paraview/2013-July/028717.html

Was there any follow up to this?

Kit
___
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://www.paraview.org/mailman/listinfo/paraview

Re: [Paraview] Building Catalyst

[Andy Bauer]

Hi Mark,

In the base edition of my version the only filter that I see that works is
the Contour filter. If you use the coproc.py script for co-processing
script and replace FECxxAdaptor.cxx you should be able to get it to run
properly. The results will be garbage but it will produce a pvtp file.

As for how to enable other filters in your build of Catalyst, that should
be in section 4 of the user's guide or in
http://www.paraview.org/Wiki/Generating_Catalyst_Source_Tree. The cmake.sh
file is just a simplified build script and doesn't do anything as far as
enabling extra filters by itself.

Andy


On Thu, Aug 15, 2013 at 10:08 AM, Vanmoer, Mark W wrote:

>  Hi Andy and Utkarsh, 
>
> I’m not sure I can share the original code, so I tried the GitHub example
> Andy linked. I configured it to use the Catalyst build directory for
> ParaView_DIR. I still get the import errors, which I see I can ignore, but
> then also
>
> ** **
>
> Traceback (most recent call last):
>
>   File "", line 2, in 
>
>   File "coproc.py", line 74, in DoCoProcessing
>
> coprocessor.UpdateProducers(datadescription)
>
>   File
> "/home/mvanmoer/builds/Catalyst/1.0.alpha-build/lib/site-packages/paraview/coprocessing.py",
> line 102, in UpdateProducers
>
> self.CreatePipeline(datadescription)
>
>   File "coproc.py", line 30, in CreatePipeline
>
> self.Pipeline = _CreatePipeline(self, datadescription)
>
>   File "coproc.py", line 16, in _CreatePipeline
>
> class Pipeline:
>
>   File "coproc.py", line 19, in Pipeline
>
> Slice1 = Slice( guiName="Slice1", Crinkleslice=0,
> SliceOffsetValues=[0.0], Triangulatetheslice=1, SliceType="Plane" )
>
> NameError: name 'Slice' is not defined
>
> ** **
>
> Okay, is this because of what you’re talking about below, Utkarsh?  That
> the Catalyst build won’t necessarily have any particular filter in it, I’d
> have to specify what I need in the cmake.sh ahead of time?
>
> ** **
>
> Mark
>
> ** **
>
> *From:* Andy Bauer [mailto:andy.ba...@kitware.com]
> *Sent:* Wednesday, August 14, 2013 8:48 PM
> *To:* Utkarsh Ayachit
> *Cc:* Vanmoer, Mark W; paraview@paraview.org
>
> *Subject:* Re: [Paraview] Building Catalyst
>
>  ** **
>
> Utkarsh,
>
>
> Is it worth the trouble to get rid of these error messages in Catalyst? **
> **
>
> Also, the most up-to-date version of the user's guide is at
> http://paraview.org/Wiki/images/4/48/CatalystUsersGuide.pdf.
>
> Andy
>
> ** **
>
> On Wed, Aug 14, 2013 at 9:33 PM, Utkarsh Ayachit <
> utkarsh.ayac...@kitware.com> wrote:
>
> These are more of warning than errors. Catalyst can be thought of as a
> stripped down ParaView. Several modules/components are removed to keep
> the package small. There will be several "editions" of catalyst based
> on which components they contain. The idea is one decides which
> filters/components they are interested in using in-situ. Then we can
> create a custom edition containing only those filters and the
> components needed to get those filters working. This is to keep the
> library size small for production runs. For testing, ParaView itself
> includes the library against which the simulation adaptors can link.
> Thus one can create/test adaptors using a regular ParaView itself.
> That will have all the modules ParaView includes and hence one can
> experiment with the which filters to use and pick to come up with the
> short list of filters that can then be used to create a custom
> edition. Within the next week or so, we are will have a couple more
> editions available that will include some of the commonly used
> filters.
>
> Hope that clarifies things  a bit. FYI, there's a user's guide
> available too that may help clarify this:
> http://public.kitware.com/pipermail/paraview/2013-July/028795.html
>
> Utkarsh
>
>
> On Wed, Aug 14, 2013 at 6:18 PM, Vanmoer, Mark W 
> wrote:
> > Okay, I was able to compile and run a Fortran code using the
> FortranAdaptorAPI and I'm getting some errors. (I had this code working
> with coprocessing and ParaView 3.14.1, so in theory it should still work).
> >
> > Error: Could not import vtkCommonComputationalGeometryPython
> > Error: Could not import vtkCommonMiscPython
> > Error: Could not import vtkCommonSystemPython
> > Error: Could not import vtkRenderingCorePython
> > Error: Could not import vtkFiltersCore
> > Error: Cannot import vtkPVServerManagerDefaultPython
> > Error: Cannot import vtkPVServerManagerRenderingPython
> > Error: Cannot import vtkPVServerManagerApplicationPython
> > Error: Could not create TimeKeeper
> > Error: Could not create AnimationScene
> >
> > How do I get Catalyst to import these? Is it just a matter of setting
> $PYTHONPATH?
> >
> > Mark
> >
> >
> >> -Original Message-
> >> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> >> Sent: Wednesday, August 14, 2013 4:05 PM
> >> To: Vanmoer, Mark W
> >> Cc: paraview@paraview.org
> >> Subject: Re: [Paraview] Bui

Re: [Paraview] Building Catalyst

[Vanmoer, Mark W]

Hi Andy and Utkarsh,
I'm not sure I can share the original code, so I tried the GitHub example Andy 
linked. I configured it to use the Catalyst build directory for ParaView_DIR. I 
still get the import errors, which I see I can ignore, but then also

Traceback (most recent call last):
  File "", line 2, in 
  File "coproc.py", line 74, in DoCoProcessing
coprocessor.UpdateProducers(datadescription)
  File 
"/home/mvanmoer/builds/Catalyst/1.0.alpha-build/lib/site-packages/paraview/coprocessing.py",
 line 102, in UpdateProducers
self.CreatePipeline(datadescription)
  File "coproc.py", line 30, in CreatePipeline
self.Pipeline = _CreatePipeline(self, datadescription)
  File "coproc.py", line 16, in _CreatePipeline
class Pipeline:
  File "coproc.py", line 19, in Pipeline
Slice1 = Slice( guiName="Slice1", Crinkleslice=0, SliceOffsetValues=[0.0], 
Triangulatetheslice=1, SliceType="Plane" )
NameError: name 'Slice' is not defined

Okay, is this because of what you're talking about below, Utkarsh?  That the 
Catalyst build won't necessarily have any particular filter in it, I'd have to 
specify what I need in the cmake.sh ahead of time?

Mark

From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Wednesday, August 14, 2013 8:48 PM
To: Utkarsh Ayachit
Cc: Vanmoer, Mark W; paraview@paraview.org
Subject: Re: [Paraview] Building Catalyst

Utkarsh,

Is it worth the trouble to get rid of these error messages in Catalyst?
Also, the most up-to-date version of the user's guide is at 
http://paraview.org/Wiki/images/4/48/CatalystUsersGuide.pdf.
Andy

On Wed, Aug 14, 2013 at 9:33 PM, Utkarsh Ayachit 
mailto:utkarsh.ayac...@kitware.com>> wrote:
These are more of warning than errors. Catalyst can be thought of as a
stripped down ParaView. Several modules/components are removed to keep
the package small. There will be several "editions" of catalyst based
on which components they contain. The idea is one decides which
filters/components they are interested in using in-situ. Then we can
create a custom edition containing only those filters and the
components needed to get those filters working. This is to keep the
library size small for production runs. For testing, ParaView itself
includes the library against which the simulation adaptors can link.
Thus one can create/test adaptors using a regular ParaView itself.
That will have all the modules ParaView includes and hence one can
experiment with the which filters to use and pick to come up with the
short list of filters that can then be used to create a custom
edition. Within the next week or so, we are will have a couple more
editions available that will include some of the commonly used
filters.

Hope that clarifies things  a bit. FYI, there's a user's guide
available too that may help clarify this:
http://public.kitware.com/pipermail/paraview/2013-July/028795.html

Utkarsh

On Wed, Aug 14, 2013 at 6:18 PM, Vanmoer, Mark W 
mailto:mvanm...@illinois.edu>> wrote:
> Okay, I was able to compile and run a Fortran code using the 
> FortranAdaptorAPI and I'm getting some errors. (I had this code working with 
> coprocessing and ParaView 3.14.1, so in theory it should still work).
>
> Error: Could not import vtkCommonComputationalGeometryPython
> Error: Could not import vtkCommonMiscPython
> Error: Could not import vtkCommonSystemPython
> Error: Could not import vtkRenderingCorePython
> Error: Could not import vtkFiltersCore
> Error: Cannot import vtkPVServerManagerDefaultPython
> Error: Cannot import vtkPVServerManagerRenderingPython
> Error: Cannot import vtkPVServerManagerApplicationPython
> Error: Could not create TimeKeeper
> Error: Could not create AnimationScene
>
> How do I get Catalyst to import these? Is it just a matter of setting 
> $PYTHONPATH?
>
> Mark
>
>
>> -Original Message-
>> From: Utkarsh Ayachit 
>> [mailto:utkarsh.ayac...@kitware.com]
>> Sent: Wednesday, August 14, 2013 4:05 PM
>> To: Vanmoer, Mark W
>> Cc: paraview@paraview.org
>> Subject: Re: [Paraview] Building Catalyst
>>
>> Great! Feel free to ping the list if you run into issues or need assistance.
>>
>> Utkarsh
>>
>> On Wed, Aug 14, 2013 at 4:21 PM, Vanmoer, Mark W
>> mailto:mvanm...@illinois.edu>> wrote:
>> > Utkarsh,
>> > It did build this time, thank you.
>> > Mark
>> >
>> >> -Original Message-
>> >> From: Vanmoer, Mark W
>> >> Sent: Wednesday, August 14, 2013 11:57 AM
>> >> To: 'Utkarsh Ayachit'
>> >> Cc: paraview@paraview.org
>> >> Subject: RE: [Paraview] Building Catalyst
>> >>
>> >> Utkarsh,
>> >> I was just running ccmake, I read the wiki as cmake.sh was for
>> >> building Catalyst from the ParaView source tree. I'll try the
>> >> cmake.sh with the new tarball and report back.
>> >>
>> >> Mark
>> >>
>> >> > -Original Message-
>> >> > From: Utkarsh Ayachit 
>> >> > [mailto:utkarsh.ayac...@kitware.com]
>> >> > Sent: Wednesday, A