ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-09-02T14:56:47-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19291Custom viewpoint names show up in toolbar2019-09-02T14:56:47-04:00Riley BradyCustom viewpoint names show up in toolbarI like the ability to create a custom viewpoint, but one can only give them names in the configure viewpoints menu. The main toolbar just shows 1, 2, 3, and so on. It would be great for those numbers to be replaced with the viewpoint nam...I like the ability to create a custom viewpoint, but one can only give them names in the configure viewpoints menu. The main toolbar just shows 1, 2, 3, and so on. It would be great for those numbers to be replaced with the viewpoint name, e.g. Arctic Ocean.https://gitlab.kitware.com/paraview/paraview/-/issues/19289Fix cell data to point data bug2019-10-07T08:12:23-04:00Andrew BauerFix cell data to point data bugIf using the `Piece Invariant` option in parallel with structured data the pipeline won't properly request the correct number of ghost levels.If using the `Piece Invariant` option in parallel with structured data the pipeline won't properly request the correct number of ghost levels.https://gitlab.kitware.com/paraview/paraview/-/issues/19288Splash image of custom app not found due to naming inconsistency2019-09-05T18:44:17-04:00Cornelis BockemühlSplash image of custom app not found due to naming inconsistencyA little bug in the ParaView build setup files that is related to handling a splash screen image: in ParaViewClient.cmake(207) [referring to v5.7-RC2] I had to change this line
`":/${_paraview_client_NAME}/${_paraview_client_splash_imag...A little bug in the ParaView build setup files that is related to handling a splash screen image: in ParaViewClient.cmake(207) [referring to v5.7-RC2] I had to change this line
`":/${_paraview_client_NAME}/${_paraview_client_splash_image_name}")`
into this:
`":/${_paraview_client_NAME}/${_paraview_client_splash_base_name}")`
Without this change, the pqAPPLICATIONInitializer::Initialize() function would look for a resource named "APPLICATION_splash.img" while in reality the name of the resource would be "APPLICATION_splash" - without the “.img” extension. (Of course the fix could have been done in a way that the naming of the splash bitmap is adapted to have the extension - only it has to match!)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19286Reading Tecplot FEPOLYHEDRON/FEPOLYGON data2021-04-21T13:45:16-04:00Serge ToxopeusReading Tecplot FEPOLYHEDRON/FEPOLYGON dataThe current Tecplot reader does not support loading FEPolyhedron or FEPolygon data, and in case of FEPolygon data comes up with obscure messages about unknown record types such as e.g.
```
ERROR: In C:\bbd\ecd3383f\build\superbuild\par...The current Tecplot reader does not support loading FEPolyhedron or FEPolygon data, and in case of FEPolygon data comes up with obscure messages about unknown record types such as e.g.
```
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\VTK\IO\Geometry\vtkTecplotReader.cxx, line 1925
vtkTecplotReader (000000000A5E5280): filename.dat: The record type CELLCENTERED found in the file is unknown.
```
The CELLCENTERED record is not the cause of the error, it is the fact that before the ZONETYPE=FEPolygon statement is completely ignored.
Would it be possible to implement handling of FEPolyhedron or FEPolygon data coming from Tecplot? Example polyhedron and polygon files are attached:
[tecplot_fepolygon.dat](/uploads/4757ba214bca09765e6cbbc04b9770c8/tecplot_fepolygon.dat)
[tecplot_fepolyhedron.dat](/uploads/63a4b28343d11792b9346a388b57a287/tecplot_fepolyhedron.dat)https://gitlab.kitware.com/paraview/paraview/-/issues/19283Plugin Autoload not working?2019-11-01T12:36:46-04:00Niklas RoeberPlugin Autoload not working?It seems that when ParaView (master) writes it ini file (.config/ParaView/ParaView5.7.0.ini), the autoload settings, either manually specified in the menu under Tools->ManagePlugins, or by using the .plugins file in ../lib64/.., is disre...It seems that when ParaView (master) writes it ini file (.config/ParaView/ParaView5.7.0.ini), the autoload settings, either manually specified in the menu under Tools->ManagePlugins, or by using the .plugins file in ../lib64/.., is disregarded, and automatically set to 0, so that next time ParaView starts up, no plugin is automatically loaded. I also manually edited the ini file with the same effect. This should be unrelated to #19276.
Steps to reproduce:
- Start ParaView
- Set one plugin of your choice to autoload
- Close ParaView
- Start ParaView (plugin autoload works, but leave everything as is and close ParaView)
- Start ParaView again -> autoload is gone, plugin is not loaded, less .config/ParaView/ParaView5.7.0.ini shows 0 for all autoloads.
The autoload specifications in ../lib64/../.plugins are also ignored.
Cheers,
Niklas5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19280TBB target not found when compiling an external plugin for ParaView2019-09-03T05:27:41-04:00Charles GueunetTBB target not found when compiling an external plugin for ParaViewSimilarly to the issue #19232, but for TBB.
We are building a collection of filters in a Paraview plugin and have encountered an error when ParaView is compiled with the option: `VTK_SMP_IMPLEMENTATION_TYPE=TBB`. During the generate pha...Similarly to the issue #19232, but for TBB.
We are building a collection of filters in a Paraview plugin and have encountered an error when ParaView is compiled with the option: `VTK_SMP_IMPLEMENTATION_TYPE=TBB`. During the generate phase of our project we have the following error:
```
CMake Error at /home/charles/Software/install/ParaView/lib64/cmake/paraview-5.7/ParaViewPlugin.cmake:1260 (add_library):
Target "TopologyToolKit" links to target "TBB::tbb" but the target was not
found. Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
Call Stack (most recent call first):
paraview/singlePlugin/CMakeLists.txt:1 (paraview_add_plugin)
CMake Error at /home/charles/Software/install/ParaView/lib64/cmake/paraview-5.7/vtkModuleWrapClientServer.cmake:179 (add_library):
Target "ttkUncertainDataEstimatorCS" links to target "TBB::tbb" but the
target was not found. Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
Call Stack (most recent call first):
/home/charles/Software/install/ParaView/lib64/cmake/paraview-5.7/vtkModuleWrapClientServer.cmake:304 (_vtk_module_wrap_client_server_library)
/home/charles/Software/install/ParaView/lib64/cmake/paraview-5.7/ParaViewPlugin.cmake:979 (vtk_module_wrap_client_server)
paraview/singlePlugin/CMakeLists.txt:1 (paraview_add_plugin)
```
Once again, I think this is more a VTK issue but I post it here since I need to have it fixed into ParaView. Tell me if this is not a good practice and I will move it to the VTK gitlab.
@ben.boeckel can you help me with this one ?
Charleshttps://gitlab.kitware.com/paraview/paraview/-/issues/19279Add ability to move camera (in 3d space) with X, Y or Z.2020-10-27T20:48:54-04:00W. Alan ScottAdd ability to move camera (in 3d space) with X, Y or Z.We currently have the ability to rotate objects (well, the camera actually) around the X, Y or Z axis if we push down on the X, Y or Z key - and then move the mouse.
Please add the ability to hold down the SHFT key, and the X, Y or Z ke...We currently have the ability to rotate objects (well, the camera actually) around the X, Y or Z axis if we push down on the X, Y or Z key - and then move the mouse.
Please add the ability to hold down the SHFT key, and the X, Y or Z key, and translate the object on the X, Y or Z axis.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19278Writing .csv file is crashing, remote server.2020-01-16T18:06:12-05:00W. Alan ScottWriting .csv file is crashing, remote server.We are crashing ParaView when saving a .csv file, remote server.
* Use 32 servers, Linux, master.
* Load Watney's 144 file Exodus dataset. All vars on, Apply.
* GenerateGlobalId filter. Success!
* Hover Cells On, find a cell. I chose...We are crashing ParaView when saving a .csv file, remote server.
* Use 32 servers, Linux, master.
* Load Watney's 144 file Exodus dataset. All vars on, Apply.
* GenerateGlobalId filter. Success!
* Hover Cells On, find a cell. I chose GlobalCellId 14543.
* Find Data. Find this GlobalCellId.
* Extract Selection. Apply.
* Spreadsheet view.
* File/ Save Data. **Field Association**, Cells. Only save wall-heat-flux. Save as .csv file. Save all time.
Crashes with the following.
```
pvserver: ///snip///VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/algorithms/kdtree-sampling.hpp:429: float vtkdiy2::detail::KDTreeSamplingPartition<Block, Point>::find_split(const Bounds&, const Bounds&) const [with Block = {anonymous}::PointBlockT; Point = {anonymous}::PointTT; vtkdiy2::detail::KDTreeSamplingPartition<Block, Point>::Bounds = vtkdiy2::Bounds<float>]: Assertion `0' failed.
Loguru caught a signal: SIGABRT
Stack trace:
73 0x401589 ///snip///bin/pvserver() [0x401589]
72 0x2aaaaacf13d5 __libc_start_main + 245
71 0x401a5c ///snip///bin/pvserver() [0x401a5c]
70 0x4019af ///snip///bin/pvserver() [0x4019af]
69 0x2aaaae463784 vtkMultiProcessController::ProcessRMIs() + 34
68 0x2aaaae4637d1 vtkMultiProcessController::ProcessRMIs(int, int) + 75
67 0x2aaaae4633b6 vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 258
66 0x2aaaae464184 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 786
65 0x2aaaacdeffde ///snip////bin/../lib/libvtkPVServerImplementationCore-pv5.7.so.1(+0x88fde) [0x2aaaacdeffde]
64 0x2aaaacdf2212 vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 212
63 0x2aaaacdf2332 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 222
62 0x2aaaad934dfd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 67
61 0x2aaaad934f4f vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 309
60 0x2aaaad93591f vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 453
59 0x2aaaad937199 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 679
58 0x2aaaab49faf1 ///snip////../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x403af1) [0x2aaaab49faf1]
57 0x2aaaad48b5c1 vtkFileSeriesWriter::Write() + 417
56 0x2aaab17c164f vtkAlgorithm::Update() + 77
55 0x2aaab17c1684 vtkAlgorithm::Update(int) + 50
54 0x2aaab18324a4 vtkStreamingDemandDrivenPipeline::Update(int) + 48
53 0x2aaab1832618 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 370
52 0x2aaab17d33a7 vtkDemandDrivenPipeline::UpdateData(int) + 679
51 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
50 0x2aaab17d2c98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1464
49 0x2aaab17c922a vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1022
48 0x2aaab17d3572 vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 140
47 0x2aaab1834e1f vtkStreamingDemandDrivenPipeline::ExecuteDataEnd(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 821
46 0x2aaab18324a4 vtkStreamingDemandDrivenPipeline::Update(int) + 48
45 0x2aaab1832618 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 370
44 0x2aaab17d33a7 vtkDemandDrivenPipeline::UpdateData(int) + 679
43 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
42 0x2aaab17d2b98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
41 0x2aaab17cb964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
40 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
39 0x2aaab17d2b98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
38 0x2aaab17cb964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
37 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
36 0x2aaab17d2b98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
35 0x2aaab17cb964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
34 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
33 0x2aaab17d2b98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
32 0x2aaab17cb964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
31 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
30 0x2aaab17d2b98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
29 0x2aaab17cb964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
28 0x2aaab1832279 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
27 0x2aaab17d2c98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1464
26 0x2aaab17c922a vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1022
25 0x2aaab17d354d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 103
24 0x2aaab17dacae vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 118
23 0x2aaab17fb13e vtkPassInputTypeAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 90
22 0x2aaac2908d8a vtkGenerateGlobalIds::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 216
21 0x2aaac2909c12 ///snip////bin/../lib/libvtkFiltersParallelDIY2-pv5.7.so.1(+0xacc12) [0x2aaac2909c12]
20 0x2aaac290b6a1 ///snip////bin/../lib/libvtkFiltersParallelDIY2-pv5.7.so.1(+0xae6a1) [0x2aaac290b6a1]
5 0x2aaac291399d ///snip////bin/../lib/libvtkFiltersParallelDIY2-pv5.7.so.1(+0xb699d) [0x2aaac291399d]
4 0x2aaaaacfe0d2 /lib64/libc.so.6(+0x2f0d2) [0x2aaaaacfe0d2]
3 0x2aaaaacfe026 /lib64/libc.so.6(+0x2f026) [0x2aaaaacfe026]
2 0x2aaaaad068f8 abort + 328
1 0x2aaaaad05207 gsignal + 55
0 0x2aaaaad05280 /lib64/libc.so.6(+0x36280) [0x2aaaaad05280]
```5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19277GenerateGlobalId filter crashes in parallel2019-10-16T21:59:31-04:00W. Alan ScottGenerateGlobalId filter crashes in parallelWe have a crash in the GenerateGlobalId filter. Here is how to replicate:
* 64 remote servers (sorry Utkarsh), Linux, master (v5.7.0-RC2-359-g5c06243). Note that 32 remote servers does NOT show this bug.
* Load the Watney Exodus datas...We have a crash in the GenerateGlobalId filter. Here is how to replicate:
* 64 remote servers (sorry Utkarsh), Linux, master (v5.7.0-RC2-359-g5c06243). Note that 32 remote servers does NOT show this bug.
* Load the Watney Exodus dataset. All vars on. Apply.
* GenerateGlobalIds.
Server side crash.
You get lots of:
```
pvserver: ////snip///VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/algorithms/kdtree-sampling.hpp:429: float vtkdiy2::detail::KDTreeSamplingPartition<Block, Point>::find_split(const Bounds&, const Bounds&) const [with Block = {anonymous}::PointBlockT; Point = {anonymous}::PointTT; vtkdiy2::detail::KDTreeSamplingPartition<Block, Point>::Bounds = vtkdiy2::Bounds<float>]: Assertion `0' failed.
Loguru caught a signal: SIGABRT
```
@utkarsh.ayachit
This is a Watney bug.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19276Add back PARAVIEW_AUTOLOAD_PLUGIN_XXX or similar2020-06-29T21:54:16-04:00Mathieu Westphal (Kitware)Add back PARAVIEW_AUTOLOAD_PLUGIN_XXX or similarPARAVIEW_AUTOLOAD_PLUGIN_XXX has been removed during the module rework.
Please add it back.
@ben.boeckelPARAVIEW_AUTOLOAD_PLUGIN_XXX has been removed during the module rework.
Please add it back.
@ben.boeckel5.8.1Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19274Glyph filter omits last entry of point dataset2019-08-26T10:37:02-04:00Philip EisenlohrGlyph filter omits last entry of point datasetAfter importing a VTP dataset and applying a Glyph filter, the last entry in the input dataset is omitted/missing. I attach a sample dataset containing three points. Out of those, only the first two will be shown. This issue is reproduci...After importing a VTP dataset and applying a Glyph filter, the last entry in the input dataset is omitted/missing. I attach a sample dataset containing three points. Out of those, only the first two will be shown. This issue is reproducible for 5.6.0 and 5.7.0RC2, so I assume that it is broken since a longer while...
[3point.vtp](/uploads/7c054af2ab48edee254579e8280c5499/3point.vtp)https://gitlab.kitware.com/paraview/paraview/-/issues/19273Catalyst scripts with Composable + Recolorable cinema exports are different2019-11-04T11:00:50-05:00Ethan StamCatalyst scripts with Composable + Recolorable cinema exports are different@dhr @demarle
Catalyst scripts that dump composable+recolorable cdb's are different if you start with a source vs. if you start with loaded data.
Steps to reproduce:
(Source)
1. Make a default wavelet source
2. View -> Export Inspect...@dhr @demarle
Catalyst scripts that dump composable+recolorable cdb's are different if you start with a source vs. if you start with loaded data.
Steps to reproduce:
(Source)
1. Make a default wavelet source
2. View -> Export Inspector
3. Click the advanced gear -> Check the box for Cinema Image Options -> Choose RTData in the Cinema Image Options window
4. Choose Cinema Image Database for the image extract -> Check its box and set composable + recolorable instead of None for deferred rendering
5. Set a root directory and check the box for cinema spec D table
6. Catalyst -> Export Catalyst Script
(Data)
1. Save and load the default wavelet source
2...6 are the same, but save the catalyst script with a different name.
Compare the two catalyst scripts. Only the script with the wavelet source has coprocessor.AddArraysToCinemaTrack().
Two scripts that I generated are attached.
[source_data_catalyst.py](/uploads/a6bc333a4f4a66f547cc9b6ffbe741b6/source_data_catalyst.py)
[read_data_catalyst.py](/uploads/c15a920182b9caa73dba079a4d7cd07c/read_data_catalyst.py)Ethan StamEthan Stamhttps://gitlab.kitware.com/paraview/paraview/-/issues/19272Crash on axis cut filter for HTG only in Y direction2019-10-29T16:07:06-04:00Yohann Bearzi (Kitware)Crash on axis cut filter for HTG only in Y directionWhen applying Axis Cut filter to a hyper tree grid in Y direction, it crashes.
To reproduce:
* Source -> Data Object -> Hyper Tree Grid (Random)
* Apply
* Filters -> Hyper Tree Grid -> Hyper Tree Grid - Axis Cut
* 'Plane Normal' ...When applying Axis Cut filter to a hyper tree grid in Y direction, it crashes.
To reproduce:
* Source -> Data Object -> Hyper Tree Grid (Random)
* Apply
* Filters -> Hyper Tree Grid -> Hyper Tree Grid - Axis Cut
* 'Plane Normal' set to 'Y Axis'
* 'Plane Position' to any number but 0
* ApplyYohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19271Please make the Find Data dialog to be dockable.2021-04-28T20:42:41-04:00W. Alan ScottPlease make the Find Data dialog to be dockable.Please make the Find Data dialog be dockable. Also, default it to the left side.Please make the Find Data dialog be dockable. Also, default it to the left side.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19268Color legend visibility isn't correctly sticky2020-05-06T21:15:04-04:00W. Alan ScottColor legend visibility isn't correctly stickyThe color legend doesn't stay off properly. Here is how to replicate:
* 5.6.0, OS X, builtin server.
* Open can.exo. All variables on.
* Hide the color legend.
* Turn visibility off for can.exo.
* Turn visibility on for can.exo.
The c...The color legend doesn't stay off properly. Here is how to replicate:
* 5.6.0, OS X, builtin server.
* Open can.exo. All variables on.
* Hide the color legend.
* Turn visibility off for can.exo.
* Turn visibility on for can.exo.
The color legend is back, but shouldn't be. This is a bug. This happens with a variable, or annotation color map.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19267Add color map resource web page2021-11-09T15:20:38-05:00W. Alan ScottAdd color map resource web pagePlease add a web page on the paraview.org site that references different color map resources. These should include:
* Francesca Samsel's sciviscolor.org
* Ken Moreland's kenmoreland.com, specifically links on color maps
* Color Brewer -...Please add a web page on the paraview.org site that references different color map resources. These should include:
* Francesca Samsel's sciviscolor.org
* Ken Moreland's kenmoreland.com, specifically links on color maps
* Color Brewer - colorbrewer2.org
* Event Horizon Telescope color maps https://github.com/liamedeiros/ehtplot/blob/docs/docs/COLORMAPS.ipynb
Please contact Francesca, and also Ken, and ask for additional pages and references.
Please add one line to the Help menu, linking to this page.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19266Coordinate Results output crashes Calculator2019-09-05T18:42:58-04:00Niklas RoeberCoordinate Results output crashes CalculatorApplying Coordinate Results within a calculator crashes ParaView5.7. We use this a lot to extrude orography. Steps to reproduce:
- Start ParaView
- Create a Wavelet
- Create a Contour
- Create a Calculator, enable "Coordinate Results",...Applying Coordinate Results within a calculator crashes ParaView5.7. We use this a lot to extrude orography. Steps to reproduce:
- Start ParaView
- Create a Wavelet
- Create a Contour
- Create a Calculator, enable "Coordinate Results", enter the formula:
iHat * coordsX + jHat * coordsY + (RTData/200 * ( kHat * (1+coordsZ)))
- Crash
This formula is nonsense for the wavelet in this way, but extrudes the orography in lon/lat projection. Good old ParaView 5.6 works well.5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19264[INSTALL] Files missing in install directory2020-05-05T22:08:09-04:00Mathieu Westphal (Kitware)[INSTALL] Files missing in install directoryLooks like some file are missing from install directory.
One example is **vtkChartSelectionHelper.h**, but others may be missing as well.
@ben.boeckel @charles.gueunetLooks like some file are missing from install directory.
One example is **vtkChartSelectionHelper.h**, but others may be missing as well.
@ben.boeckel @charles.gueunethttps://gitlab.kitware.com/paraview/paraview/-/issues/19263[PBR] position light cone angle and focal point has no effect with PBR2019-09-04T07:14:42-04:00Mathieu Westphal (Kitware)[PBR] position light cone angle and focal point has no effect with PBRin PBR mode, position light cone angle has no effect
Steps to reproduce :
* Open ParaView
* Wavelet apply
* switch to PBR
* View -> Light Inspector
* Add a light
* positional
* Position : 0, 30, 0
* Focal Point : 0, 0, 0
* Cha...in PBR mode, position light cone angle has no effect
Steps to reproduce :
* Open ParaView
* Wavelet apply
* switch to PBR
* View -> Light Inspector
* Add a light
* positional
* Position : 0, 30, 0
* Focal Point : 0, 0, 0
* Change cone angle, or focal point, **no effect at all**
![Peek_2019-08-21_09-18](/uploads/fcb886b8eb7556339c38e9b1bbdb4f17/Peek_2019-08-21_09-18.gif)
@michael.miglioreMichael MiglioreMichael Migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19258Lights are uncontrollable2019-08-16T13:23:26-04:00W. Alan ScottLights are uncontrollablePlease update the mouse controls for the lights. They are unusable.
* Linux, 5.7.0-RC2, builtin server.
* Sources/ Cone.
* View/ Light Inspector. Add a light. Coords Scene. Type Positional.
* Make sure that Show Light is checked.
...Please update the mouse controls for the lights. They are unusable.
* Linux, 5.7.0-RC2, builtin server.
* Sources/ Cone.
* View/ Light Inspector. Add a light. Coords Scene. Type Positional.
* Make sure that Show Light is checked.
* Zoom out.
Now, grab the ball at the base of the cone. Move it around. You are doing two things in 3d space at the same time, on a 2d screen. One is you are moving the sphere, second is you are changing the size of the cone. Unusable.
Maybe:
* Add a hot key, like "s" for size, or something. Then, when the key is down, you only move one thing.
* Maybe make it so that if the sphere is selected, and the x, y or z key is selected, you move the sphere in that axis. Alternatively, if the "r" (or "s") is selected, you change the size of the cone?