View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012008ParaViewBugpublic2011-03-24 12:352016-08-12 09:58
ReporterAlan Scott 
Assigned ToRobert Maynard 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target Versiongit-masterFixed in Version 
Summary0012008: CTH velocities are calculated incorrectly
DescriptionWe've found a problem with how paraview reads in velocities from CTH spyplot files which appears to have been a problem since at least 3.6.2. The problem is related to how CTH outputs velocities in it's spyplot files.

First of all, note that velocities are treated differently in CTH compared to all the other variables. All non-velocity values are cell-centered quantities, but velocities are face-centered quantities (x velocities on faces with an x normal, y velocities on faces with y normal, and z velocities on faces with a z normal). In order to get an appropriate cell-centered value for velocity, you have to average the velocities for opposing faces.

This is where we run into problems. Spyplot does not do this averaging before it outputs its results to an spcth file. When it outputs velocities for a cell, it is actually outputting the velocities on the bottom faces, i.e. on the x, y, and z faces that have a smaller quantity centroid than the other x, y, or z face on the cell. In order to get the cell-centered velocities, you need to take the velocities output for the cell and average them with the appropriate cells adjacent in the positive x, y, and z directions. This is elaborated in 2-D in the attached PDF file; 3-D is a simple extension.

Although this is a quirk of the CTH data, it is very much needed for this to be incorporated into paraview so that the proper velocities are output. It is an issue for all CTH visualization, but it is most evident using the material interface filter, which outputs improper averaged velocities for fragments, thus making velocity vector and momentum computations incorrect.

All of this was determined through direct debugging of routines within paraview, and has been confirmed with the CTH developers. I have a very simple, small test case which demonstrates all these issues and is unclassified. Please let me know if you would like it.

Please let me know if you have any questions about any of this.

Note from Alan - I have the dataset example. It is called CTH-velocities.

TagsNo tags attached.
ProjectSandia
Topic Name
Typeincorrect functionality
Attached Filespdf file icon CTH_velocities.pdf [^] (113,182 bytes) 2011-03-24 12:35

 Relationships

  Notes
(0027227)
Utkarsh Ayachit (administrator)
2011-08-04 15:27

 Pushing to 4.0 after discussion with Alan.
(0037944)
Kitware Robot (administrator)
2016-08-12 09:58

 Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.

 Issue History
Date Modified Username Field Change
2011-03-24 12:35 Alan Scott New Issue
2011-03-24 12:35 Alan Scott File Added: CTH_velocities.pdf
2011-03-29 14:59 Utkarsh Ayachit Assigned To => Robert Maynard
2011-03-29 14:59 Utkarsh Ayachit Status backlog => tabled
2011-03-31 11:24 Utkarsh Ayachit Target Version 3.10.1 => 3.12
2011-06-24 14:06 Alan Scott Status backlog => todo
2011-06-27 08:32 Utkarsh Ayachit Project => Sandia
2011-07-25 11:56 Utkarsh Ayachit Type => incorrect functionality
2011-07-25 11:56 Utkarsh Ayachit Target Version => 3.12
2011-08-04 15:27 Utkarsh Ayachit Note Added: 0027227
2011-08-04 15:27 Utkarsh Ayachit Target Version 3.12 => 4.0
2012-05-31 10:23 Utkarsh Ayachit Status todo => backlog
2012-10-18 13:49 Utkarsh Ayachit Target Version 4.0 => git-master
2016-08-12 09:58 Kitware Robot Note Added: 0037944
2016-08-12 09:58 Kitware Robot Status backlog => closed
2016-08-12 09:58 Kitware Robot Resolution open => moved

Copyright © 2000 - 2018 MantisBT Team