260 results found
-
Add filters to edit/move selected points or create labels at cell/point selections.
Sometimes it would be useful if I could move selected points by a vector.
Also, it would great if I could set label values at cells and points, which could be used for boundary conditions in e.g. FEM codes. The option could be to create an array with default values and set a given value at the selected nodes.4 votes -
automatic rescaling option for the colormap
It will be great if paraview has an option to enable automatic rescaling for the color map. This is useful to compare the results easily with other software that enables the colormap to be rescaled automatically such as matlap.
3 votes -
Improve Fluent compatibility
native support and of zonal display would save alot of time
3 votes -
Allow Image Resizing in Pipelines
Currently, if an Image source has a certain Extent, Paraview will pass that as UPDATE_EXTENT to all subsequent filters in the pipeline, even if a filter changes the whole extent. This prohibits for example implementing vtkImageConstantPad as a useful Paraview filter. For further info see http://markmail.org/message/sfnw7sgojytzw6y2 .
3 votes -
legend layout improvements
it would be nice having
- line-break / feed in legend headers, e.g. for displaying the unit in a second line
- ability to remove the display of the highest and lowest values (which are always there and they are not aligned with the other values)
- Ability to choose the labels, much like the "new value" / "new range" buttons of the slice filterinstead having an option
13 votes -
Remove legend ticks !!!
I think the visibility of the ticks on the legend should be optional...
1 vote -
Create an XML file syntax checker
A script to check simple things like if the class the plugin is using actually exists and if the functions that are supposed to be called actually exist. It would be nice to know these things before errors occur at runtime :)
2 votes -
Add carpet plot view
This 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.
2 votes -
Easier to use Plane Source
The plane source seems very awkward to use - specifying three corners of the plane. A more natural way to specify a plane is by the origin and normal vector. A radius would also be needed to specify how large the patch of the plane should be. Maybe a "Square Sphere Source" source could be added on top of the existing Sphere Source so people can use the existing one for "difficult" planes (non-rectangular) and the new one for "easy" planes (square).
8 votes -
Persistent selection tool (and type) with auto use & execute
When probing a data set it would be nice to have an option where the selection tool stays active, and the pipeline knows to automatically use new selections after they're created and execute the pipeline.
Unless you're just using cell and point labels, a typical current process is to select, extract and add some further pipeline (e.g. statistics, particle pathlines...). The main problem comes when you want to probe a different piece of the data: you need to go back and choose the selection tool again and make a new selection (and maybe go to the Selection Browser and change…
2 votes -
Add an auto-redraw option.
Currently, ParaView automatically re-renders the screen after any filters have been applied, which can cause large delays if datasets are large and representations are set to anything but outline. It would be nice to have an auto-redraw tickbox option with a redraw(render) button on the UI, so that the user can apply any filters and render whenever they want manually by button clicks. A similar effect can be achieved using representations, but the drop-down box can prove fiddly if it has to be changed frequently.
5 votes -
automatically adjust point/line sizes for screenshots with different resolution
If you have points or lines in the scene and you take a screen shot at a higher resolution than the current window (say 5000x5000), many of the objects stay the same size (spheres, planes, triangulated meshes) but many objects get much smaller (points, lines). Surely this is because the points and lines are specified in arbitrary units (Point Size = 3, Line Width=2, for example). An example is here:
http://rpi.edu/~doriad/Paraview_List/linesize.jpgNotice the lines in the screenshot are much thinner.
It would be nice to have theses sizes automatically adjusted to the relative difference between the screenshot size and the…
4 votes -
Add a combo-box in the DisplayPanel for Composite/MIP/MinIP mode of the Volume mapper
I changed the XML (rendering.xml) by adding a SetBlendMode property, with 3 values:
- Composite
- Maximum intensity
- Minimum intensity
default_value allows to choose one of the 3, but have to recompile paraview. The blend mode cannot be changed from the PV interface.3 votes -
When using several windows, add ability to resize them all to the same dimensions
Sometimes I use several windows to visualize diferent quantities in a flow. I would wish to have a button or check box so the windows would share the same dimensions. It is like the "Link camera" but for the windows dimensions.
3 votes -
support reading and writing point data in a simple binary XYZ or XYZ-Scalar format.
Paraview already supports many different file formats, but from what I can tell, these all relate to other 3rd party programs. It would be very useful if paraview could read and write to files with a simple binary format, such as a contiguous block of doubles or floats <x1><y1><z1><scalar1><x2><y2>...
This would make integration in to custom apps much easier.1 vote -
When loading saved state remember settings
When loading saved state remember if (for instance, when having slice) if "view plane" is selected or not.
6 votes -
improve xml writers
let the user chose arrays to write just as it is possible to chose the arrays to be read.
4 votes -
Add a tick level property to the Cube Axis Annotation
It would be nice to be able to define the spacing between ticks, instead of only have the default values.
4 votes -
integrate variables bug fix
a) have a field with constant values all over the field
b) define a slice (rectangle)
c) integrate this variable
d) divide the values by the area of the slice
e) Expectation: get the average value which is the constant BUT paraview gave me a value of 25 % wrong6 votes -
2 votes