ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-08-31T04:54:00-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17768XML parsing of the Statefile is slow and grow in O(n^2)2023-08-31T04:54:00-04:00Jonathan BorduasXML parsing of the Statefile is slow and grow in O(n^2)Hello, dear developers.
With paraview 5.3, the loading time of a state file explodes with the number of filters in the pipeline.
A simple way to test this:
1. Create 100+ sphere sources in a state file (I strongly recommend using a mac...Hello, dear developers.
With paraview 5.3, the loading time of a state file explodes with the number of filters in the pipeline.
A simple way to test this:
1. Create 100+ sphere sources in a state file (I strongly recommend using a macro). In my tests, all spheres were visible.
2. Save the state.
3. Disconnect
3. Load the state.
My tests:
100 spheres - 7 mb - 15 sec.
200 spheres - 15 mb - 60 sec.
300 spheres - 20 mb - 120 sec.
It seems to follow an order of growth of O(n^2). I found that surprising since there aren't any link between the spheres and would expect a linear growth.
I saw in the code that we are using a 3 years old version of pugixml (1.4) while they are at 1.8. Maybe an upgrade would speed up the process and hopefully make it O(n). I tried swapping with 1.8, but the interface change considerably between 1.4 and 1.8.
Maybe another XML parsing library would scale up in a better way. Finally, I don't know if it would really be faster, but maybe the statefile should be saved in JSON ?
Thanks in advance, Jonathan.https://gitlab.kitware.com/paraview/paraview/-/issues/17766SaveScreenshot(Layout) in python does not give the same results as Save Scree...2021-03-23T13:50:13-04:00Mathieu Westphal (Kitware)SaveScreenshot(Layout) in python does not give the same results as Save Screenshot fonctionnality in paraviewHow to reproduce :
- Open ParaView
- Load this [TestState.pvsm](/uploads/49c76a4ab8002d8b8add0cfc1cafebc6/TestState.pvsm)
- Save Screenshot All View
- This image is generated :
![TestState2](/uploads/db659ccb6eccf7321ca6a26298236b9c/Te...How to reproduce :
- Open ParaView
- Load this [TestState.pvsm](/uploads/49c76a4ab8002d8b8add0cfc1cafebc6/TestState.pvsm)
- Save Screenshot All View
- This image is generated :
![TestState2](/uploads/db659ccb6eccf7321ca6a26298236b9c/TestState2.png)
- Open pvpython
- LoadState()
- SaveScreenshot("file.png", GetLayout())
- This image is generated :
![TestState](/uploads/e5d31cea2edaa300ad6d47fc5da0f44f/TestState.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17765Interactive View Link background hiding not working2021-03-23T13:50:21-04:00Mathieu Westphal (Kitware)Interactive View Link background hiding not working- Open ParaView
- Create two view, set a different background for a view
- Add a Camera Link with an interactive view link
- Edit camera options
- enable background opacity
- no effect- Open ParaView
- Create two view, set a different background for a view
- Add a Camera Link with an interactive view link
- Edit camera options
- enable background opacity
- no effectMathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17749Creating a selection in Python does not enable "Clear selection" button2023-06-15T11:14:42-04:00Cory Quammencory.quammen@kitware.comCreating a selection in Python does not enable "Clear selection" button* Start ParaView
* Add a Sphere
* In the Python console, run:
`SelectPoints()`
* The trash can "Clear selection" tool button in the selection bar is not enabled, but should be.* Start ParaView
* Add a Sphere
* In the Python console, run:
`SelectPoints()`
* The trash can "Clear selection" tool button in the selection bar is not enabled, but should be.https://gitlab.kitware.com/paraview/paraview/-/issues/17744Loading a state file via Recent Files menu does not offer a "fix paths" dialog.2021-03-23T13:52:30-04:00Artem BodrinLoading a state file via Recent Files menu does not offer a "fix paths" dialog.Hello, dear developers.
Simple test: open a PNG file, save state, detach from server (or restart ParaView), use File->Recent Files->YourSavedState - no "Load State Options" Dialog.
Use File->Load State..., choose saved test state, dial...Hello, dear developers.
Simple test: open a PNG file, save state, detach from server (or restart ParaView), use File->Recent Files->YourSavedState - no "Load State Options" Dialog.
Use File->Load State..., choose saved test state, dialog is offered.https://gitlab.kitware.com/paraview/paraview/-/issues/17743pqApplicationCore does not emit aboutToLoadState signal anymore2024-03-07T20:47:45-05:00Artem BodrinpqApplicationCore does not emit aboutToLoadState signal anymoreHello, dear developers.
With a release of ParaView v5.4 you have changed a state loading procedure, so signal pqApplicationCore::aboutToLoadState() does not emitted anymore, but left in code.
I have to say that this is really useful sig...Hello, dear developers.
With a release of ParaView v5.4 you have changed a state loading procedure, so signal pqApplicationCore::aboutToLoadState() does not emitted anymore, but left in code.
I have to say that this is really useful signal to adjust state XML file before it is loaded. Is this a bug or you have desided to get rid of it in future? In the latter case is there any workaround to get a root XML element right before loading the state (maybe via handling some vtkCommand somehow?)
Thanks in advance, Artem.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17742Failure when replaying trace of cube file merging2021-03-23T13:53:01-04:00Ian BellFailure when replaying trace of cube file mergingI did a simple pipeline:
```
0. Start trace
1. Load two cube files from file (generated by Psi4), one for density, another for ESP
2. Contour from density cube file
3. Resample contour with the ESP from cube file 2
4. Stop trace
5. ...I did a simple pipeline:
```
0. Start trace
1. Load two cube files from file (generated by Psi4), one for density, another for ESP
2. Contour from density cube file
3. Resample contour with the ESP from cube file 2
4. Stop trace
5. Run the generated script with ``/Applications/ParaView-5.4.1.app/Contents/bin/pvpython to_png.py``.
```
Same error when I run script from python shell in paraview
Output is:
```
>>> Traceback (most recent call last):
File "<string>", line 80, in <module>
File "/Applications/ParaView-5.4.1.app/Contents/Python/paraview/servermanager.py", line 1613, in OutputPort
if outputPort >= proxy.GetNumberOfOutputPorts():
AttributeError: 'NoneType' object has no attribute 'GetNumberOfOutputPorts'
```
Script below:
``` python
#### import the simple module from the paraview
from paraview.simple import *
#### disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()
# create a new 'Gaussian Cube Reader'
dtcube = GaussianCubeReader(FileName='/Users/ian/vmd/pfe/Dt.cube')
# create a new 'Gaussian Cube Reader'
eSPcube = GaussianCubeReader(FileName='/Users/ian/vmd/pfe/ESP.cube')
# set active source
SetActiveSource(dtcube)
# get active view
renderView1 = GetActiveViewOrCreate('RenderView')
# uncomment following to set a specific view size
# renderView1.ViewSize = [396, 552]
# show data in view
dtcubeDisplay = Show(dtcube, renderView1)
# trace defaults for the display properties.
dtcubeDisplay.Representation = 'Molecule'
# reset view to fit data
renderView1.ResetCamera()
# show color bar/color legend
dtcubeDisplay.SetScalarBarVisibility(renderView1, True)
# show data in view
dtcubeDisplay_1 = Show(OutputPort(dtcube, 1), renderView1)
# trace defaults for the display properties.
dtcubeDisplay_1.Representation = 'Outline'
dtcubeDisplay_1.ColorArrayName = ['POINTS', '']
dtcubeDisplay_1.OSPRayScaleArray = 'Property: Dt'
dtcubeDisplay_1.OSPRayScaleFunction = 'PiecewiseFunction'
dtcubeDisplay_1.SelectOrientationVectors = 'None'
dtcubeDisplay_1.ScaleFactor = 6.9
dtcubeDisplay_1.SelectScaleArray = 'Property: Dt'
dtcubeDisplay_1.GlyphType = 'Arrow'
dtcubeDisplay_1.GlyphTableIndexArray = 'Property: Dt'
dtcubeDisplay_1.DataAxesGrid = 'GridAxesRepresentation'
dtcubeDisplay_1.PolarAxes = 'PolarAxesRepresentation'
dtcubeDisplay_1.ScalarOpacityUnitDistance = 1.735365729852697
dtcubeDisplay_1.Slice = 31
# show data in view
eSPcubeDisplay = Show(eSPcube, renderView1)
# trace defaults for the display properties.
eSPcubeDisplay.Representation = 'Molecule'
# show color bar/color legend
eSPcubeDisplay.SetScalarBarVisibility(renderView1, True)
# show data in view
eSPcubeDisplay_1 = Show(OutputPort(eSPcube, 1), renderView1)
# trace defaults for the display properties.
eSPcubeDisplay_1.Representation = 'Outline'
eSPcubeDisplay_1.ColorArrayName = ['POINTS', '']
eSPcubeDisplay_1.OSPRayScaleArray = 'Property: ESP'
eSPcubeDisplay_1.OSPRayScaleFunction = 'PiecewiseFunction'
eSPcubeDisplay_1.SelectOrientationVectors = 'None'
eSPcubeDisplay_1.ScaleFactor = 6.9
eSPcubeDisplay_1.SelectScaleArray = 'Property: ESP'
eSPcubeDisplay_1.GlyphType = 'Arrow'
eSPcubeDisplay_1.GlyphTableIndexArray = 'Property: ESP'
eSPcubeDisplay_1.DataAxesGrid = 'GridAxesRepresentation'
eSPcubeDisplay_1.PolarAxes = 'PolarAxesRepresentation'
eSPcubeDisplay_1.ScalarOpacityUnitDistance = 1.735365729852697
eSPcubeDisplay_1.Slice = 31
# update the view to ensure updated data information
renderView1.Update()
# find source
dtcube_1 = FindSource('Dt.cube')
# create a new 'Contour'
contour1 = Contour(Input=OutputPort(dtcube_1,1))
contour1.ContourBy = ['POINTS', 'Property: Dt']
contour1.Isosurfaces = [69.45500183549095]
contour1.PointMergeMethod = 'Uniform Binning'
# Properties modified on contour1
contour1.Isosurfaces = [0.002]
# show data in view
contour1Display = Show(contour1, renderView1)
# trace defaults for the display properties.
contour1Display.Representation = 'Surface'
contour1Display.ColorArrayName = [None, '']
contour1Display.OSPRayScaleArray = 'Normals'
contour1Display.OSPRayScaleFunction = 'PiecewiseFunction'
contour1Display.SelectOrientationVectors = 'None'
contour1Display.ScaleFactor = 5.507733917236329
contour1Display.SelectScaleArray = 'None'
contour1Display.GlyphType = 'Arrow'
contour1Display.GlyphTableIndexArray = 'None'
contour1Display.DataAxesGrid = 'GridAxesRepresentation'
contour1Display.PolarAxes = 'PolarAxesRepresentation'
contour1Display.GaussianRadius = 2.7538669586181643
contour1Display.SetScaleArray = [None, '']
contour1Display.ScaleTransferFunction = 'PiecewiseFunction'
contour1Display.OpacityArray = [None, '']
contour1Display.OpacityTransferFunction = 'PiecewiseFunction'
# update the view to ensure updated data information
renderView1.Update()
# find source
eSPcube_1 = FindSource('ESP.cube')
# create a new 'Resample With Dataset'
resampleWithDataset1 = ResampleWithDataset(Input=OutputPort(eSPcube_1,1),
Source=contour1)
# get color transfer function/color map for 'PropertyESP'
propertyESPLUT = GetColorTransferFunction('PropertyESP')
# show data in view
resampleWithDataset1Display = Show(resampleWithDataset1, renderView1)
# trace defaults for the display properties.
resampleWithDataset1Display.Representation = 'Surface'
resampleWithDataset1Display.ColorArrayName = ['POINTS', 'Property: ESP']
resampleWithDataset1Display.LookupTable = propertyESPLUT
resampleWithDataset1Display.OSPRayScaleArray = 'Property: ESP'
resampleWithDataset1Display.OSPRayScaleFunction = 'PiecewiseFunction'
resampleWithDataset1Display.SelectOrientationVectors = 'None'
resampleWithDataset1Display.ScaleFactor = 5.507733917236329
resampleWithDataset1Display.SelectScaleArray = 'Property: ESP'
resampleWithDataset1Display.GlyphType = 'Arrow'
resampleWithDataset1Display.GlyphTableIndexArray = 'Property: ESP'
resampleWithDataset1Display.DataAxesGrid = 'GridAxesRepresentation'
resampleWithDataset1Display.PolarAxes = 'PolarAxesRepresentation'
resampleWithDataset1Display.GaussianRadius = 2.7538669586181643
resampleWithDataset1Display.SetScaleArray = ['POINTS', 'Property: ESP']
resampleWithDataset1Display.ScaleTransferFunction = 'PiecewiseFunction'
resampleWithDataset1Display.OpacityArray = ['POINTS', 'Property: ESP']
resampleWithDataset1Display.OpacityTransferFunction = 'PiecewiseFunction'
# hide data in view
Hide(OutputPort(eSPcube, 1), renderView1)
# hide data in view
Hide(contour1, renderView1)
# show color bar/color legend
resampleWithDataset1Display.SetScalarBarVisibility(renderView1, True)
# update the view to ensure updated data information
renderView1.Update()
# Rescale transfer function
propertyESPLUT.RescaleTransferFunction(-0.0565273, 0.159)
# get opacity transfer function/opacity map for 'PropertyESP'
propertyESPPWF = GetOpacityTransferFunction('PropertyESP')
# Rescale transfer function
propertyESPPWF.RescaleTransferFunction(-0.0565273, 0.159)
#### saving camera placements for all active views
# current camera placement for renderView1
renderView1.CameraPosition = [107.59699888881308, 23.59012667657415, -57.507272680761304]
renderView1.CameraFocalPoint = [32.999999046325684, 34.49999713897705, 31.000000953674316]
renderView1.CameraViewUp = [0.19001350376679654, -0.9421065764899228, 0.2762789657587113]
renderView1.CameraParallelScale = 30.59271872663042
#### uncomment the following to render all views
# RenderAllViews()
# alternatively, if you want to write images, you can use SaveScreenshot(...).
```https://gitlab.kitware.com/paraview/paraview/-/issues/17733save/load state breaks camera customizations2021-03-23T13:53:34-04:00W. Alan Scottsave/load state breaks camera customizationsSaving then loading state breaks camera customizations. Replicate as follows:
* 5.4.1, Linux, local server.
* Sources, wavelet, apply, Surface.
* File/ Save State.
* Edit/ Reset Session.
* File/ Load State.
* Edit/ Settings/ Camera...Saving then loading state breaks camera customizations. Replicate as follows:
* 5.4.1, Linux, local server.
* Sources, wavelet, apply, Surface.
* File/ Save State.
* Edit/ Reset Session.
* File/ Load State.
* Edit/ Settings/ Camera. Now, set all three buttons to Pan. Apply.
Notice that the camera manipulators was not reset. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/17732Open pvti files by group: animation stuck2021-03-23T13:54:01-04:00Ahmad HesamOpen pvti files by group: animation stuckHello,
I have a vtkImageData object that I write (with a XMLPImageDataWriter) every time step to a pvti file. Let's say for a 100 time steps. When I open the output_\*.pvti files **as a group**, properties like X, Y, Z extent and range ...Hello,
I have a vtkImageData object that I write (with a XMLPImageDataWriter) every time step to a pvti file. Let's say for a 100 time steps. When I open the output_\*.pvti files **as a group**, properties like X, Y, Z extent and range do not change as I animate over time (while in reality they do change).
And if I open the files **individually** (for example output_99.pvti) these properties are displayed correctly in ParaView.
The problem appears when I open them as a group; it then keeps the properties of the first file.
Reproducer:
1. Untar `growing_grid.tar.gz`
2. In ParaView: Open... --> Select `diffusion_grid_*` as a group
3. Check the "Show data axis" checkbox in the properties
4. Play animation and observe that the grid (vtkImageData) is not growing (see red box in image)
4. Open... -> Select `diffusion_grid_99` and observe that this is indeed larger than the last timestep of the previously opened object (see green box in image)
![static_grid_bug](/uploads/6e950a2f044ca22cb80505290596d089/static_grid_bug.png)
Does anyone else has this issue, and is there a way to solve this?
Cheers!
[growing_grid.tar.gz](/uploads/a431b7808ebfa23b213b917739f883ea/growing_grid.tar.gz)https://gitlab.kitware.com/paraview/paraview/-/issues/17727Problem opening large images due to incorrect calculation of number of points...2021-03-23T13:54:28-04:00ConstantineProblem opening large images due to incorrect calculation of number of points for large imagesThis is related to a VTK problem.
For large images, e.g. 2008x2004x2571 In vtkStructuredPointsReader, the line 429 numPts = dim[0]*dim[1]*dim[2] Executes using int32 and produces an incorrect number 1755851680
The dim array is int inste...This is related to a VTK problem.
For large images, e.g. 2008x2004x2571 In vtkStructuredPointsReader, the line 429 numPts = dim[0]*dim[1]*dim[2] Executes using int32 and produces an incorrect number 1755851680
The dim array is int instead of vtkIdType. I expect the same error is present in other readers.
So the npts!=numPts and the reader fails.https://gitlab.kitware.com/paraview/paraview/-/issues/17723Property range sliders misleading2021-12-13T05:29:00-05:00Aron HelserProperty range sliders misleadingA property with a range domain with a min and max is displayed as a range slider plus an input box, like this:
![slider](/uploads/5ac4fd8786d7c5bf7d382602ee7a110e/slider.png)
The input box lets you input values outside the min/max. Howe...A property with a range domain with a min and max is displayed as a range slider plus an input box, like this:
![slider](/uploads/5ac4fd8786d7c5bf7d382602ee7a110e/slider.png)
The input box lets you input values outside the min/max. However, it appears that the value is clamped to the min/max before being applied.
The input box still shows the unclamped value. An example: a sphere source with End Theta at 370 or larger, the theta still ends at 360. Set Start Theta to 90 to see it.
We should either allow the unclamped value, or display the clamped value in the input box.
This issue was discovered in https://gitlab.kitware.com/paraview/paraview/merge_requests/1894#note_317889https://gitlab.kitware.com/paraview/paraview/-/issues/17720Xdmf2: 3-component arrays saved to XDMF and re-read do not have 3 components2021-03-23T13:56:19-04:00Cory Quammencory.quammen@kitware.comXdmf2: 3-component arrays saved to XDMF and re-read do not have 3 componentsSteps to reproduce:
* Launch ParaView/builtin server
* Sources -> Sphere
* File -> Save Data. Save as an Xdmf Data File (*.xmf)
* Reset session.
* Load the previously saved Xdmf file. The Normals array from the Sphere source will be pre...Steps to reproduce:
* Launch ParaView/builtin server
* Sources -> Sphere
* File -> Save Data. Save as an Xdmf Data File (*.xmf)
* Reset session.
* Load the previously saved Xdmf file. The Normals array from the Sphere source will be present, but it will have a single component.
The attached files are from the Xdmf file export in this series of steps.
[VectorTest.xmf](/uploads/7ae7e1ce33d2eb5d509fd6691a231e6b/VectorTest.xmf)
[VectorTest.h5](/uploads/229935fa7d6a01315e47bd0f1e5fa451/VectorTest.h5)
Note that the `Attribute` element has an XML attribute named `Type` which is set to `"None"`. Changing this to an XML attribute named `AttributeType` and setting its value to `"Vector"` causes the "Normals" array to be read in correctly as a vector.https://gitlab.kitware.com/paraview/paraview/-/issues/17718[uservoice] Allow "copy to clipboard" data from interactive probing at mesh p...2021-03-23T13:56:35-04:00Utkarsh Ayachit[uservoice] Allow "copy to clipboard" data from interactive probing at mesh pointssee [this](https://paraview.uservoice.com/forums/11350-general/suggestions/11156898-allow-copy-to-clipboard-data-from-interactive-pr)
ParaView 5 brings the long-awaited interactive probing. I noticed the tool tip data can't be copied.see [this](https://paraview.uservoice.com/forums/11350-general/suggestions/11156898-allow-copy-to-clipboard-data-from-interactive-pr)
ParaView 5 brings the long-awaited interactive probing. I noticed the tool tip data can't be copied.https://gitlab.kitware.com/paraview/paraview/-/issues/17713enable "compute quartile" filter also for cell and point data2021-03-23T13:45:12-04:00Cornelis Bockemühlenable "compute quartile" filter also for cell and point dataCurrently the "compute quartile" filter works only for tables, but it would make sense to extend this to working for point and cell data as well. With this it would also be consistent with the "histogram" filter that already allows this.Currently the "compute quartile" filter works only for tables, but it would make sense to extend this to working for point and cell data as well. With this it would also be consistent with the "histogram" filter that already allows this.https://gitlab.kitware.com/paraview/paraview/-/issues/17707OSPRay screenshot issue using high resolution2024-03-07T20:47:45-05:00SCOSPRay screenshot issue using high resolutionIssue when exporting an image at a resolution higher than the screen size with OSPRay.
For example here is the result exporting the image with a size 2X the screen size:
![test_2X](/uploads/8e775ee4b28324946fb50d7f6b526619/test_2X.png)
...Issue when exporting an image at a resolution higher than the screen size with OSPRay.
For example here is the result exporting the image with a size 2X the screen size:
![test_2X](/uploads/8e775ee4b28324946fb50d7f6b526619/test_2X.png)
Here is how it should look:
![test_1X](/uploads/de3ea69770cbc79cc20b662d04f24e96/test_1X.png)
Thanks5.13 (Summer 2024)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17698No automatic rendering with in-situ simulations2024-01-23T04:13:53-05:00Ahmad HesamNo automatic rendering with in-situ simulationsHello,
Whenever I am trying to visualize something live (i.e. with Catalyst), the rendering view is not being updated unless I pan over the view with my mouse.
I noticed that automatic rendering *only* happens when I am dealing with a...Hello,
Whenever I am trying to visualize something live (i.e. with Catalyst), the rendering view is not being updated unless I pan over the view with my mouse.
I noticed that automatic rendering *only* happens when I am dealing with a large dataset. There seems to be some kind of a threshold for when to update the rendering view, based on the data size (or based on the amount of change in data).
I tried increasing the CoProcessor frequency (coprocessor.SetUpdateFrequencies(freqs)), and also the EnableLiveVisualization(True, freq), but it didn't help.
Attached I have a reproducer.
**To reproduce:**
0. Untar the MovingSphere.tar.gz
1. `mkdir build && cd build`
2. `cmake .. && make`
3. Open ParaView, Catalyst --> Connect, Catalyst --> Pause Simulation
4. `./Spheres ../script/sphere_script.py`
5. In ParaView I pipe the "Spheres" and "input" filters, and view them in a single RenderView (see picture below)
6. In Paraview: Catalyst --> Continue
![sphere_reproducer](/uploads/d375341d60efd172034e3f036ff46a29/sphere_reproducer.png)
**Expectation:**
After step 6 I expect one of the spheres (i.e. Glyphs) to move around the other (according to the arrows in the image above). Inspecting the values, this indeed happens, BUT the RenderView is not updated and the visualization is static... Only if I pan around the screen or Pause the simulation, the positions visually updates.
Andy Bauer hadn't heard of this issue before and advised me to open an issue here. I hope someone has an idea on how to make the visualization render automatically.
Cheers!!
[MovingSphere.tar.gz](/uploads/c6523f82d78c4edf092e1b91bf6df5d3/MovingSphere.tar.gz)https://gitlab.kitware.com/paraview/paraview/-/issues/17684Saved Parallel VTM are not ditributed the same way they were before being saved2021-03-23T13:46:46-04:00Mathieu Westphal (Kitware)Saved Parallel VTM are not ditributed the same way they were before being savedHow to reproduce :
* mpirun -np 2 ./bin/pvserver
* Open ParaView, connect to pvserver
* Create a Sphere
* Create another sphere, transform so both sphere can be seen
* Group
* Show vtkProcessId, each sphere is half stored on each n...How to reproduce :
* mpirun -np 2 ./bin/pvserver
* Open ParaView, connect to pvserver
* Create a Sphere
* Create another sphere, transform so both sphere can be seen
* Group
* Show vtkProcessId, each sphere is half stored on each node
* Save as a vtm
* Load .vtm, show vtkProcessId
* Now each node as one fulle spherehttps://gitlab.kitware.com/paraview/paraview/-/issues/17680D3 filter not working on and Xdmf2 data set2020-05-05T02:48:23-04:00David E. DeMarleD3 filter not working on and Xdmf2 data setOn the cooley install of ParaView 5.4.0, applying the D3 filter to /projects/visualization/DATA/MASS_STAR/DATA read via the Xdmf2 reader either crashes or produces unbalanced data.On the cooley install of ParaView 5.4.0, applying the D3 filter to /projects/visualization/DATA/MASS_STAR/DATA read via the Xdmf2 reader either crashes or produces unbalanced data.David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17678Enable "deep color" rendering (30 bit-per-pixel / 10 bit-per-channel and beyond)2021-03-23T13:47:05-04:00Jonathan BorduasEnable "deep color" rendering (30 bit-per-pixel / 10 bit-per-channel and beyond)As seen in the attached image, we can see the transitions between the different grays that occur with a 24bits-per-pixel screenshot export of ParaView.
While most image editing software and printer support 32bits-per-pixel such as Ms Pa...As seen in the attached image, we can see the transitions between the different grays that occur with a 24bits-per-pixel screenshot export of ParaView.
While most image editing software and printer support 32bits-per-pixel such as Ms Paint and Photoshop.
Most GPU manufacturers call that “deep color”. Some display already have 30bpp/10bpc.
[test2.tif](/uploads/022cfc23e9adf0b60fbe56041d9a07c7/test2.tif)https://gitlab.kitware.com/paraview/paraview/-/issues/17674Parallel Reading of LongArray does not work correctly2021-03-23T13:47:25-04:00Mathieu Westphal (Kitware)Parallel Reading of LongArray does not work correctlyWhen reading data containing a vtkLongArray, the data is correct only on the first node, not on the next nodes.
How to reproduce :
* Open ParaView in //
* Create a sphere, Apply
* Add a GenerateIds filter, Apply
* Save as a .pvtp (v...When reading data containing a vtkLongArray, the data is correct only on the first node, not on the next nodes.
How to reproduce :
* Open ParaView in //
* Create a sphere, Apply
* Add a GenerateIds filter, Apply
* Save as a .pvtp (vtkIdTypeArray are saved as vtkLongArray)
* Open previously saved .pvtp, only the Ids on the first node are correct
* Open individually each .vtp file, the Ids are correct.