View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0009852ParaViewFeaturepublic2009-11-06 08:532016-08-12 09:59
ReporterBerk Geveci 
Assigned ToT.J. Corona 
PrioritynormalSeverityfeatureReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target Version5.1Fixed in Version 
Summary0009852: Add a carpet plot view
DescriptionThis view should take a 2D dataset and render it as a carpet plot using a custom mapper to avoid the memory cost of converting it to polydata and warping it. It should also have decent x-y-z axis.
TagsNo tags attached.
ProjectSandia
Topic Name
Typeincorrect functionality
Attached Filespdf file icon flow_instability.pdf [^] (2,171,498 bytes) 2016-07-25 19:28

 Relationships

  Notes
(0034837)
Alan Scott (manager)
2015-07-27 20:39

 I have a user (Matt) asking for this.
(0036569)
Alan Scott (manager)
2016-07-25 19:24

 From Ben:


Thanks for taking a look at this ticket, to provide some context to the request, I've attached a (fairly complex) example of the kind of plots I had in mind. These are located in the second column, you can ignore the plots in the first column and the inset.

In these plots, the vertical axis is position (along a line) and the horizontal axis is time. The color is determined by the values of a variable along this line.

At present, this figure is generated by loading exodus output into Paraview, selecting points that (more or less) fall along the line, using "Plot Selection Over Time," using "Save Data" to output these as csv files, and then doing my own post-processing in matplotlib. It would be helpful to get the same results without all of the hoop jumping.

Some desirable features:

* Choice of an arbitrary vector (ala "Plot Over Line") which automatically interpolates from nearby values.
* Some control over the temporal/spatial discretization
* Export to a interchangeable format for additional post-processing
* Custom ranges for the various axes ala "Plot Over Line"

Additionally, the axes need not always be space versus time, though I'd argue it is a good default.

A distinct but related capability would be the ability to average/integrate over a particular dimension. Say I ran a 2D simulation in x and y, but only cared about behavior in y, it would be useful to integrate/average over all (or part) of x (or theta, or r, or phi, or ...).

Sorry if this is too much information. Let me know if you have any questions,
(0038084)
Kitware Robot (administrator)
2016-08-12 09:59

 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
2009-11-06 08:53 Berk Geveci New Issue
2011-06-16 13:10 Zack Galbreath Category Feature Request => Feature
2015-07-27 20:38 Alan Scott Assigned To => Alan Scott
2015-07-27 20:38 Alan Scott Status expired => backlog
2015-07-27 20:38 Alan Scott Resolution open => reopened
2015-07-27 20:39 Alan Scott Project => Sandia
2015-07-27 20:39 Alan Scott Type => incorrect functionality
2015-07-27 20:39 Alan Scott Note Added: 0034837
2015-07-27 20:39 Alan Scott Target Version => 4.5
2015-07-27 20:43 Alan Scott Assigned To Alan Scott =>
2015-09-11 16:44 Utkarsh Ayachit Target Version 4.5 => 5.1
2016-07-25 14:06 T.J. Corona Assigned To => T.J. Corona
2016-07-25 14:06 T.J. Corona Status backlog => active development
2016-07-25 19:24 Alan Scott Note Added: 0036569
2016-07-25 19:28 Alan Scott File Added: flow_instability.pdf
2016-08-12 09:59 Kitware Robot Note Added: 0038084
2016-08-12 09:59 Kitware Robot Status active development => closed
2016-08-12 09:59 Kitware Robot Resolution reopened => moved

Copyright © 2000 - 2018 MantisBT Team