<div dir="ltr"><div><div>Utkarsh,<br></div><div><br>Is it worth the trouble to get rid of these error messages in Catalyst? <br><br></div>Also, the most up-to-date version of the user's guide is at <a href="http://paraview.org/Wiki/images/4/48/CatalystUsersGuide.pdf">http://paraview.org/Wiki/images/4/48/CatalystUsersGuide.pdf</a>.<br>
<br></div>Andy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 14, 2013 at 9:33 PM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">These are more of warning than errors. Catalyst can be thought of as a<br>
stripped down ParaView. Several modules/components are removed to keep<br>
the package small. There will be several "editions" of catalyst based<br>
on which components they contain. The idea is one decides which<br>
filters/components they are interested in using in-situ. Then we can<br>
create a custom edition containing only those filters and the<br>
components needed to get those filters working. This is to keep the<br>
library size small for production runs. For testing, ParaView itself<br>
includes the library against which the simulation adaptors can link.<br>
Thus one can create/test adaptors using a regular ParaView itself.<br>
That will have all the modules ParaView includes and hence one can<br>
experiment with the which filters to use and pick to come up with the<br>
short list of filters that can then be used to create a custom<br>
edition. Within the next week or so, we are will have a couple more<br>
editions available that will include some of the commonly used<br>
filters.<br>
<br>
Hope that clarifies things a bit. FYI, there's a user's guide<br>
available too that may help clarify this:<br>
<a href="http://public.kitware.com/pipermail/paraview/2013-July/028795.html" target="_blank">http://public.kitware.com/pipermail/paraview/2013-July/028795.html</a><br>
<span class="HOEnZb"><font color="#888888"><br>
Utkarsh<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Aug 14, 2013 at 6:18 PM, Vanmoer, Mark W <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>> wrote:<br>
> 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).<br>
><br>
> Error: Could not import vtkCommonComputationalGeometryPython<br>
> Error: Could not import vtkCommonMiscPython<br>
> Error: Could not import vtkCommonSystemPython<br>
> Error: Could not import vtkRenderingCorePython<br>
> Error: Could not import vtkFiltersCore<br>
> Error: Cannot import vtkPVServerManagerDefaultPython<br>
> Error: Cannot import vtkPVServerManagerRenderingPython<br>
> Error: Cannot import vtkPVServerManagerApplicationPython<br>
> Error: Could not create TimeKeeper<br>
> Error: Could not create AnimationScene<br>
><br>
> How do I get Catalyst to import these? Is it just a matter of setting $PYTHONPATH?<br>
><br>
> Mark<br>
><br>
><br>
>> -----Original Message-----<br>
>> From: Utkarsh Ayachit [mailto:<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>]<br>
>> Sent: Wednesday, August 14, 2013 4:05 PM<br>
>> To: Vanmoer, Mark W<br>
>> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>> Subject: Re: [Paraview] Building Catalyst<br>
>><br>
>> Great! Feel free to ping the list if you run into issues or need assistance.<br>
>><br>
>> Utkarsh<br>
>><br>
>> On Wed, Aug 14, 2013 at 4:21 PM, Vanmoer, Mark W<br>
>> <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>> wrote:<br>
>> > Utkarsh,<br>
>> > It did build this time, thank you.<br>
>> > Mark<br>
>> ><br>
>> >> -----Original Message-----<br>
>> >> From: Vanmoer, Mark W<br>
>> >> Sent: Wednesday, August 14, 2013 11:57 AM<br>
>> >> To: 'Utkarsh Ayachit'<br>
>> >> Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>> >> Subject: RE: [Paraview] Building Catalyst<br>
>> >><br>
>> >> Utkarsh,<br>
>> >> I was just running ccmake, I read the wiki as cmake.sh was for<br>
>> >> building Catalyst from the ParaView source tree. I'll try the<br>
>> >> cmake.sh with the new tarball and report back.<br>
>> >><br>
>> >> Mark<br>
>> >><br>
>> >> > -----Original Message-----<br>
>> >> > From: Utkarsh Ayachit [mailto:<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>]<br>
>> >> > Sent: Wednesday, August 14, 2013 11:52 AM<br>
>> >> > To: Vanmoer, Mark W<br>
>> >> > Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>> >> > Subject: Re: [Paraview] Building Catalyst<br>
>> >> ><br>
>> >> > Mark,<br>
>> >> ><br>
>> >> > No, you wouldn't need to use any external VTK. I've posted an<br>
>> >> > updated tarball. Feel free to give that a try. Also, how are you<br>
>> >> > starting the build? Using cmake.sh script included in the package?<br>
>> >> ><br>
>> >> > Utkarsh<br>
>> >> ><br>
>> >> > On Wed, Aug 14, 2013 at 11:38 AM, Vanmoer, Mark W<br>
>> >> > <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>> wrote:<br>
>> >> > > Hi, I'm trying to build Catalyst using the tarball from the<br>
>> >> > > Catalyst download page. I'm getting the following error during<br>
>> >> > > the CMake configure<br>
>> >> > > step:<br>
>> >> > ><br>
>> >> > ><br>
>> >> > ><br>
>> >> > > CMake Error at VTK/CMake/vtkModuleTop.cmake:29 (message):<br>
>> >> > ><br>
>> >> > > No such module "vtkChartsCore" needed by<br>
>> >> > "vtkPVServerManagerApplication"<br>
>> >> > ><br>
>> >> > > Call Stack (most recent call first):<br>
>> >> > ><br>
>> >> > > VTK/CMake/vtkModuleTop.cmake:45 (vtk_module_check)<br>
>> >> > ><br>
>> >> > > VTK/CMake/vtkModuleTop.cmake:52 (vtk_module_check)<br>
>> >> > ><br>
>> >> > > VTK/CMakeLists.txt:348 (include)<br>
>> >> > ><br>
>> >> > ><br>
>> >> > ><br>
>> >> > > Is all of the necessary VTK with the Catalyst tarball, or do I<br>
>> >> > > need to have a separate VTK build?<br>
>> >> > ><br>
>> >> > ><br>
>> >> > ><br>
>> >> > > Thanks,<br>
>> >> > ><br>
>> >> > > Mark<br>
>> >> > ><br>
>> >> > ><br>
>> >> > > _______________________________________________<br>
>> >> > > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> >> > ><br>
>> >> > > Visit other Kitware open-source projects at<br>
>> >> > > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> >> > ><br>
>> >> > > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> >> > > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
>> >> > ><br>
>> >> > > Follow this link to subscribe/unsubscribe:<br>
>> >> > > <a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
>> >> > ><br>
>> ><br>
><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br></div>