<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Doina--</p>
<p><br>
</p>
<p>In what follows, I will skip talking about a 3-nod quadratic line
as a way to display a cured beam or a deformed beam. (I live in a
world of large deformation simulations and I like to display that
type of behavior.)</p>
<p><br>
</p>
<p>The concept of FIELD (aka GLOBAL) simulation results, for
example, results that come from or related to overall behavior
like total Kinetic Energy (KE), are well supported by the
Exodus-II format and are absent from the EnSight format and the
VTK format for simulation results. I will confine my comments to
what I have to offer to just POINT data and CELL data. <br>
</p>
<p><br>
</p>
<p>It is convenient to divide simulation results into three
categories for virtually all of the data formats that PV can read.</p>
<p>(1) GEOMETRY data<br>
</p>
<p>(2) POINT data<br>
</p>
<p>(3) CELL data</p>
<p><br>
</p>
<p>The following is the VTK-XML ASCII format. (See the attached file
'resultsvtk.f')<br>
</p>
<p><br>
</p>
<p>(1) GEOMETRY. ParaView is quite happy with just GEOMETRY data.(It
is a nice way to start when one is trying to write a datum set for
ParaView. ParaView will display an object with only the geometry
data.)</p>
<p><br>
</p>
<p>(1a) Write the entire Point inventory from 1 to n where n =
number of nodal points in terms of coordinate 3-tuples
[(x1,y1,z1,), ...,(xn,yn,zn)]</p>
<p><br>
</p>
<p>(1b) Write the entire Cell inventory of connectivity n-tuples (as
array offsets!)</p>
<p>(1c) Write the 'starting location' for the n-tuples in (1b)</p>
<p>(1d) Write the VTK cell-type values for the n-tuples in (1b)</p>
<p><br>
</p>
<p>ParaView now has everything it needs to display your geometry.</p>
<p><br>
</p>
<p>(2) Write POINT data information.</p>
<p>(2a) In the case of 'mode shapes,' write the mode's displacement
3-tuples (aka Vectors, name="Mode1") <br>
</p>
<p>[(UxM1,UyM1,UzM1),...,(UxMn,UyMn,UzMn)]</p>
<p>(2b) Repeat with name="Mode2", and so fourth (aka<i> und so
weiter</i>)</p>
<p><br>
</p>
<p>ParaView now has the enough information to animate the mode
shapes. Instructions are here</p>
<p>(
<a class="moz-txt-link-freetext" href="https://public.kitware.com/pipermail/paraview/2017-October/041077.html">https://public.kitware.com/pipermail/paraview/2017-October/041077.html</a>
) for producing animations of the mode shapes.</p>
<p><br>
</p>
<p>Hope this helps.</p>
<p><br>
</p>
<p>--Sam<br>
</p>
<p> <br>
</p>
<div class="moz-cite-prefix">On 11/21/2017 7:15 AM, Doina Gumeniuc
(224252 MAHS) wrote:<br>
</div>
<blockquote type="cite"
cite="mid:AM0PR0602MB34590ACC3D8B3B53F6ADC15EA4230@AM0PR0602MB3459.eurprd06.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<p>Hi Samuel,</p>
<p><br>
</p>
<p>Thank you for your reply.</p>
<p>I have different frequencies, 50 in total. If I use FIELD
POINT DATA and then for arrayname 1 and so on, I use the
Freq1, Freq2... then for 6Dofs, I use vectors in x,y,z for
translation and Phi-x,Phi-y, Phi-z for rotation.... would it
make sense in paraview? I can hopefully then warp by vectors
using the data for each frequency.</p>
<p><br>
</p>
<p>Thank you! I hope I was clear.</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
ParaView <a class="moz-txt-link-rfc2396E" href="mailto:paraview-bounces@paraview.org"><paraview-bounces@paraview.org></a> on behalf of
Samuel Key <a class="moz-txt-link-rfc2396E" href="mailto:samuelkey@bresnan.net"><samuelkey@bresnan.net></a><br>
<b>Sent:</b> November 18, 2017 7:00:51 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
<b>Subject:</b> Re: [Paraview] Degrees of freedom</font>
<div> </div>
</div>
<div style="background-color:#FFFFFF">
<p>Doina--</p>
<p><br>
</p>
<p>At the risk of underestimating ParaView's functionalities, I
can tell you what will work. For displaying geometry, PV only
needs Point (aka nodal point) x,y,z-coordinates, a Cell (aka
Finite Element, ...) type and for each Cell an n-tuple of
Point "array locations", for example,
EnSight-format::{1,2,4,3,7,8,} or VTK-format::{0,1,3,2,6,7}.
<br>
</p>
<p><br>
</p>
<p>The VTK format uses C-language 'array offsets' for Cell
connectivity n-tuples. The EnSight format uses
FORTRAN-language array locations for Finite Element
connectivity n-tuples. It is just the way it is.</p>
<p><br>
</p>
<p>Variables are either located at Points or in Cells
(conceptually Cell centers). The arrays supplied for variables
must span all of the Points or all of the Cells. (I do not
know how to use or about the acceptability of "partially"
specified variable datum sets.) For Points with 6-DOFs versus
3-DOFs, if you want to see the three rotational DOFs, use
POINT DATA arrays and fill in the Phi-x, Phi-y, Phi-z values
using zeros for at those Points without a rotation.</p>
<p><br>
</p>
<p>If you want to visually display a 2-node, 6-DOF beam's
geometry (a curved beam or a deformed beam) , one solution is
too use a VTK Cell type 'VTK_QUADRATIC_EDGE = 21' for the
beam. This will require you to add-on-the-fly to the
simulation results a beam center-Point with x,y,z-coordinates
and displacements for the beam's center Point using the beam's
interpolation functions. (PV has a Warp Filter that will let
you then scale up the deflections for visualization purposes.)</p>
<p><br>
</p>
<p>Should you have access to source code for the simulations, I
can supply FORTRAN language routines that write VTK
ASCII-formatted simulation results. (My personal preference is
the EnSight format.)<br>
</p>
<p><br>
</p>
<p>--Sam<br>
</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="x_moz-cite-prefix">On 11/18/2017 6:12 AM, Doina
Gumeniuc (224252 MAHS) wrote:<br>
</div>
<blockquote type="cite">
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div id="x_divtagdefaultwrapper" dir="ltr"
style="font-size:12pt; color:#000000;
font-family:Calibri,Helvetica,sans-serif">
<p>Hi all!</p>
<p>I am still learning the use of paraview and I have got to
such a question: How to show in a vtk input file the
degrees of freedom of elements? Some of the beams have 6
degrees of freedom, some of the other elements...less or
nothing at all. IS there any possibility?</p>
<p>Thank you a lot in advance!</p>
</div>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
Powered by <a class="x_moz-txt-link-abbreviated" href="http://www.kitware.com" moz-do-not-send="true">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="x_moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html" moz-do-not-send="true">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="x_moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView" moz-do-not-send="true">http://paraview.org/Wiki/ParaView</a>
Search the list archives at: <a class="x_moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView" moz-do-not-send="true">http://markmail.org/search/?q=ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="x_moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview" moz-do-not-send="true">http://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<br>
</body>
</html>