# General

## I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

### There are two ways to get more votes:

• When an admin closes an idea you've voted on, you'll get your votes back from that idea.
• You can remove your votes from an open idea you support.
• To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

1. ## Hello, I tried to see results from an Abaqus output file (.odb) , but I found It impossible

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

It seems odd that despite Sandia's involvement in both LAMMPS and ParaView, ParaView can't read in native LAMMPS output files from simulations.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
3. ## buid a filter able to selectively rename/delete arrays from a dataset

Sometime after extensive calculations you end up with several point/cell data arrays that are useless and just take memory like IDs, Region ID etc It would be nice to be able to rename/delete these from the current dataset and spare memory

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
4. ## provide some kind of global variable definition

Often I'd like to have a "global variable", so that I can change a value at only one position, which is referenced by several filters, including Python programmable filters/sources.
The smartest thing would be, to have a slider widget, with which I could interactively change the value of this variable and so could examine different stages/points of view/slices... (depends on how I used the variable) of the dataset.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
5. ## Traveling with Fluid particle

Creating animations of user traveling with a fluid particle within a fluid domain, so that you can visualize what the journey looks like inside the domain.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
6. ## Writing to Paraview from an external program

Paraview operates/implements a client-server paradigm. This suggests that it may be possible for an external (e.g. C++ application) to communicate with a running instance of Paraview, by sending it commands (e.g. open legacy VTK file) via the port attached to the server. Such a feature would be ideal for:

- debugging programs that output VTK data.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)

We are working on this feature as well as the ability to linking the ParaView engine with the simulation (aka co-processing or in-situ processing)

7. ## green dot marking the current time for parametric plots

In a PlotSelectionOverTime filter, the resulting 2D plot can be shown as a function y = y( timestep ). This is the default, and by default a very handy vertical green line marks the current timestep.

The plot can also show parametric graphs, where (x,y) is plotted, and x = x( timestep) as well as y = y( timestep ).

In this latter case, I would like to see a green dot marking the (x,y) of the current timestep.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
8. ## 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 filter

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
9. ## Integrate Julia

I think that Julia is the next best scientific programming language. CFD, FEM, Magnetic, and other solvers, as well as filters could be written right inside Paraview, and executed with decent performance. The same code can be developed as stand-alone functions.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
10. ## delete parent with children in pipeline

Presently, a parent in the pipeline can only be deleted when all children have been deleted before. Suggestion to allow deletion of a parent with implicit deletion of all of its children (instead of throwing an error that parent cannot be deleted).

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
11. ## Add real vector graphics

With paraview 5 the export to vector graphic formats most often results in a rasterized image (http://public.kitware.com/pipermail/paraview/2016-February/036314.html). This is huge drawback of the new version. Please bring the old true svg, eps, pdf export back!
(Old uservoice entry for this: https://paraview.uservoice.com/forums/11350-general/suggestions/313565-add-vector-graphics-output-i-e-postscript)

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
12. ## Add a tutorial which describes how to load data using python script without using a compiled data loader.

Add a tutorial which describes how to load data into Paraview using python script but without using a compiled data reader plug-in (or anything else). It can save a lot of time for people which are not so familiar with compilation process (don't have the knowledge to compile their own data reader).

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
13. ## Temporal Derivative Filter

I'd like to have a filter that calculates the difference of my data (point data, cell data, etc.) compared to the previous time step, i.e. the time derivative of my data.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
14. ## Modernize VMRL and OBJ readers

VRML reader should support aliased materials, OBJ reader should support MTL files (suggested by David E DeMarle)

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
15. ## Export Dynamic Scenes

Add capabilities to the VRML, WebGL, X3D etc. writers to enable the export of animated scenes.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
16. ## bug

this data file crashes paraview 3.14.1 on mac osx 10.6.8.
i know it's a bad data file; there is no space separating the X and Y components of the POINT data.
i know this isn't the bug tracker.

# vtk DataFile Version 3.0
Surprise, surprise. Bad input data crashes ParaView.
ASCII
DATASET UNSTRUCTURED_GRID
POINTS 1 double
0.622120545112035E+000-0.418009927112657E+000 0.000000000000000E+000
CELLS 1 2
1
1
CELL_TYPES 1
1
CELL_DATA 1
VECTORS test_vec double
1.000000000000000E+000 2.000000000000000E+000 3.000000000000000E+000

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
17. ## proper orthogonal decomposition analysis filter

I think it is very easy for the developers to implement a proper orthogonal decomposition for unsteady flow with equal spaced timesteps using Snapshot POD algorithm described in chapter 3.2 of http://web.mit.edu/kwillcox/Public/Web/BTTanMS.pdf

The algorithm is:
0. get timestepvalues of interest as t_i, i=1..N
1. load field P of two timesteps such as as P_i=P(t_i),P_j=P(t_j)
2. calculate the correlation R_ij = inner_product(P_i,P_j)/N, the definition of inner product could be integration of P_i*P_j over the volume.
3. get the eigen value lambda_i and corresponding vector eV_ii of matrix {R_ij}
4. construct the i-th POD basis psi_i = sum(dot(eV_ij,P_j),j=1..N), usually, only the first…

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
18. ## Include Sets for OpenFOAM cases

paraFoam (the OpenFOAM extension to Paraview) has a function to 'Include Sets/Zones' to show mesh sets from snappyHexMesh. Paraview is superb as a standalone tool. However, it lacks this one function.

Currently when using Paraview without the paraFoam module, for example on Windows, I cannot view mesh sets. It would be a greatly appreciated addition.

Thanks!

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
19. ## Add multi-block support to the "Temporal particles to pathlines" filter

When using a data-set with multiple spatial blocks, where the temporal information is present in the top-level multi-block wrapper node,
the pathlines filter does not find any timestepping information.

(cf. related discussion on the mailing list: http://www.paraview.org/pipermail/paraview/2010-October/019042.html)

Since we produce our data massively in parallel, we can not write a single spatial block efficiently and must rely on xdmf's multi-block capability. Without an efficient trajectory-trace filter, however, particle plotting using paraview is obviously mostly pointless.

Vote
(thinking…)
Signed in as (Sign out)
You have left! (?) (thinking…)
20. ## Enable vector export of axis labels specified in MathText form in line chart views

Currently (as of version 4.1), when exporting line chart views in vector form, the mathtext axis labels get output in plain form such as $\gamma$ instead of the Greek gamma symbol. Mathtext apperaing elsewhere, such as legends, gets output correctly. Only the axes labels do not get output correctly. I have tested it with both "renedr text as paths" checked and unchecked and the error was not affected by it.