[Paraview] Tensor variables in ExodusII database

Timothy Jesse Fuller timothy.fuller at utah.edu
Mon Dec 22 18:53:59 EST 2014


Thanks for the reply Sam.  I made a typo in my original question - I did have the off-diagonal components labeled as you suggested.  I tried swapping x and z in the last off-diagonal term to see if that would make a difference - to no avail.  Interestingly, ParaView does seem to interpret the variable as a tensor, as indicated in ParaView re-ordering the components from how they are written to the database.  e.g. ParaView lists them as _xx, _xy, _xz, _yy, _yz, _zz but they are written to the database as _xx, _yy, _zz, _xy, _yz, _xz (or _zx) - as shown in attached screen shots.

I seem to recall opening ExodusII files with tensors displayed in a “collapsed" fashion - with the magnitude being the default view, just as Displacement in the attached screen shots.  Any further advice to reproduce this behavior is much appreciated!

Cheers,


Tim Fuller, PhD
E: timothy.fuller at utah.edu<mailto:timothy.fuller at utah.edu>
[cid:72ADD404-B341-4AB1-A349-E0BFA769C97B at hsd1.ut.comcast.net.][cid:EB05174E-2A39-411E-8F16-2207AA1AC2A9 at hsd1.ut.comcast.net.]



On Dec 22, 2014, at 4:06 PM, Samuel Key <samuelkey at bresnan.net<mailto:samuelkey at bresnan.net>> wrote:

Tim,

Tribal knowledge leads me to suggest trying

var_xy, var_yz, var_zx

for the off-diagonal terms.

(I can't recall for sure but the last entry may be var_xz)

Sam

On 12/22/2014 3:26 PM, Timothy Jesse Fuller wrote:
When writing a symmetric tensor to an ExodusII database, the following link indicates that ParaView will interpret the variable as a symmetric tensor if it is written to the file as var_xx, var_yy, var_zz, var_xy, var_xz, var_yz, where var is the variable name

http://www.paraview.org/Bug/view.php?id=5979

However, when I write symmetric tensors to the database with the above convention, ParaView interprets them as 6 independent scalars.  Is there a more updated method of naming symmetric tensors in ExodusII database files so that ParaView will interpret them correctly?

Cheers,


-- Tim --


Tim Fuller, PhD
E: timothy.fuller at utah.edu<mailto:timothy.fuller at utah.edu>







_______________________________________________
Powered by www.kitware.com<http://www.kitware.com/>

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141222/a6b0facc/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-12-22 at 4.42.04 PM.png
Type: image/png
Size: 143174 bytes
Desc: Screen Shot 2014-12-22 at 4.42.04 PM.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141222/a6b0facc/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2014-12-22 at 4.37.41 PM.png
Type: image/png
Size: 147320 bytes
Desc: Screen Shot 2014-12-22 at 4.37.41 PM.png
URL: <http://public.kitware.com/pipermail/paraview/attachments/20141222/a6b0facc/attachment-0003.png>


More information about the ParaView mailing list