5
<https://bugreports.qt.io/browse/QTBUG-40485>
https://software.intel.com/en-us/node/744153
<https://software.intel.com/en-us/node/744153>
Jonathan Borduas
_____
From: Paul Melis <paul.me...@surfsara.nl
<mailto:paul.me...@surfsara.nl>>
Run with graphics processor -> High-performance
NVIDIA processor solved the problem.
Is this a known issue?
Regards,
Paul
--
Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.me...@surfsara.nl | www.surf
.0) anyway when requesting a 3.2 context. Does
ParaView, or VTK, use XRandR to get a valid window on which an OpenGL
context is created? Could this be a reason I see the 3.2 context
creation failure?
Regards,
Paul
--
Paul Melis
| Visualization group leader & developer | SURFsara |
| Sc
I got bitten by the default masking settings a couple of times as well.
Maybe change the default to not do masking when the number of input
points is low, like 1?
Paul
On 06/29/2016 12:23 AM, Scott, W Alan wrote:
Huangrui Mo,
Try outputting a glyph every point. On the Properties tab,
Paul
3. Interact with render view.
Do you get the same segfault? If so, it's independent of what you're
rendering, but just the fact that remote rendering kicks in. We can
then debug further.
Utkarsh
On Mon, Jun 27, 2016 at 11:37 AM, Paul Melis <paul.me...@surfsara.nl> wrote:
On 06/
On 06/27/2016 05:29 PM, Paul Melis wrote:
On 04/19/2016 01:04 PM, Paul Melis wrote:
Hi Utkarsh,
On 18-04-16 20:04, Utkarsh Ayachit wrote:
This has always worked for me with earlier versions of
ParaView, but something seems to have changed. It could be the
newer NVidia
driver we use since
On 04/19/2016 01:04 PM, Paul Melis wrote:
Hi Utkarsh,
On 18-04-16 20:04, Utkarsh Ayachit wrote:
This has always worked for me with earlier versions of
ParaView, but something seems to have changed. It could be the newer
NVidia
driver we use since a few weeks, but like I said, I don't see
, it will tell you how much pressure you are putting on your
memory.
Alan
-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Paul Melis
Sent: Thursday, June 16, 2016 2:52 AM
To: Geveci, Berk (External Contact) <berk.gev...@kitware.com>; Sven
a-window-here-a-window-there-a-window-everywhere approach. They are both
good and useful tools and are work-horses for scivis tasks. Whenever I
get a request from an HPC user which one to use I recommend ParaView, as
it is easier to get into for basic scivis work.
Regards,
Paul
--
Paul Melis
|
without a problem. A test between my workstation (PV client) and a
different machine (PV server) with driver 352.79 also works.
Paul
--
Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG Amsterdam |
| T 020 800 1312 | paul.me...@surfsar
we use since a few weeks, but like I said, I don't see
issues with any other OpenGL application.
Paul
Alan
-Original Message-
From: ParaView [mailto:paraview-boun...@paraview.org] On Behalf Of Paul Melis
Sent: Monday, April 18, 2016 3:55 AM
To: paraview@paraview.org
Subject: [EXTERNAL
w_indirect,
GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced,
GL_ARB_enhanced_layouts, GL_ARB_ES2_compatibility,
GL_ARB_ES3_compatibility, GL_ARB_ES3_1_compatibility,
--
Paul Melis
| Visualization group leader & developer | SURFsara |
| Science Park 140 | 1098 XG A
On 01/14/13 17:33, Paul Melis wrote:
I use the following Xdmf file to read this set into PV 3.14.1:
?xml version=1.0 ?
!DOCTYPE Xdmf SYSTEM Xdmf.dtd []
Xdmf
Domain
Grid Name=TheGrid GridType=Uniform
Topology TopologyType=3DRectMesh Dimensions=4096 4096 160/
Geometry
Hi all,
I have a rectilinear dataset of 4096x4096x160 floats with constant
spacing in X and Y, but varying spacing in Z. I've put the data in a
single HDF5 file (for now) with the following layout:
HDF5 ql200.hdf {
GROUP / {
DATASET ql {
DATATYPE H5T_IEEE_F32LE
DATASPACE SIMPLE
AM, Paul Melis paul.me...@sara.nl wrote:
Ah, missed that. But my issue is not that the LOD-rendering mesh is the
same as the fullres one (it's not, as expected), but that the LOD
resolution setting does not seem to influence the LOD mesh in my case.
Especially for a very large mesh I would expect
remember
changing vtkPVRenderView to accept LOD resolution as a normalized
value between [0,1], clearly I forgot to update the GUI. I'll push a
fix a post a patch.
Utkarsh
On Thu, Jun 21, 2012 at 5:35 AM, Paul Melis paul.me...@sara.nl wrote:
Hi Utkarsh,
I looked a bit into the code
think I know the problem. I remember
changing vtkPVRenderView to accept LOD resolution as a normalized
value between [0,1], clearly I forgot to update the GUI. I'll push a
fix a post a patch.
Utkarsh
On Thu, Jun 21, 2012 at 5:35 AM, Paul Melis paul.me...@sara.nl wrote:
Hi Utkarsh,
I looked
version did you apply the patch to?
Utkarsh
On Thu, Jun 21, 2012 at 8:14 AM, Paul Melis paul.me...@sara.nl wrote:
Thanks for the patch. I applied it but get really strange results I
can't quite explain. I can see the correct values now appearing in
vtkGeometryRepresentation
Argh, I see that git needs Qt 4.7.x :-/
On 06/21/2012 02:26 PM, Paul Melis wrote:
I applied it to the 3.14.1 sources. Perhaps I should indeed switch to
the git version.
Is the 3.14 client compatible with the server code in git?
On 06/21/2012 02:22 PM, Utkarsh Ayachit wrote:
With git
anomolies due
to the settings (for me, however, it works fine even when -dr isn't
specified.)
Utkarsh
On Thu, Jun 21, 2012 at 8:18 AM, Utkarsh Ayachit
utkarsh.ayac...@kitware.com wrote:
Paul,
What version did you apply the patch to?
Utkarsh
On Thu, Jun 21, 2012 at 8:14 AM, Paul Melis paul.me
Hi,
I'm doing remote rendering with PV 3.14.0, with quite a large set (isosurface
of 98M tris) on 16 render nodes, each with a GTX460 and 12 GB RAM (Linux 64-bit
cluster btw).
This model renders like a dog when interacting. I've checked the subsampling
settings, compression settings and LOD
:
Try reproducing with sphere source. Any luck?
On Wed, Jun 20, 2012 at 9:26 AM, Paul Melis paul.me...@sara.nl wrote:
It's already at 0 (see below).
Paul
On 06/20/2012 03:16 PM, Utkarsh Ayachit wrote:
WHat is the LOD Threshold set to? Try setting it to 0.
Utkarsh
On Wed, Jun 20, 2012 at 6
I actually get the same result when using the builtin server.
On 06/20/2012 03:34 PM, Paul Melis wrote:
Same result, I see no difference in meshes used during interaction
between 10x10x10 and 160x160x160 for LOD Resolution. Just to make sure:
- LOD Threshold is checked, set to 0.00 MBytes
It's already at 0 (see below).
Paul
On 06/20/2012 03:16 PM, Utkarsh Ayachit wrote:
WHat is the LOD Threshold set to? Try setting it to 0.
Utkarsh
On Wed, Jun 20, 2012 at 6:07 AM, Paul Melis paul.me...@sara.nl wrote:
Hi,
I'm doing remote rendering with PV 3.14.0, with quite a large set
Hmm, maybe not a good test, as depending on the sphere resolution a the
quadric clustering will produce the same results for a range of
dimension settings (i.e. 10^3 and up)
On 06/20/2012 03:36 PM, Paul Melis wrote:
I actually get the same result when using the builtin server.
On 06/20/2012
03:40 PM, Paul Melis wrote:
Hmm, maybe not a good test, as depending on the sphere resolution a the
quadric clustering will produce the same results for a range of
dimension settings (i.e. 10^3 and up)
On 06/20/2012 03:36 PM, Paul Melis wrote:
I actually get the same result when using
Does the LOD render use quadric clustering by the way?
And if so, should the LOD resolution setting produce the same mesh
during interactive rendering as when applying a Quadric Clustering
filter to the same input with the same resolution settings?
On 06/20/2012 03:40 PM, Paul Melis wrote:
Hmm
difference.
On 06/20/2012 04:03 PM, Utkarsh Ayachit wrote:
Look closely. They are not the same. Look the wireframing around the
centre of the sphere closely.
On Wed, Jun 20, 2012 at 9:53 AM, Paul Melis paul.me...@sara.nl wrote:
Hmmm, amiss at my end or in ParaView? The LOD and non-LOD views
Hi Dominik,
Just curious, but does your output resemble the pics in this bug report?
http://paraview.org/Bug/view.php?id=12509
Paul
On 03/16/12 19:50, Utkarsh Ayachit wrote:
Any more details to reproduce the issue? Can you reproduce it with
Wavelet source? I tried with Wavelet and seems to
, Paul Melis wrote:
Is this a problem with my local setup? If so, are there tests I can
do to figure out what's wrong?
I did some more testing and it is not a problem with my local setup,
as I can get correct GPU-based volume rendering with PV 3.12.0 in the
following two situations:
* Running PV
On 11/22/2011 10:08 AM, Paul Melis wrote:
Is this a problem with my local setup? If so, are there tests I can do
to figure out what's wrong?
I did some more testing and it is not a problem with my local setup, as
I can get correct GPU-based volume rendering with PV 3.12.0 in the
following two
Hi,
I'm running PV on an 8-node cluster in desktop-delivery mode. Each node
has an NVidia Geforce GTX460, NVidia driver 260.19.26, supporting OpenGL
4.1.0. OS is Debian 6.0 x86_64. In case it matters I pass
--use-offscreen-rendering to pvserver.
With both 3.10.1 and 3.12.0 GPU-based volume
Hi,
On 08/16/2011 06:22 PM, Utkarsh Ayachit wrote:
If you're writing out data that is already partitioned, you should
write it out as a collection of grids. Then each grid in that
collection is read on a separate partition.
Manual partitioning was something I was hoping to avoid. I figured
Hi Utkarsh,
On 08/16/2011 06:22 PM, Utkarsh Ayachit wrote:
If you're writing out data that is already partitioned, you should
write it out as a collection of grids. Then each grid in that
collection is read on a separate partition.
I followed your advice, but seem to have hit on another bug,
use to upload the dataset directly to us.
Utkarsh
On Mon, Aug 15, 2011 at 10:54 AM, Paul Melis paul.me...@sara.nl wrote:
On 08/15/2011 04:17 PM, Paul Melis wrote:
With a dataset stored in Xdmf I get an interesing data duplication
result. The set consists of 55296 points, each with associated
On 08/16/2011 04:23 PM, Utkarsh Ayachit wrote:
Thanks for reporting Paul. The issue is now fixed
(http://paraview.org/Bug/view.php?id=12527). The fix will make it into
git-master at the next gatekeeper review and will be included in 3.12.
No problem, thanks for the quick fix!
Attached is the
Hi,
With a dataset stored in Xdmf I get an interesing data duplication
result. The set consists of 55296 points, each with associated scalar
and vector values. See below for the XML file and HDF5 layout.
It loads fine when running PV standalone. But when loading this set on a
parallel PV server
On 08/15/2011 04:17 PM, Paul Melis wrote:
With a dataset stored in Xdmf I get an interesing data duplication
result. The set consists of 55296 points, each with associated scalar
and vector values. See below for the XML file and HDF5 layout.
[...]
?xml version=1.0?
Xdmf
Domain
Hello Robert,
On 08/05/2011 04:53 PM, Robert Maynard wrote:
I have seen this problem before you need to fix the MPI_INCLUDE_PATH to
only point to the directory that has mpi.h not both of those
directories. If this fixes the problem you should open a bug
on http://paraview.org/Bug
Hi,
I'm building PV 3.8.1 and PV 3.10.1 on exactly the same Debian 6.0
system (64-bit) system using the exact same CMAKE configuration lines:
#!/bin/sh
cmake \
-DCMAKE_BUILD_TYPE=Release \
-DMANTA_BUILD=$HOME/c/manta-2439-build \
-DMANTA_SOURCE=$HOME/c/manta-2439 \
?
A fresh build in a clean build directory (together with the cmake line
below) doesn't solve the problem. Note that I'm not setting the openmpi
header/library locations directly, but let CMake detect them. I assume
that's not a problem?
Regards,
Paul
On Fri, Aug 5, 2011 at 8:15 AM, Paul Melis
Hi,
I just noticed my cmake is 2.8.2, would trying the latest version help here?
Paul
On 08/05/2011 04:47 PM, Paul Melis wrote:
Hi David,
On 08/05/2011 02:55 PM, David Partyka wrote:
Have you turned MPI On then Off and then back On again? I've seen it get
confused when this happens
On 08/05/2011 04:53 PM, David Partyka wrote:
Yeah, FindMPI has recently been re-written I would update to the latest
and give that a shot.
With cmake 2.8.5 I get the following warning more than once during cmake
configure:
CMake Warning (dev) at
Hi,
This is an old post, to which I replied at the time, but now that I'm
rereading it I'm wondering whether the summary below was correct?
On 11/26/2009 07:50 AM, chew ping wrote:
so based on the timer log results that i collected, what i read about
offscreen-rendering and the explanation
for each
direction quite easily.
David E DeMarle
Kitware, Inc.
RD Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x109
On Thu, Mar 24, 2011 at 11:24 AM, Paul Melis paul.me...@sara.nl
mailto:paul.me...@sara.nl wrote:
Hi,
Is there in PV (3.8 / 3.10) a quick way
Hi,
With a freshly built PV 3.8.1 with CMake 2.8.4 I get (see attachement
for full log) this with make install:
[...]
-- Installing:
/home/opti/software/pv381reldebinfo/lib/paraview-3.8/purple-2/perl
-- Installing:
/home/opti/software/pv381reldebinfo/lib/paraview-3.8/purple-2/perl/auto
--
Hi,
Is there in PV (3.8 / 3.10) a quick way to switch between orthographic
and perspective projection? The only method I see is going through the
menu (Edit - View settings - General - Use Parallel Projection).
Thanks,
Paul
___
Powered by
Dear all,
Is it possible to use one of the parallel file formats to read in a 3D
image data set from a set of 2D slices, where the slice images remain in
a standard image format (e.g. PNG, JPEG)? Concretely, I have a set of
slices in PNG format and want to visualize/process the volume they
define
Hi,
Is there some documentation on the file format Cosmology files
(.cosmo) supported in PV? I've been reading Analyzing and visualizing
cosmological simulations with paraview by Woodring et.al, where the
cosmological support that was added to PV 3.8 is described. The .cosmo
file format is
Hi,
After starting a fresh PV3.8RC1 and pressing Ctrl+O to get started, I get:
QAction::eventFilter: ambiguous shortcut overload: Ctrl+O
... and no file open dialog.
Regards,
Paul
___
Powered by www.kitware.com
Visit other Kitware open-source
Felipe Bordeu Weldt wrote:
I'm using PV3.8RC1 for Mac and everything work fine.
are you using the linux or windows version ???
Oops, forgot the platform details. It's on 32-bit Linux, with PV 3.8 RC1
compiled against Qt 4.6.2 (the SDK version).
Paul
Hi,
I previously built PV 3.8 RC1 with cmake 2.6.4 successfully. I've now
switched to cmake 2.8.1 and compilation succeeds 99.9% :)
[...]
Scanning dependencies of target NIfTIWriter
[100%] Building CXX object
Plugins/AnalyzeNIfTIReaderWriter/CMakeFiles/NIfTIWriter.dir/qrc_NIfTIWriter.cxx.o
[100%]
Hi Sven,
Sven Buijssen wrote:
That's a known issue with PV 3.8 RC1 and CVS HEAD when compiling from scratch,
occurring on 64bit Linux systems, but not on 32bit Linux nor 64bit Solaris
SPARC. Don't know about Mac or Windows.
For completeness, this is on 32-bit Linux.
It is caused by
Hi,
Dave Partyka wrote:
Greetings Everyone,
We have just made ParaView 3.8.0 Release Candidate 1 binaries
available for download on the ParaView download page. Final binaries
and/or more release candidates should follow shortly after the Git
transition occurring next week.
Dave Partyka wrote:
Greetings Everyone,
We have just made ParaView 3.8.0 Release Candidate 1 binaries
available for download on the ParaView download page. Final binaries
and/or more release candidates should follow shortly after the Git
transition occurring next week.
Hi David,
David E DeMarle wrote:
When you configure manta, try turning MANTA_SSE off.
Right, that's what my next step turned out to be :)
Costs a lot of performance though... (8.7 fps instead 18 for the
standard manta demo).
Then rebuild paraview and try the manta plugin.
You may want to
David E DeMarle wrote:
When you configure manta, try turning MANTA_SSE off.
Then run manta to make sure that manta itself is working.
By the way, on a Vis09 presentation by Jon Woodrig, yourself and others
it is mentioned that you should configure manta with MANTA_USE_X11 to
OFF. Is that
David E DeMarle wrote:
As far as I know you don't _need_ to turn off X11 in manta to use it
in ParaView - I never do. Although I can think of reasons why it
_might_ make sense to do so I am not really sure why we made that
recommendation back then.
Well, I finally got the plugin to work
Utkarsh Ayachit wrote:
I cannot think of why this could be happening. Try playing with scalar
coloring on/off etc. for the glyphs.
What happens if you further process the gyphs, say pass through a shrink
filter?
No change, still no results.
One thing I just noticed in shock is that when
Hi,
I'm experimenting with running paraview on a remote visualization
server, using VirtualGL. This package basically lets you run an OpenGL
application as you normally would, but intercepts the swapbuffer events
to read back the framebuffer, which then gets JPEG compressed and sent
to a client
geometries at the same time and does that work?
Do you mean adding a Glyph filter twice, one set to e.g. Spheres, the
other to 2D vertex? If so, then this only shows the 2D vertices
Paul
On Wed, Mar 3, 2010 at 7:27 AM, Paul Melis paul.me...@sara.nl wrote:
Hi,
I'm experimenting
Utkarsh Ayachit wrote:
Do you mean adding a Glyph filter twice, one set to e.g. Spheres, the
other to 2D vertex? If so, then this only shows the 2D vertices
I meant simply try creating two sphere sources (with different
centers). Do both of them show up correctly?
Yes,
Paul
Hi Ken,
How does Paraview's tiled panel display support fit into this? Am I right in
assuming that in that case (without offscreen-rendering) the pvservers send
image output to the client, where a composited image is displayed? Or is the
client also doing local rendering of geometry sent to
Greg Abram wrote:
We have a 15x5 tiled display, and I'm thinking about running to the whole
thing.
If you do, can you keep us informed if you run into
http://public.kitware.com/Bug/view.php?id=8464 ?
If not, I'd be very interested to know how your setup differs from mine,
as it seems that
Paul Melis wrote:
The first thing that's off is that although I get undecorated Paraview
render areas on each panel display they don't fill the whole screen
(only roughly 75% in both width and height).
I did some more testing using a different setup (3 displays, vertically
stacked). I noticed
Hello,
pvserver --help reports:
--use-offscreen-rendering Render offscreen on the satellite processes.
This option only works with software rendering or mangled mesa on Unix.
Is this true? Is there no way to get offscreen hardware-accelerated
rendering in Paraview other than compiling with
Hello,
Paul Melis wrote:
Berk Geveci wrote:
Yeah, unfortunately it is hard for us to provide binaries with MPI
support because MPI is implemented with different (internal) APIs by
different vendors. We would have to create a different binary for each
MPI distribution
Hi,
I'm trying to get paraview to handle rendering on a single GPU with
dual-monitor outputs. These outputs are run using different X screens on
the same X server. Using xinerama is not an option as this is a
preliminary test setup for driving a TPD using nodes that each drive 2
displays and the
12, 2009 at 9:00 AM, Paul Melis paul.me...@sara.nl wrote:
Hi,
I'm trying to get paraview to handle rendering on a single GPU with
dual-monitor outputs. These outputs are run using different X screens on
the same X server. Using xinerama is not an option as this is a
preliminary test setup
69 matches
Mail list logo
