260 results found
-
Create a reader for the Fieldview format (.fvuns).
The .fvuns format is commonly used for creating animations in FLUENT. The reason is that you can export selected planes/surfaces (even with dynamic mesh), meaning that you will have lower file than when exporting the entire data set. For long transient animations, this format is therefor highly useful.
1 vote -
Extract the index from selected points, in the order they are selected and extract plane parameters from slice
Hi, I would like to extract the index of the points selected in the order I selected them. But when I choose extract selection and save the csv file, I get them ordered from small to big. Also I would like to save the point coordiantes and his normal when I choose slice. I see them in the box in the left, but there is no option to save them in a csv file. Thanks
6 votes -
Load Materials on surfaces
Now that OSPRay rendering seems to turn out really well, it would be really a plus if it could be added also the option to active material rendering (like metal, glass, plastic, etc.) on surfaces, instead of simple solid colors.
3 votesThis is under development for 5.5.
-
Conical Slices
I would like to do a slice but using a cone. Is there a way to extract information using different geometries?
4 votes -
The solution for easy file import from SolidWorks to ParaView.
I'd like to suggest some solution for easy import files from SolidWorks. I tried to do it, but there is only wrl file theoretically compatible. In practice, my SW 2014 and ParaView 5.2 dosn't interact. There is an ERROR: In C:\bbd\df0abce0\source-paraview\VTK\Common\ExecutionModel\vtkDemandDrivenPipeline.cxx, line 710
vtkCompositeDataPipeline (00000204B4E93B60): Input port 0 of algorithm vtkAppendPolyData(00000204B5040810) has 0 connections but is not optional.2 votes -
cell volume
It would be great to have a filter that directly computes cells volume and store it as a variable
8 votes -
Custom Launcher
We can add Menu items or Macros with Custom Icons.
3 votes -
Setting zoom sensitivity
Scale the speed at which zoom occurs based on mouse input. In other words, add a user preference for scaling how rapidly or slowly the scene zooms in or out based on moving the scroll wheel. My mouse seems extremely sensitive.
10 votes -
Rendering sell element thickness and beam element cross section for code aster
Code Aster beam and shell element but In paraview we can't see the thickness and cross section of shell and beam element
4 votes -
3 votes
-
Add Drag and Drop and support 'open with' for pvsm files
It should be possible to launch the program with a pvsm file without being prompted to select an importer for this file format (which is not even listed).
5 votes -
Add a query information filter
This filter should accept a query with :
- an operator : min / max / mean .... etc.
- a celldata or pointdata name
- an optional selection
- a format descriptorThe filter should then add a 3d text with the result of the query and an optional arrow to point out the location of the query (if the query is min/max).
It should be possible to place automaticaslly the 3d text object where it 's not disturbing.
It should be possible to define formats with multiple fields.
For example :
- query : max Temp
- format…4 votes -
Global Z scale option
Allow a global z scale like Google Earth. Currently I have to scale each of dozens of input data individually. This is an important feature for terrain visualizations.
2 votes -
default .med plugin
open source FE solver of code aster doesn't have post processing tool with it and default output format is (.med) . it's available in paravize but that require separate coupling so it's better to have .med plugin with para view
6 votes -
Catch invalid printf-formatting strings instead of having the application crash
Specifically, in the "Edit Color Legend Parameters" dialog, entering "%4.3s" as the "Range Label Format" and pressing "Apply" makes the application crash hard.
1 vote -
Load field data from DiscreteData_t type node in CGNS file
The CGNS standard suggests "DiscreteDatat nodes are intended for the storage of fields of data not usually identified as part of the flow solution, such as fluxes or equation residuals." However now the DiscreteDatat nodes seems ignored by Paraview (version 5.1.2). One has to put all field data in FlowSolution_t node in order to have the data been loaded by Paraview which breaks the CGNS convention.
3 votes -
OS X Packaging strategy to support installation and removal of multiple ParaView Options
Create a way that would allow an MDM solution like the JAMF Casper Suite to install update and manage multiple version of ParaView provide backward compatibility of ParaView.
One of the solutions for ParaView would be to provide backward compatibility in newer version to older version. This is how most of the software vendors we deal with handle the multiple versions installed at the same time issue. Others create entirely new software like Microsoft Office for Mac 2011 and Office for Mac 2016 that are installed via pkgs and operate in parallel.
1 vote -
improve windows 10 compatibility
Windows 10 seems to have some incompatibilities with Paraview (v. 5.1.0), and sometimes crashes when opening .xdmf files. Also, when representing volumes, they do not look as good as in Ubuntu 14.04.
7 votes -
Develop a translator to convert CALCULIX generater .frd files in to paraview readable files
Develop a translator to convert CALCULIX generater .frd files in to paraview readable files
41 votes -
Import block names during multi-block XDMF import
Currently grid names are not imported during XDMF import. This would be very useful in case of multi-block data, where currently generic names are assigned. See also this post:
https://cmake.org/pipermail/paraview/2009-July/012858.html1 vote
