<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Andy and Utkarsh,
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Traceback (most recent call last):<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "<string>", line 2, in <module><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "coproc.py", line 74, in DoCoProcessing<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> coprocessor.UpdateProducers(datadescription)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "/home/mvanmoer/builds/Catalyst/1.0.alpha-build/lib/site-packages/paraview/coprocessing.py", line 102, in UpdateProducers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> self.CreatePipeline(datadescription)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "coproc.py", line 30, in CreatePipeline<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> self.Pipeline = _CreatePipeline(self, datadescription)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "coproc.py", line 16, in _CreatePipeline<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> class Pipeline:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> File "coproc.py", line 19, in Pipeline<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> Slice1 = Slice( guiName="Slice1", Crinkleslice=0, SliceOffsetValues=[0.0], Triangulatetheslice=1, SliceType="Plane" )<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">NameError: name 'Slice' is not defined<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">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?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Mark<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andy Bauer [mailto:andy.bauer@kitware.com]
<br>
<b>Sent:</b> Wednesday, August 14, 2013 8:48 PM<br>
<b>To:</b> Utkarsh Ayachit<br>
<b>Cc:</b> Vanmoer, Mark W; paraview@paraview.org<br>
<b>Subject:</b> Re: [Paraview] Building Catalyst<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Utkarsh,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Is it worth the trouble to get rid of these error messages in Catalyst? <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">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>.<o:p></o:p></p>
</div>
<p class="MsoNormal">Andy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Aug 14, 2013 at 9:33 PM, Utkarsh Ayachit <<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">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 style="color:#888888"><br>
<span class="hoenzb">Utkarsh</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><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><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>