Re: [Paraview] Updated OpenFOAMReader supporting OpenFOAM 5.x

[Allie Vacanti]

It looks like there are some issues preventing us from reviewing/merging
this patch, as I mentioned on the merge request here:
https://gitlab.kitware.com/vtk/vtk/merge_requests/3750

Once those are addressed we can do a more thorough code review/testing
cycle.

Thanks!
Allie

On Wed, Dec 27, 2017 at 11:36 AM, SeongMo  wrote:

> Hi, All
>
>
> I made a merge request for modified OpenFOAMReader classes for OpenFOAM
> 5.x.
>
> The classes are tested in ascii and binary formatted dictionary files and
> working well.
>
> I found that the reader has some problems when the dictionary file is
> gzipped either in ascii or binary formats.
>
> It looks like gzipped files are not read correctly because the
> GetFieldNames member function failed to find out field files. I tried to
> fix that problem but could not.
>
> The classes are uploaded in VTK gitlab repository but attached also so
> that you can freely test the classes and find out the problem.
>
>
> Regards.
>
> SeongMo
>
>
> --
> SeongMo Yeon, Ph.D, Senior Engineer
> Offshore Hydrodynamics Research
> SAMSUNG HEAVY INDUSTRIES CO., LTD.
> Central Research Institute
> E-mail : seongmo.y...@gmail.com
> Tel :
> 
> Fluctuat nec mergitur
>
>
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

[Paraview] How to plot selection over time of slice

[Kurt Sansom]

Hi all,
   I have a simulation where I have exported the inlets and outlets of a
domain. I was able to use a box clip for each inlet/outlet, calculate the
flux through each face, integrate, and then plot selection over time. I was
able to plot flow overt time. (this worked)

steps that work:
1) box clip the portion of the slice of interest
2) calculator to get flux
3) integrate variables
4) plot selection overtime

However, the problem I am having now, is that I want to take multiple slice
locations and do the same thing, however when i do the following.

1) create slice
2) box clip the portion of the slice of interest
3) calculator to get flux
4) integrate variables
5) plot selection overtime

There is no output. It's clear that the slice operation is doing something
different or I am missing a step such that I can't select the entity of
interest.


Regards,
  ~Kurt

-- 
Kurt Sansom
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview

Re: [Paraview] Confirming that pvserver runs with OSMesa + OpenSWR driver on cpu only compute nodes

[Burlen Loring]

Hi Fabrizio,

in the shell where you launch your pvserver you could set the following 
environment variables:


   export LIBGL_ALWAYS_SOFTWARE=1 GALLIUM_DRIVER=swr

this is bash syntax, your shell may be different. When I do that I see 
"SWR detected AVX" print in that shell when the connection to paraview 
client is made.


Burlen

On 12/21/2017 08:02 AM, Fabrizio Bisetti wrote:

Hello there:

I've successfully built and installed the following OSMesa rendering stack 
(from source) for use on CPU only compute nodes of a small cluster

I've then built Paraview 5.4.0 (from source). The pvserver runs on a compute 
node and we connect to it from a remote Paraview client via forward connection 
with SSH tunneling.

I am having trouble confirming which driver the pvserver uses for rendering. My 
understanding is that OSMesa gets compiled with various cpu-based driver 
options, i.e. soft pipe (classic OSMesa), llvmpipe, and swr.

I would like to ensure that swr (OpenSWR) is being used.

Note that one complicating factor is that the CPU-based compute nodes do not 
have any X installed and I've compiled only OSMesa (see below). Thus, I cannot 
compile the GLUT based utility glinfo or gears, which could possibly tell me 
how the rendering is done.

Finally, while it seems that one can invoke paraview with a switch 
--mesa-swr-avx2, I am not sure that can be done with pvserver.

Also, even then, how would I confirm this is which driver is being used?

Thank you for any help/pointers.

Fabrizio




**HARDWARE**

Each compute node features two (x2) Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz 
for a total of 28 cores. The compute nodes do not have a GPU.

**SOFTWARE STACK**

Everything is compiled with gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) 
on a Linux 3.10.0-514.el7.x86_64 (Centos 7).

Here is the cpu-based rendering stack

1) LLVM 5.0.0

cmake3 -G "Unix Makefiles"  \
-DCMAKE_BUILD_TYPE=Release \
-DLLVM_TARGETS_TO_BUILD=X86 \
-DLLVM_INSTALL_UTILS=TRUE \
-DLLVM_ENABLE_RTTI=TRUE \
-DBUILD_SHARED_LIBS=TRUE \
-DCMAKE_INSTALL_PREFIX=$INSTALLDIR \
../llvm-5.0.0.src

2) Mesa3D 17.3.0

Note that the compute nodes do not have any X servers (X11) nor any other 
OpenGL implementation (e.g. repo based from a yum install)

./configure \
 --disable-xvmc \
 --disable-glx \
 --disable-dri \
 --with-dri-drivers= \
 --with-gallium-drivers=swrast,swr \
 --enable-texture-float \
 --disable-egl \
 --disable-gbm \
 --with-platforms= \
 --enable-gallium-osmesa \
 --enable-llvm \
 --prefix=$INSTALLDIR

3) GLU 9.0.0

SITE_MESA_LIB=/path/to/mesa/install/above

PKG_CONFIG_PATH="$SITE_MESA_LIB/pkgconfig" \
OSMESA_LIBS="-L$SITE_MESA_LIB -lOSMesa" \
 ./configure --prefix=$INSTALLDIR \
 --enable-osmesa \
 --enable-shared

4) ParaView 5.4.0

I've configured the basic ParaView build as recommended.
I am using OpenMPI 2.1.0 compiled with the system gcc.

The additional OSMesa options are as below:

VTK_USE_X=OFF
VTK_USE_OFFSCREEN:BOOL=ON

OPENGL_INCLUDE_DIR=/path/to/mesa/install/above/include
OPENGL_gl_LIBRARY:FILEPATH=/path/to/mesa/install/above/lib/libOSMesa.so
OPENGL_glu_LIBRARY:FILEPATH=/path/to/glu/install/above/lib/libGLU.so

VTK_OPENGL_HAS_OSMESA:BOOL=ON
OSMESA_INCLUDE_DIR:PATH=/path/to/mesa/install/above/include
OSMESA_LIBRARY:FILEPATH=/path/to/mesa/install/above/lib/libOSMesa.so

Note that I've set everything to point to the OSMesa install directory.
___
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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://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

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
https://paraview.org/mailman/listinfo/paraview