Saideep,
This may or may not be what you are asking for, but you should be able to get
the exact location of the contour on the boundaries by first extracting the
boundary and then running the contours on the boundary. This will give you the
contours on the boundary only.
How you get the
No objection there. I'd suggest reporting an issue for the same,
otherwise it's going to get lost and forgotten.
https://gitlab.kitware.com/paraview/paraview/issues
On Fri, Sep 9, 2016 at 1:28 PM, Dennis Conklin
wrote:
> Utkarsh,
>
> Okay, thanks for that
Hi guys;
Is there a way to know the precise location of a contour on the boundaries (as
shown in picture)? I use the traditional tool "ruler", however when I have too
many points to measure (as in the figure) by hand it gets complicated.
I tried using the integrate variables(selecting the
Utkarsh,
Okay, thanks for that explanation. I have some comments.
The documentation is very confusing and/or incomplete and misleading.
Hovering over the expression box produces a popup which makes it seem as though
t-index is the way to access things. No real distinction is made between
Looking at the old error reports, it's an issue of differences in indexing in
programming languages. I guess Paraview was initially designed with Fortran's
output in mind?
-Andrew Burns
-Original Message-
From: Lúcio Corrêa [mailto:labcor...@gmail.com]
Sent: Friday, September 09, 2016
Dennis,
Python Annotation only works with what's available in the current
timestep. If you look at the "Field Data" in the SpreadSheet view,
you'll see that the Exodus reader puts out an array with values for
all timesteps for variables like REACTZ_901 and hence you can offset
into it using
Thanks guys!
2016-09-09 16:44 GMT+02:00 Armin Wehrfritz :
> This is apparently a "very very old bug" [1] and pops up every now and
> then on this mailing-list. There was apparently a plan to fix this back
> in 2009 [2], but I'm doubtful that this was done.
>
> [1]
This is apparently a "very very old bug" [1] and pops up every now and
then on this mailing-list. There was apparently a plan to fix this back
in 2009 [2], but I'm doubtful that this was done.
[1] http://public.kitware.com/pipermail/paraview/2014-September/032263.html
[2]
We noticed this also, I believe the plan is to remove the flipping of dimension
ordering. However, I am unsure on when that will occur.
Andrew Burns
Software Engineer | Leidos
Phone: 410-306-0409
ARL DSRC
andrew.j.burns35@mail.mil
-Original Message-
From: ParaView
For whichever timestep ParaView fails, that timestep has incorrect
number of arrays. All datasets in a timeseries must have identical
arrays. It seems that's not the case with your data. You
On Fri, Sep 9, 2016 at 2:43 AM, Gokce Tuba Masur wrote:
>
> Hello,
>
> I have 12
Simon,
> To start off with, I am trying to work out if it's possible to display this
> type of network in ParaView as connected tubes, with radii scaled by the
> size of the vessels. As I say, these datasets are large, typically with
> around 300k segments. If this kind of visualisation is
Hi,
I'm investigating how I might use ParaView to visualise large 3D spatial
graphs (i.e. a spatial distribution of nodes connected by segments) that
represent blood vessel networks in tumours. I usually use Amira or
Imaris for this, but would much prefer to use an open source solution
like
Hello All
Sorry to bother you again... I seem to miss something wanting to fix color scale
ranges for objects with multiple attributes.
For example: I have a vtk-Plane with associated velocity and density values that
I can choose for coloring. When I imported the object, I set
13 matches
Mail list logo