Hi Ken,
The data dimensions are: 116 x 51 x 51 (xyz), so the model extent was set to:
X = 0 - 115, Y = 0 - 50, Z = 0 -50
These extents work fine and no errors assciated with the input, and no
missing nodes. The model comprises 51 layers and each is 116 x 51 and
all have the total 5916.
Not sure
Dear Utkarsh,
can you give a quick update whether the suggested bug fix is likely to be
solved:
> Proxies are being created before the session was "ready for use". Like
> I said, collaboration isn't being used actively in production so such
> issues are expected. Since I don't have active
Hi Cory,
thanks for link to the developer mailing list discussion. I think CMake 3.3 is
better then
3.5, because at least the last Leap 42.1 release provides that.
I patched ParaView to require CMake 3.0 and it builds fine. I will package
ParaView 5.1
that way and hope you reduce the requirement
Hi Christoph,
Thank you for working on packaging ParaView for openSUSE!
Please see this discussion in the paraview-developers mailing list
archive that gives reasons for updating the required version of CMake
to 3.5:
http://public.kitware.com/pipermail/paraview-developers/2016-April/004229.html
Just FYI, Version 5.1.0 seems to fix most of the z-sorting issue I was
kvetching about prior to the weekend. However, intersecting cross
section planes still do not properly occlude one another.
Tested on Ubuntu Studio 16.04.
spl
Dear Paraview developers,
congratulations to the 5.1 release and thanks for your hard work!
I currently try to package it for openSuse and I stumbled upon the
required CMake version. What's the reason for this harsh requirement?
Wouldn't be 3.0 or similar be sufficient?
Currently all stable
Jim,
I think I'm pretty confused about what you are trying to do. I don't know what
you mean by "pick center on one of the glyphs." Can you back up and describe in
detail how you are setting up your visualization. What you use to read the
data, what filters you apply, how you set up the
Lester,
What are the dimensions of the grid in the table? Are they 116x51x51 or
115x50x50?
The extent that you set in the TableToStructuredGrid filter uses inclusive
indices. That means they should go from 0 to one less than the size of the
dimension. So if your grid is 115x50x50, then the
Folks,
ParaView 5.1.0 is now available for download [1]. Please refer to the
release notes on the Kitware blog [2]. As always, we look forward to
your feedback [3].
Also stay tuned to the Kitware Blog [4] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
I'd like to add review of merge requests to the agenda.
On Jun 20, 2016 10:57 PM, "Utkarsh Ayachit"
wrote:
> +1. I will be there.
>
> On Mon, Jun 20, 2016 at 4:30 PM, Berk Geveci
> wrote:
> > Hi folks,
> >
> > We are planning a ParaView bug
Hello,
I have tried to generate a structured grid from a csv file comprising
51 layers with X and Y as Long and Lat respectively.
(1) Load CSV file
(2) Filter -> TableToStructuredGrid
set dimensions:
x = 0 - 115
y = 0 - 50
z = 0 - 50
This all works fine, but the plot is skewed oddly in the
Hi,
We have come across a minor but annoying bug in the Paraview OPENFOAM reader.
The component of the Paraview OPENFOAM parser that reads boundary conditions
has been set up to always expect another number where a scalar is encountered
in the following configuration:
(1.111 ###
when you
We use the ParaView super build project to build paraview and all of its
dependencies for our binaries (and for some supercomputers as well).
* https://gitlab.kitware.com/paraview/paraview-superbuild
David E DeMarle
Kitware, Inc.
R Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone:
Hi! Where I can find actual Paraview v5.1 build script for Windows?
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
14 matches
Mail list logo