<div dir="ltr">That was a P.<div><br><div style>When Mira@ANL ( a Q ) came out a few months ago, I briefly attempted to port the xlc_bgp config into an xlc_bgq config, but got bogged down in miscellaneous compilation issues and put it on hold.</div>
<div style><br></div><div style>It won't be that hard to do, it just takes a more time and patience than I had at the time.</div></div><div style><br></div><div style><br></div></div><div class="gmail_extra"><br clear="all">
<div>David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div>
<br><br><div class="gmail_quote">On Fri, Aug 30, 2013 at 10:10 AM, Benson Muite <span dir="ltr"><<a href="mailto:benson_muite@yahoo.com" target="_blank">benson_muite@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Can you let me know whether it is BG P or BG Q on which catalyst was built.<br>
<br>
Thanks,<br>
Benson<br>
<br>
On 30/08/2013 11:24, <a href="mailto:paraview-request@paraview.org">paraview-request@paraview.org</a> wrote:<br>
> 1. Re: Building on Titan using ParaViewSuperbuild (David E DeMarle)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Thu, 29 Aug 2013 16:08:13 -0400<br>
> From: David E DeMarle <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>><br>
<div class="im">> Subject: Re: [Paraview] Building on Titan using ParaViewSuperbuild<br>
</div>> To: "Vanmoer, Mark W" <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>><br>
> Cc: "<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>" <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br>
> Message-ID:<br>
> <<a href="mailto:CANjZAi-1K%2BBfLgLEvPeQdAu%2BwPT-AQKU0azDDcE4kCd-rOT1yg@mail.gmail.com">CANjZAi-1K+BfLgLEvPeQdAu+wPT-AQKU0azDDcE4kCd-rOT1yg@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
<div class="im">><br>
> On Thu, Aug 29, 2013 at 3:51 PM, Vanmoer, Mark W <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>>wrote:<br>
><br>
>> So coprocessing will not be built using the below instructions? I would<br>
>> have mentioned that, but coprocessing appears to<br>
>><br>
> still be part of a regular, non-cross-compile build, so I figured it was<br>
>> part of ENABLE_paraview<br>
>><br>
> The coprocessing plugin, which adds things to the GUI to make it easy to<br>
> record coprocessing pipeline setups doesn't need to be turned on since that<br>
> lives in the client only. (It is like python trace or state recording, but<br>
> tailored to recording in-situ setups).<br>
><br>
> Catalyst (the stripped down version of ParaView server that a simulation<br>
> code can link to and use to run those recorded pipelines quickly) is not<br>
> yet an option in ParaViewSuperbuild. To cross compile Catalyst a bit more<br>
> work will be required. It will follow the same plan as how the ParaView<br>
> server is compiled, but I just haven't tried it. When I did cross compile<br>
> Catalyst last year at this time I did the same steps that<br>
> ParaViewSuperbuild's TOOLS and CROSS build passes did, just by hand.<br>
><br>
>> Also, for the below configcross.sh, do we need to pass in a CMake variable<br>
</div>>> telling it where the tools build dir is located?****<br>
<div class="im">>><br>
>><br>
> That should be an option that you can easily set, but it isn't sorry.<br>
><br>
> CMake/CrossCompilationMacros.cmake assumes it can find it one directory up<br>
> and over like so:<br>
> macro(find_hosttools)<br>
> set(PARAVIEW_HOSTTOOLS_DIR<br>
> ${CMAKE_BINARY_DIR}/../tools/paraview/src/paraview-build/ CACHE PATH<br>
> "Location of host built paraview compile tools directory")<br>
> set(PYTHON_HOST_EXE ${CMAKE_BINARY_DIR}/../tools/install/bin/python CACHE<br>
> PATH<br>
> "Location of host built python executable")<br>
> set(PYTHON_HOST_LIBDIR ${CMAKE_BINARY_DIR}/../tools/install/lib CACHE PATH<br>
> "Location of host built python libraries")<br>
> set(BOOST_HOST_INCLUDEDIR ${CMAKE_BINARY_DIR}/../tools/install/include<br>
> CACHE PATH<br>
> "Location of host built boost headers")<br>
> endmacro()<br>
><br>
> You could predefine all four of those if you like.<br>
><br>
><br>
</div>>> Thanks,****<br>
>><br>
>> Mark****<br>
>><br>
>> ** **<br>
>><br>
>> *From:* David E DeMarle [mailto:<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>]<br>
>> *Sent:* Thursday, August 29, 2013 1:41 PM<br>
>> *To:* Hong Yi<br>
>> *Cc:* Vanmoer, Mark W; <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>><br>
>> *Subject:* Re: [Paraview] Building on Titan using ParaViewSuperbuild****<br>
>><br>
>> ** **<br>
>><br>
>> On Thu, Aug 29, 2013 at 2:13 PM, Hong Yi <<a href="mailto:hongyi@renci.org">hongyi@renci.org</a>> wrote:****<br>
<div class="im">>><br>
>> Hi David,<br>
>><br>
>> I just started to try superbuild on Titan also. I don't see you set<br>
>> ENABLE_MPI to be true in your configure script. Could you confirm whether<br>
>> ENABLE_MPI needs to be set to TRUE in order for ParaView to run on Titan in<br>
</div>>> parallel? Since my purpose is to link our****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> The ENABLE_MPI flag at the Superbuild level is unrelated. It has a purpose<br>
>> only when CROSS_BUILD_STAGE=HOST, that is when making ParaView binary<br>
</div>>> installers for desktops from Superbuild. ****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> You shouldn't turn it on in the TOOLS or CROSS stages. Instead let the<br>
>> CROSS stage use the system installed MPI. It does that by turning<br>
>> PARAVIEW_USE_MPI=ON when it configures the ParaView sub-build. See<br>
>> CMake/crosscompile/xk7_gnu to see where it does that, and to see the other<br>
</div>>> flags it uses.****<br>
>><br>
>> ****<br>
<div class="im">>><br>
>> simulation code (already built statically with CMake on Titan) to<br>
>> ParaView CoProcessing libraries (I am using version 3.98.1) for in-situ<br>
>> visualization on Titan, so in this case, do I have to set ENABLE_paraview<br>
>> to true and do I need to enable OSMesa for ParaView to resort to off-screen<br>
</div>>> rendering for in-situ visualization? ****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> The CROSS stage turns on Python, Mesa and ParaView. Titan's accelerators<br>
</div>>> don't really run X11, so Mesa is the only option for rendering there.****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> Although I can build ParaView from source on Titan login nodes, I am not<br>
>> able to run it on compute nodes, so I am starting to try superbuild hoping<br>
>> to be able to cross build ParaView libraries to run in-situ visualization<br>
</div>>> on Titan.****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> I've cross compiled Catalyst itself before on a bluegene. I did it<br>
>> manually before SuperBuild existed. I will see if I can dig up my config<br>
>> scripts. Cross compiling Catalyst should be more or less that same thing as<br>
>> cross compiling ParaView, but a bit faster and easier because their is less<br>
</div>>> code involved.****<br>
>><br>
>> ** **<br>
>><br>
>> Thanks,<br>
>> Hong****<br>
>> ------------------------------<br>
>><br>
>> *From:* <a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a> [<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>] on<br>
<div class="im">>> behalf of David E DeMarle [<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>]<br>
</div>>> *Sent:* Thursday, August 29, 2013 1:21 PM****<br>
>><br>
>><br>
>> *To:* Vanmoer, Mark W<br>
>> *Cc:* <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>> *Subject:* Re: [Paraview] Building on Titan using ParaViewSuperbuild****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> Your tools build is pointing to the compiler wrapper that you normally<br>
</div>>> would use to make code for the back end. ****<br>
<div class="im">>><br>
>> The tools build should just use plain old local gcc since we only build<br>
</div>>> things at that point that run on the login node.****<br>
>><br>
>> ** **<br>
>><br>
>> Try these setup scripts:****<br>
<div class="im">>><br>
>> I source configtools.sh to set up my environment before I build the<br>
</div>>> compile tools, and configcross.sh before before I cross compile ParaView.*<br>
>> ***<br>
>><br>
>> ** **<br>
>><br>
>> configtools.sh****<br>
>><br>
>> #use my own cmake, system one is too old****<br>
>><br>
>> setenv PATH<br>
>> /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}****<br>
>><br>
>> #switch compiler to compile code for front end****<br>
>><br>
>> module unload PrgEnv-pgi****<br>
>><br>
>> module load gcc****<br>
>><br>
>> #configure settings for to build compile tools only****<br>
>><br>
>> cmake \****<br>
>><br>
>> -DCROSS_BUILD_STAGE:STRING=TOOLS -Dcross_target:STRING=xk7_gnu \****<br>
>><br>
>> -DCMAKE_BUILD_TYPE:STRING=Release \****<br>
>><br>
>> -DBUILD_TESTING:BOOL=FALSE \****<br>
>><br>
>> -DParaView_FROM_GIT:BOOL=OFF \****<br>
>><br>
>> -DENABLE_paraview:BOOL=TRUE \****<br>
>><br>
>> -DENABLE_boost:BOOL=TRUE \****<br>
>><br>
>> -DENABLE_python:BOOL=TRUE \****<br>
>><br>
>> -DENABLE_portfwd:BOOL=FALSE \****<br>
>><br>
>> ../../ParaViewSuperbuild****<br>
>><br>
>> ** **<br>
>><br>
>> ** **<br>
>><br>
>> then make****<br>
>><br>
>> ** **<br>
>><br>
>> configcross.sh****<br>
>><br>
>> #use my own cmake, system one is too old****<br>
>><br>
>> setenv PATH<br>
>> /autofs/na4_proj/csc035/demarle/pvdev/titan/cmake-build/bin:${PATH}****<br>
>><br>
>> #switch compiler to compile code for back end****<br>
>><br>
>> module unload PrgEnv-pgi****<br>
>><br>
>> module unload gcc****<br>
>><br>
>> module load PrgEnv-gnu****<br>
<div class="im">>><br>
>> #not sure why module load wasn't sufficient, but ended up needing to force<br>
</div>>> ****<br>
>><br>
>> #cmake to choose the right compiler****<br>
>><br>
>> setenv CC /opt/cray/xt-asyncpe/5.17/bin/cc****<br>
>><br>
>> setenv CXX /opt/cray/xt-asyncpe/5.17/bin/CC****<br>
<div class="im">>><br>
>> #configure settings to cross compile python, (mesa - implied), and paraview<br>
</div>>> ****<br>
>><br>
>> cmake \****<br>
>><br>
>> -DCROSS_BUILD_STAGE:STRING=CROSS -Dcross_target:STRING=xk7_gnu \****<br>
>><br>
>> -DCMAKE_BUILD_TYPE:STRING=Release \****<br>
>><br>
>> -DBUILD_TESTING:BOOL=TRUE \****<br>
>><br>
>> -DParaView_FROM_GIT:BOOL=OFF \****<br>
>><br>
>> -DENABLE_paraview:BOOL=TRUE \****<br>
>><br>
>> -DENABLE_python:BOOL=TRUE \****<br>
>><br>
>> ../../ParaViewSuperbuild****<br>
>><br>
>> ** **<br>
>><br>
>> then make again****<br>
>><br>
>> ** **<br>
>><br>
>><br>
>> ****<br>
<div class="im">>><br>
>> David E DeMarle<br>
>> Kitware, Inc.<br>
>> R&D Engineer<br>
>> 21 Corporate Drive<br>
>> Clifton Park, NY 12065-8662<br>
</div>>> Phone: <a href="tel:518-881-4909" value="+15188814909">518-881-4909</a>****<br>
>><br>
>> ** **<br>
<div class="im">>><br>
>> On Tue, Aug 27, 2013 at 4:26 PM, Vanmoer, Mark W <<a href="mailto:mvanmoer@illinois.edu">mvanmoer@illinois.edu</a>><br>
</div>>> wrote:****<br>
<div class="im">>><br>
>> Hi, I'm trying to follow the advice on building ParaView on Titan using<br>
</div>>> the ParaViewSuperbuild method from an earlier discussion in June.****<br>
>><br>
>> ****<br>
>><br>
>> When I run make in the "TOOLS" directory I get the following error:****<br>
>><br>
>> ****<br>
>><br>
>> [ 66%] Building CXX object<br>
>> Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/ProcessXML.cxx.o****<br>
>><br>
>> Linking CXX executable ../../bin/vtkkwProcessXML-pv4.0****<br>
<div class="im">>><br>
>> /usr/bin/ld: attempted static link of dynamic object<br>
</div>>> `../../lib/libvtkCommonCore-pv4.0.so.1'****<br>
>><br>
>> collect2: error: ld returned 1 exit status****<br>
>><br>
>> make[6]: *** [bin/vtkkwProcessXML-pv4.0] Error 1****<br>
<div class="im">>><br>
>> make[5]: *** [Utilities/ProcessXML/CMakeFiles/kwProcessXML.dir/all] Error 2<br>
</div>>> ****<br>
>><br>
>> make[4]: *** [CMakeFiles/pvCompileTools.dir/rule] Error 2****<br>
>><br>
>> make[3]: *** [pvCompileTools] Error 2****<br>
<div class="im">>><br>
>> CMake Error at<br>
>> /ccs/home/vanmoer/builds/superbuild/tools-build/pv-paraview-build.cmake:26<br>
</div>>> (message):****<br>
>><br>
>> Failed!!!****<br>
>><br>
>> ****<br>
>><br>
>> ****<br>
>><br>
>> make[2]: *** [paraview/src/paraview-stamp/paraview-build] Error 1****<br>
>><br>
>> ****<br>
<div class="im">>><br>
>> I don't see a BUILD_SHARED that I can toggle. All of the<br>
</div>>> CMAKE_SHARED_LINKER_FLAGS* vars are empty, if those are related. ****<br>
>><br>
>> ****<br>
>><br>
>> Any suggestions?****<br>
>><br>
>> ****<br>
>><br>
>> Thanks,****<br>
>><br>
>> Mark****<br>
>><br>
>> ****<br>
>><br>
>> ****<br>
<div class="im">>><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>
</div>>> <a href="http://www.paraview.org/mailman/listinfo/paraview****" target="_blank">http://www.paraview.org/mailman/listinfo/paraview****</a><br>
>><br>
>> ** **<br>
>><br>
>> ** **<br>
>><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://www.paraview.org/pipermail/paraview/attachments/20130829/9f8989fe/attachment-0001.htm" target="_blank">http://www.paraview.org/pipermail/paraview/attachments/20130829/9f8989fe/attachment-0001.htm</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Fri, 30 Aug 2013 10:24:37 +0200<br>
> From: Richard GRENON <<a href="mailto:richard.grenon@onera.fr">richard.grenon@onera.fr</a>><br>
> Subject: Re: [Paraview] Performance of the CGNS Reader<br>
> To: Mickael Philit <<a href="mailto:mickey.phy@gmail.com">mickey.phy@gmail.com</a>><br>
> Cc: "Angelini, Richard C \(Rick\) CIV USARMY ARL \(US\)"<br>
> <<a href="mailto:richard.c.angelini.civ@mail.mil">richard.c.angelini.civ@mail.mil</a>>, "<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>"<br>
> <<a href="mailto:paraview@paraview.org">paraview@paraview.org</a>><br>
> Message-ID: <<a href="mailto:522056C5.3060202@onera.fr">522056C5.3060202@onera.fr</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
><br>
> Thank you for this answer, Mickael.<br>
><br>
> My 1.36 Gb CGNS dataset is built from structured meshes and Paraview<br>
> should not 'eat' too much memory. I have checked that enabling<br>
> multi-core in Paraview does not change anything: PV always needs about<br>
> 15 mn to load my dataset, same loading time as without multi-core.<br>
><br>
> I think that the loading time ratio 15 mn / 1 mn for PV against Tecplot<br>
> remains too high, even if PV parses the file two times. If Tecplot takes<br>
> advantage from multi-core (I don't know), the loading time ratio between<br>
> PV and Tecplot should not excess 8 when using 4 CPUs. A ratio of 15<br>
> leading to 15 mn of loading time or more for larger datasets is<br>
> unacceptable for interactivity. So PV is unusable for large CGNS<br>
> datasets, unless using batch mode. I think that an effort in redesigning<br>
> the CGNS reader would be welcome.<br>
><br>
> Best regards.<br>
><br>
> Richard<br>
><br>
> Le 29/08/2013 20:55, Mickael Philit a ?crit :<br>
>> Hello,<br>
>><br>
>> First, the CGNS reader coming through the VisItBridge is not working<br>
>> in parallel, it's a plain serial reader.<br>
>> Second, there are limitations to the current cgns reader way of doing<br>
>> thing, since :<br>
>> - At the beginning, it parses the whole file (this takes a lot of<br>
>> time) to get variable names, blocks and so on, before actually reading<br>
>> the data. [ I think that tecplot is cleaner because it seems to read<br>
>> the whole CGNS file in one pass ]<br>
>> - meshes are read in a temporary array and converted to a VTK vector<br>
>> of coordinates (thus memory manipulation)<br>
>> - for unstructured meshes, convertion from 'integer' to 'long' of<br>
>> cells connectivity eats memory.<br>
>> The CGNS reader can improve but at the cost of redesining some parts<br>
>> to fit better in paraview and go for parallel.<br>
>><br>
>> Mickael<br>
>><br>
>><br>
>> On 29/08/2013 16:50, Angelini, Richard C (Rick) CIV USARMY ARL (US)<br>
>> wrote:<br>
>>> As a followup to this that may be related - does the CGNS reader<br>
>>> through the VisItBridge work in parallel? I've loaded up a couple<br>
>>> of different CGNS datasets and then applied the ProcessIDScalars<br>
>>> filter and it doesn't appear to be distributing the data - even<br>
>>> multi-block CGNS files.<br>
>>><br>
>>><br>
>>> ________________________________<br>
>>> Rick Angelini<br>
>>><br>
>>> USArmy Research Laboratory<br>
>>> CISD/HPC Architectures Team<br>
>>> Building 120 Cube 315<br>
>>> Phone: 410-278-6266<br>
>>><br>
>>> ________________________________________<br>
>>> From: <a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a> [<a href="mailto:paraview-bounces@paraview.org">paraview-bounces@paraview.org</a>]<br>
>>> on behalf of Richard GRENON [<a href="mailto:richard.grenon@onera.fr">richard.grenon@onera.fr</a>]<br>
>>> Sent: Thursday, August 29, 2013 10:38 AM<br>
>>> To: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
>>> Subject: [Paraview] Performance of the CGNS Reader<br>
>>><br>
>>> Hello.<br>
>>><br>
>>> I am testing the CGNS reader of Paraview 4.0.1 64 bits running on a<br>
>>> Linux Workstation having 4 CPUs and 5.8 Gbytes of memory. Paraview was<br>
>>> installed from the binaries available on the download page.<br>
>>><br>
>>> I am trying to load a 1.36 Gbytes CGNS file that is available through<br>
>>> the network.<br>
>>><br>
>>> While loading this file, the Paraview Windows is frozen and cannot be<br>
>>> refreshed, and I must check with the "ps" command on a terminal window<br>
>>> or with a system monitor if PV is still running or if it is really<br>
>>> frozen. A progress bar for all readers would be welcome in a next<br>
>>> release.<br>
>>><br>
>>> Finally, the file can be loaded, but it always takes about 15 mn (+ or -<br>
>>> 1 mn depending of the load of the network), while Tecplot always loads<br>
>>> the same file within less that 1 mn !<br>
>>><br>
>>> How do you explain this poor performance of the CGNS reader ? Can it be<br>
>>> improved, or am I missing something ? Is there some Paraview option that<br>
>>> could reduce loading time of large files ?<br>
>>><br>
>>> Best regards<br>
<span class="HOEnZb"><font color="#888888">>>><br>
>>> --<br>
>>> Richard GRENON<br>
>>> ONERA<br>
>>> Departement d'Aerodynamique Appliquee - DAAP/ACI<br>
>>> 8 rue des Vertugadins<br>
>>> 92190 MEUDON - FRANCE<br>
>>> phone : <a href="tel:%2B33%201%2046%2073%2042%2017" value="+33146734217">+33 1 46 73 42 17</a><br>
>>> fax : <a href="tel:%2B33%201%2046%2073%2041%2046" value="+33146734146">+33 1 46 73 41 46</a><br>
>>> mailto:<a href="mailto:Richard.Grenon@onera.fr">Richard.Grenon@onera.fr</a><br>
>>> <a href="http://www.onera.fr" target="_blank">http://www.onera.fr</a><br>
</font></span><div class="HOEnZb"><div class="h5">>>><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>
>>> 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>