Hi, Ryan
You can specify the size of the images by assigning the render view
properties: view size.
-
renderView1 = GetActiveViewOrCreate('RenderView')
renderView1.ViewSize = [600, 557]
renderView1.ResetCamera()
-
Thanks,
Yoshimi
2016-09-27 23:10 GMT+09:00 Jamison,
As far as VTK/ParaView are concerned, lines and triangles are just different
types of cells. The filters treat each cell uniformly. That is, the gradient
filter is treating triangles and lines the same and mixing the results together
in the same way as if the data contained triangles and
Hi, everyone,
I am new to this list. I like to ask few questions about how to setup a
3D system. Please give me some suggestions if you have experiences.
My goal is to let people able to watch the VTK files through Paraview
with a 3D glasses on the monitor or TV. So here are the questions:
Matthias,
In the off-chance that the various mesh components (node
sets, line-sets, surface facet sets, ...) have been written to
the simulation results output as distinct displayable graphics
objects, you might be able to use the PV Extract Block filter to
Hi Ken,
thank you for pointing this out! I was not aware that boundary lines are also
inifinitely flat cells. This seems true for all boundaries, also the internal
boundaries between the two faces.
The question for me is now: Is this normal, or does that mean that the whole
FEM simulation is
Yoshimi,
Thanks for the script! This does exactly what I was wanting to do.
One further question, where in the script can I define the size of the images
to save?
Best, Ryan
> On Sep 26, 2016, at 10:40 PM, kenichiro yoshimi
> wrote:
>
> Hi, Ryan
>
> You try the
Matthias,
If values are being pulled from 7900 units down to 5300 units, there must be
some neighbor with lower values. Why that is happening for you I cannot say
without looking at your data. Perhaps on the boundary there are some malformed
or 2D cells with invalid gradients.
-Ken
From:
Hi Armin,
thank you - thats what i searched for ...
Stefan
Hi Stefan,
IIRC there is a .vtu file containing polyhderal cells in the VTK DATA
repository.
Otherwise, I attached a .xmf and a .vtu file containing each containing
identical data, i.e. 2 hexahedral and 2 polyhderal cell.
Hi Ken,
what I don’t understand is that the cell gradients are correct, but their
average at the border is not. (Example: All cell gradients adjacent to one node
at the border have approx. 7900 units in y direction, the node has approx. 5300)
So it seems I cannot determine the gradient in the
Hi Stefan,
IIRC there is a .vtu file containing polyhderal cells in the VTK DATA
repository.
Otherwise, I attached a .xmf and a .vtu file containing each containing
identical data, i.e. 2 hexahedral and 2 polyhderal cell.
Please note that the white-space in these files has no meaning, and that
Yes. Off by a month, my mistake. The intent is to let the survey run for
a week.
--
Chuck Atkins
Staff R Engineer, Scientific Computing
Kitware, Inc.
On Mon, Sep 26, 2016 at 3:03 PM, Ben Boeckel
wrote:
> On Mon, Sep 26, 2016 at 14:01:38 -0400, Chuck Atkins
You could run the results through the point to cell filter, but that would give
you the same answer as the gradient of unstructured dataset filter with the
faster approximation option on.
-Ken
From: "Zenker, Dr. Matthias"
Date: Tuesday, September 27, 2016 at 8:28
Hi Kenneth,
thank you for the quick answer!
So it seems not that trivial to calculate an electrical field between a rod and
a plane given the potential…
The compute derivatives filter does not give me the problem at the boundary
indeed. Instead it gives a value per cell, not per node, which
Matthias,
The gradient is estimated with finite differences. Thus, it is not wholly
unexpected that there could be differences at the boundaries. However, the
algorithm does not assume zero for adjacent cells at the boundaries.
The way the unstructured gradient filter works is that it computes
Hi,
when I use the gradient filter (unstructured dataset), I observe edge effects
which are IMO unphysical. For the nodes on the outer boundary of my domain, the
gradient magnitude is smaller than I would expect. The behavior is like the
filter tries to use the adjacent nodes to calculate the
Works perfectly, thank you!
Von: Andy Bauer [mailto:andy.ba...@kitware.com]
Gesendet: Montag, 26. September 2016 19:09
An: Zenker, Dr. Matthias
Cc: paraview@paraview.org
Betreff: Re: [Paraview] WG: save filter result
Use the Pass Arrays filter to get avoid passing unwanted arrays through the
16 matches
Mail list logo