CLASSIFICATION: UNCLASSIFIED
Utkarsh,
I am running ParaView 5.0.1 connecting to a remote ParaView 5.0.1 server built
with osmesa
And I have rebuild osmesa from both
Mesa 11.1.2 and Mesa 11.2.2 using
./configure \
--disable-xvmc \
--disable-glx \
--disable-dri \
--with-dri-drive
nks,
Joe
~~~
Joseph G. Hennessey Ph.D., Lockheed Martin Army Research Lab DOD Supercomputing
Resource Center
Email: joseph.g.hennessey2@mail.mil
-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Hennessey,
Joseph G
nal Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Thursday, June 02, 2016 4:19 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Cc: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US)
; Su, Simon M CIV USARMY RDECOM ARL (US)
; ParaView
Subject: Re: [Paraview] [
CLASSIFICATION: UNCLASSIFIED
Rick,
In the superbuild source directory
The file
CMake/DetermineParaViewVersion.cmake line 10
Change
set (hardcoded_paraview_version "5.0.1")
to
set (hardcoded_paraview_version "5.1.0")
Thanks,
Joe
~~~
Joseph G. Hennessey Ph.D
CLASSIFICATION: UNCLASSIFIED
Hello,
I am experiencing an error when running ParaView 5.1.0 using VGL
When starting ParaView 5.1.0 I get the following warnings
[VGL] WARNING: The OpenGL rendering context obtained on X display
[VGL]:0.0 is indirect, which may cause performance to suffer.
[VGL
ssey,
Joseph G CTR USARMY RDECOM ARL (US)
Subject: Re: [Non-DoD Source] Re: [Paraview] 5.1.2/OpenGL2 issue
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
CLASSIFICATION: UNCLASSIFIED
Hello,
I am seeing an error when attempting to load PLY files formed
from saving parallel .vtm surface files that have been saved in
the PLY format. The file name convention for loading them at once
seems to break down and only load random subsections of the .vtm
fi
CLASSIFICATION: UNCLASSIFIED
Hello,
Recent versions of ParaViewData (5.0.0 and above) have their file names as
md5 sums.
While version 4.4.0 of ParaViewData and earlier used human readable names.
Is there still a version of ParaViewData (5.0.0 and above) that has human
readable names?
Thank,
Jo
CLASSIFICATION: UNCLASSIFIED
Hello,
I have found that pvbatch is silently failing in a python file when
WriteAnimation
is called and used with ParaView 5.2.0 under linux.
But pvpython will execute the same command from the same python file
correctly.
The call where it is failing is below
Write
anks,
Joe
~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
-Original Message-
From: Andy Bauer [mailto:andy.ba...@kitware.com]
Sent: Tuesday, January 10, 2017 9:52 AM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Cc
CLASSIFICATION: UNCLASSIFIED
Hello,
ParaView 5.1.2 is not recording changes to the LUT Scalar Bar position and
size when tracing is one with all options.
And that even when I manually set the positions of the LUT in the script
file run by pvpython,
Paraview will seem to pull the settings for th
CLASSIFICATION: UNCLASSIFIED
Alessandro,
This looks like a useful feature to add to the reader, and we will put in our
list of things to work on. But, I can not immediately implement this as we
have a number of high priority updates such as c++11 support, and an updated
base Xdmf library curre
CLASSIFICATION: UNCLASSIFIED
Hello,
I am finding that the volume rendering is not working with
OSPRay Renderer not working with ParaView 5.3.0-RC3.
The volume render sample that I am testing looks fine
when rendered with the default renderer, but when I switch to the
OSPRay volume renderer,
ource Center
-Original Message-
From: David E DeMarle [mailto:dave.dema...@kitware.com]
Sent: Wednesday, March 08, 2017 3:02 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Cc: paraview@paraview.org
Subject: [Non-DoD Source] Re: [Paraview] Volume rendering with OSPRay Renderer
not wo
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
render
y 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 authentic
Hello,
I am the one who requested the changes,
they were made to correct the stereo separation with working with zSpace
hardware
for data that was small in size (floating point values of coordinates, >> 1,
for example data that ranged from 0.000 to 0.001
I checked its use with data across
such as the zSpace.
Thanks,
Joe
~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
DOD Supercomputing Resource Center
Email: joseph.g.hennessey2@mail.mil
-Original Message-
From: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Sent: Monday
Hello,
I am trying to monitor the progress of a paraview filter (contour)
on rather large data, so that I could predict when it will finish.
Is there a recommended way to do this? I am running using
42 paraview servers and I cannot find an easy way of estimating
the filter percent of progress or
Hello,
Has anyone managed to use ParaView 5.4.x with more than 64 core
on a single node when running in client/server moder.
Thanks,
Joe
~~~
Joseph G. Hennessey Ph.D., SAIC
Team SAIC
Army Research Lab
Email: joseph.g.hennessey2@mail.mil
smime.p7s
Descri
Hello,
I have been running into problems with
mpi4py and SGI's mpt 2.14 and 2.15 versions of MPI
while compiling ParaView 5.3.0 on HPC systems.
mpi4py cannot find MPI_CONVERSION_FN_NULL
when compiling mpi4py.MPI.c
MPI_CONVERSION_FN_NULL was not used by the
version of mpi4py that came with ParaV
Hello,
I am experiencing an error with volume rendering very large
tetrahedral data with ParaView version 5.4.1.
The data is loaded properly and the surface representation works,
but when I change the representation to Volume, I get the standard
dialog below to which I respond "Yes"
'This wil
anuary 24, 2018 4:00 PM
To: Hennessey, Joseph G CTR USARMY RDECOM ARL (US)
Cc: paraview@paraview.org
Subject: [Non-DoD Source] Re: [Paraview] Error when trying to turn on Volume
Rendering for large tetrahedral data in ParaView 5.4.1
All active links contained in this email were disabled. Please
23 matches
Mail list logo
