[Paraview] Building Catalyst

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Fri Aug 16 11:42:29 EDT 2013 

Sounds good. Yea, using full ParaView to get off the ground may indeed
be the best approach. Once you start doing production runs, the
Editions would come in handy.

Utkarsh

On Fri, Aug 16, 2013 at 11:22 AM, Vanmoer, Mark W <mvanmoer at illinois.edu> wrote:
> Hi Andy and Utkarsh,
>
>
>
> Okay, so for the time being I decided to work with a fully blown Catalyst
> out of the ParaView src until I get my head around making editions. This
> allowed me to get the GitHub F90 example. However, with the original
> simulation, I have a different issue, which I’ll start in a new thread.
>
>
>
> Thanks,
>
> Mark
>
>
>
> From: Andy Bauer [mailto:andy.bauer at kitware.com]
> Sent: Thursday, August 15, 2013 9:47 AM
> To: Vanmoer, Mark W
> Cc: Utkarsh Ayachit; paraview at paraview.org
>
>
> Subject: Re: [Paraview] Building Catalyst
>
>
>
> 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 <mvanmoer at illinois.edu>
> 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 "<string>", line 2, in <module>
>
>   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.bauer at kitware.com]
> Sent: Wednesday, August 14, 2013 8:48 PM
> To: Utkarsh Ayachit
> Cc: Vanmoer, Mark W; paraview at 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.ayachit at 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 <mvanmoer at 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.ayachit at kitware.com]
>>> Sent: Wednesday, August 14, 2013 4:05 PM
>>> To: Vanmoer, Mark W
>>> Cc: paraview at 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
>>> <mvanmoer at 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 at 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.ayachit at kitware.com]
>>> >> > Sent: Wednesday, August 14, 2013 11:52 AM
>>> >> > To: Vanmoer, Mark W
>>> >> > Cc: paraview at paraview.org
>>> >> > Subject: Re: [Paraview] Building Catalyst
>>> >> >
>>> >> > Mark,
>>> >> >
>>> >> > No, you wouldn't need to use any external VTK. I've posted an
>>> >> > updated tarball. Feel free to give that a try. Also, how are you
>>> >> > starting the build? Using cmake.sh script included in the package?
>>> >> >
>>> >> > Utkarsh
>>> >> >
>>> >> > On Wed, Aug 14, 2013 at 11:38 AM, Vanmoer, Mark W
>>> >> > <mvanmoer at illinois.edu> wrote:
>>> >> > > Hi, I'm trying to build Catalyst using the tarball from the
>>> >> > > Catalyst download page. I'm getting the following error during
>>> >> > > the CMake configure
>>> >> > > step:
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > CMake Error at VTK/CMake/vtkModuleTop.cmake:29 (message):
>>> >> > >
>>> >> > >    No such module "vtkChartsCore" needed by
>>> >> > "vtkPVServerManagerApplication"
>>> >> > >
>>> >> > >    Call Stack (most recent call first):
>>> >> > >
>>> >> > >    VTK/CMake/vtkModuleTop.cmake:45 (vtk_module_check)
>>> >> > >
>>> >> > >    VTK/CMake/vtkModuleTop.cmake:52 (vtk_module_check)
>>> >> > >
>>> >> > >    VTK/CMakeLists.txt:348 (include)
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > Is all of the necessary VTK with the Catalyst tarball, or do I
>>> >> > > need to have a separate VTK build?
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > Thanks,
>>> >> > >
>>> >> > > Mark
>>> >> > >
>>> >> > >
>>> >> > > _______________________________________________
>>> >> > > 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
>>> >> > >
>>> >
>>
> _______________________________________________
> 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
>
>
>
>

More information about the ParaView mailing list