Re: [Paraview] Multi Block Data Set

2017-05-12 Thread Cory Quammen 
"Extract Block" will copy a selected block to a new data set that you
can reposition. The original block will remain in the original
dataset, which maybe isn't what you want. You could also pick the
inverse selection of blocks in a second "Extract Block" filter and
then apply the "Group" filter to put the moved block and other blocks
again.

HTH,
Cory

On Fri, May 12, 2017 at 4:22 PM, Dean, Kevin
 wrote:
> Hello,
>
> Is there a way to select a block from a multiblock dataset and update its
> position independent of the rest of the dataset?
>
> Kevin Dean
>
> This email and its contents are confidential. If you are not the intended
> recipient, please do not disclose or use the information within this email
> or its attachments. If you have received this email in error, please report
> the error to the sender by return email and delete this communication from
> your records.
> ___
> 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:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
Staff R Engineer
Kitware, Inc.
___
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:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Multi Block Data Set

2017-05-12 Thread Dean, Kevin 
Hello,

Is there a way to select a block from a multiblock dataset and update its
position independent of the rest of the dataset?

Kevin Dean

-- 
This email and its contents are confidential. If you are not the intended 
recipient, please do not disclose or use the information within this email 
or its attachments. If you have received this email in error, please report 
the error to the sender by return email and delete this communication from 
your records.
___
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:
http://public.kitware.com/mailman/listinfo/paraview

Re: [Paraview] gpu_shader4 extension is not supported

2017-05-12 Thread Burlen Loring 

Hi Patrick,

OSMesa (and friends such as OpenSWR) do not need to make use of GLX. In 
fact I think it should be disabled completely for that case in both Mesa 
and ParaView builds. For eg, when you configure ParaView you'd specify 
-DVTK_USE_X=OFF. At least this is how it was in the past. I haven't been 
following developments lately. The wiki 
 has specifics.


Burlen

On 05/12/2017 07:25 AM, Patrick Begou wrote:

Hi,

I'm still trying to build paraview 5.3 with Qt4.8. As paraview 
superbuild was failing on my desktop (centos 6.9, Nvidia GPU), I build 
paraview by hand and it is running now with and without pvserver 
connection

.
The problem went back with building same paraview version on the 
cluster frontend: CentOS 6.7, no GPU. The compilation is successfull 
but launching paraview I get some errors with OpenGL:


ERROR: In 
/kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, 
line 825
vtkXOpenGLRenderWindow (0x2280fb0): GL version 2.1 with the 
gpu_shader4 extension is not supported by your graphics driver but is 
required for the new OpenGL rendering backend. Please update your 
OpenGL driver. If you are using Mesa please make sure you have version 
10.6.5 or later and make sure your driver in Mesa supports OpenGL 3.2.


ERROR: In 
/kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, 
line 812

vtkXOpenGLRenderWindow (0x2280fb0): failed to create offscreen window

ERROR: In 
/kareline/data/begou/PARAVIEW5/paraview/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, 
line 813

vtkXOpenGLRenderWindow (0x2280fb0): GLEW could not be initialized.

I've built and installed mesa from mesa-17.0.4.tar.gz using:
./configure \
PKG_CONFIG_PATH=/share/apps/paraview-5.3.0/lib/pkgconfig \
--prefix=/share/apps/paraview-5.3.0 \
--disable-osmesa --enable-gallium-osmesa --enable-gallium-llvm \
--with-llvm-prefix=/share/apps/paraview-5.3.0

With several requested libraries:
libxshmfence-1.2.tar.gz
libxcb-1.12.tar.gz
libXau-1.0.8.tar.gz
pthread-stubs-0.3.tar.gz
xcb-proto-1.12.tar.gz
libdrm-2.4.70.tar.gz
llvm-4.0.0.src.tar.xz
all under /share/apps/paraview-5.3.0/

I've checked with strace that paraview was loading libGL in 
/share/apps/paraview-5.3.0/lib and not the system one, requested by 
other application (frontend is in production and I cannont break these 
libraries used by other softwares).



I must confess I'm not familiar at all with these libraries and 
environments, mesa or osmesa, GPU or not GPU, of screen rendering... 
all documentation deeping in obscure details while I'm searching to 
understand these concepts.
it is clear for me that on the nodes (without GPU) I will use OSMesa 
and no GUI, but on the frontend where I need GUI ???


Thanks for your advices and sorry if this is a very basic lack of 
understanding from myself.


Patrick


Paraview cmake is:
ccmake -DBUILD_SHARED_LIBS=ON \
   -DPARAVIEW_USE_MPI=ON \
   -DCMAKE_BUILD_TYPE=Release \
   -DPARAVIEW_BUILD_QT_GUI=ON \
   -DPARAVIEW_QT_VERSION=4 \
-DQT_QMAKE_EXECUTABLE=/share/apps/paraview-5.3.0/qt4.8.6/bin/qmake \
   -DPARAVIEW_ENABLE_FFMPEG=ON \
   -DPARAVIEW_ENABLE_PYTHON=ON \
-DPYTHON_INCLUDE_DIR=/share/apps/python279/include/python2.7 \
-DPYTHON_LIBRARY=/share/apps/python279/lib/libpython2.7.so \
-DPYTHON_LIBRARY_DEBUG=/share/apps/python279/lib/libpython2.7.so \
   -DCMAKE_INSTALL_PREFIX=/share/apps/paraview-5.3.0 \
   -DCMAKE_VERBOSE_MAKEFILE=ON \
   -DCMAKE_CXX_COMPILER=/share/apps/GCC485/bin/g++ \
   -DCMAKE_C_COMPILER=/share/apps/GCC485/bin/gcc \
-DCMAKE_Fortran_COMPILER=/share/apps/GCC485/bin/gfortran \
   -DFFMPEG_ROOT=/share/apps/paraview-5.3.0 \
-DOPENGL_INCLUDE_DIR=/share/apps/paraview-5.3.0/include \
-DOPENGL_gl_LIBRARY=/share/apps/paraview-5.3.0/lib/libGL.so \
 ../paraview


--
===
|  Equipe M.O.S.T. |  |
|  Patrick BEGOU   |mailto:patrick.be...@grenoble-inp.fr  |
|  LEGI|  |
|  BP 53 X | Tel 04 76 82 51 35   |
|  38041 GRENOBLE CEDEX| Fax 04 76 82 52 71   |
===


___
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:
http://public.kitware.com/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

Re: [Paraview] [Non-DoD Source] Re: ResetCamera throwing bad_alloc

2017-05-12 Thread Utkarsh Ayachit 
Joe,

I suspect there is indeed some data corruption going on. Do you have a
debug build? Or can you share the data with me? Let's see where the
exception is being thrown that will illuminate the problem.

Utkarsh

On Thu, May 11, 2017 at 6:17 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL
(US)  wrote:

> Utkarsh,
>
> It does not crash when it is commented out.
>
> It is trying to read an ExodusII file
>
> # create a new 'ExodusIIReader
> test_data = ExodusIIReader(FileName=path)
>
> # show data in view
> test_Display = Show(test_data, renderView1)
>
> but does not crash until ResetCamera is called.
>
> So, I guess the problem is with the ExodusIIReader,
> and just doesn't manifest until the ResetCamera,
> triggers an update to the pipeline. I know the data
> is okay as I can read it with another version of ParaView
> 5.3.0 on the same system.
>
> Thanks,
>
> Joe
>
> ~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
> Aberdeen Proving Ground, MD 21005
> Voice:  410-278-3619
> Fax:410-278-8799
> Email:  joseph.g.hennessey2@mail.mil
>
>
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Thursday, May 11, 2017 3:44 PM
> To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
> 
> Cc: paraview@paraview.org
> Subject: [Non-DoD Source] Re: [Paraview] ResetCamera throwing bad_alloc
>
> All active links contained in this email were disabled. Please verify the
> identity of the sender, and confirm the authenticity of all links contained
> within the message prior to copying and pasting the address to a Web
> browser.
>
>
> 
>
>
>   Joe,
>
> Do you see the error if you comment out all the "#Show stuff in
> renderView1" part?
>
> Utkarsh
>
> On Thu, May 11, 2017 at 3:13 PM, Hennessey, Joseph G CTR USARMY RDECOM ARL
> (US)  Caution-mailto:joseph.g.hennessey2@mail.mil > > wrote:
>
>
> Hello,
>
> I am getting an error on running a python script with pvpython and
> ParaView
> 5.3.0 on linux.
>
> # get active view
> renderView1 = GetActiveViewOrCreate('RenderView')
>
> # uncomment following to set a specific view size
> renderView1.ViewSize = [1200, 600]
>
> # Properties modified on renderView1
> renderView1.Background = [1.0, 1.0, 1.0]
>
> #Show stuff in renderView1
> .
> .
> .
>
> # reset view to fit data
> renderView1.ResetCamera()
>
> ResetCamera() is throwing an error
>
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
>
> Has anyone seen this particular error before with just calling
> ResetCamera()
> on a renderView?
>
> Thanks,
>
> Joe
>
> ~~~
> Joseph G. Hennessey Ph.D., SAIC
> Team SAIC
> Army Research Lab
> DOD Supercomputing Resource Center
>
>
> ___
> Powered by Caution-www.kitware.com < Caution-
> http://www.kitware.com >
>
> Visit other Kitware open-source projects at
> Caution-http://www.kitware.com/opensource/opensource.html <
> Caution-http://www.kitware.com/opensource/opensource.html >
>
> Please keep messages on-topic and check the ParaView Wiki at:
> Caution-http://paraview.org/Wiki/ParaView <
> Caution-http://paraview.org/Wiki/ParaView >
>
> Search the list archives at: Caution-http://markmail.org/
> search/?q=ParaView <
> Caution-http://markmail.org/search/?q=ParaView >
>
> Follow this link to subscribe/unsubscribe:
> Caution-http://public.kitware.com/mailman/listinfo/paraview <
> Caution-http://public.kitware.com/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:
http://public.kitware.com/mailman/listinfo/paraview

[Paraview] Fwd: [ParaView.org Contact Form] Consulting form

2017-05-12 Thread Mathieu Westphal 
Thanks Mathieu, that’s really helpful. The compute power for the datasets
being visualised will be making use of some kind of HPC, most likely.



There is currently some consideration of using Chromebooks for the course,
does anyone on the mailing list have any experience of using these with
ParaView?



Best wishes,



Kat



*From:* Mathieu Westphal [mailto:mathieu.westp...@kitware.com]
*Sent:* 11 May 2017 12:11
*To:* Helene Grandmontagne ; Parkins, Kat
; ParaView 
*Subject:* Re: [ParaView.org Contact Form] Consulting form



Dear Mr. Parkins

Since your question may be better suited for the ParaView mailing-list,
i've included it in the recipient.

ParaView hardware requirement are pretty basic, however it may grow
depending on the data you want to handle and the type of operation you want
to do on it.

For a visualisation course, there is no reason to handle large dataset, so
in this case basic requirement should suffice.

CPU : Any kind of modern processor (lets say Core 2 Duo and after)

RAM : 4Gb (must be able to open your dataset basically)

300 Mb of disk space

Recommended : OpenGL 3.2 capable GPU (nVidia 100M / Intel HD400 and after,
with updated drivers)

So as you can see, it is not much.

Regards,


Mathieu Westphal



On Thu, May 11, 2017 at 7:38 AM, Helene Grandmontagne <
helene.grandmonta...@kitware.com> wrote:

Hello,



Est-ce que je peux te laisser lui répondre?



Hélène



-- Forwarded message --

From: 
Date: Wed, May 10, 2017 at 3:19 PM
Subject: [ParaView.org Contact Form] Consulting form
To: kitw...@kitware.com


Name: Kat Parkins
Phone: 07872 850292
Email: k.park...@imperial.ac.uk
TimeZone: Europe
Description: Hi, I'd like to talk to someone about the hardware
requirements for Paraview. A new course is planning to teach students to
visualise data, and we need to look at the cost of the laptops needed to do
this.

Thanks,

Kat



-- 

Hélène Grandmontagne

Business development engineer

Kitware SAS

26 rue Louis Guérin

69100 Villeurbanne, France

F: +33 (0)4.37.45.04.15 <+33%204%2037%2045%2004%2015>
http://www.kitware.fr

-- 

Hélène Grandmontagne

Business development engineer

Kitware SAS

26 rue Louis Guérin

69100 Villeurbanne, France

F: +33 (0)4.37.45.04.15 <+33%204%2037%2045%2004%2015>
http://www.kitware.fr
___
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:
http://public.kitware.com/mailman/listinfo/paraview