ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-09-06T04:58:24-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22285ProcessIds cannot be shown in ParaView when using local rendering2023-09-06T04:58:24-04:00Mathieu Westphal (Kitware)ProcessIds cannot be shown in ParaView when using local renderingProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to repro...ProcessIds are a recently introduced attributes data, similar to GlobalIds. The filter `GenerateProcessIds` can generate such ideas,
however, they are not copied to the client when using client/server with local rendering.
Step to reproduce:
- run pvserver, run paraview
- Connect to pvserver
- Make sure remote rendering threshold is higher than 20Mb
- Sphere, Apply
- GenerateProcessIds, Apply
- Try to color with ProcessIds, no data is visible and solid color is used, this is a bug
- A simple work around is to use calculator to copy the array in a non ProcessIds arrays
This is probably caused by the copy of the surfacic data from the server to the client which probably ignore the ProcessIds
Note: The following tests are impacted by this bug and should be modified whenever this bug is fixed:
- DistributePoints
- GenerateProcessIds
- GhostCellsGeneratorSynchronizehttps://gitlab.kitware.com/paraview/paraview/-/issues/22284Issue while reading data from lagrangian particles generated by OpenFOAM usin...2023-09-05T11:42:41-04:00franco otaolaIssue while reading data from lagrangian particles generated by OpenFOAM using the OpenFOAM readerHello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the ...Hello,
when opening a simulation with lagrangian particles done in OpenFOAM, there is an issue with the time stamps of the particles which blocks the possibility of using for example the temporal particles pathlines filter to create the path that the particles followed during the simulation, even though the data 'is there'. Here is the discussion of about the issue: https://discourse.paraview.org/t/lagrangianparticletracker-example-file/571 , the error that I am getting (using paraview 5.11.1 with OpenFOAM 2306) is the following:
```
ERROR: In vtkTemporalPathLineFilter.cxx, line 343
vtkTemporalPathLineFilter (000001E683425760): The input dataset did not have a valid DATA_TIME_STEPS information key
ERROR: In vtkExecutive.cxx, line 741
vtkPVCompositeDataPipeline (000001E692199690): Algorithm vtkTemporalPathLineFilter (000001E683425760) returned failure for request: vtkInformation (000001E690439420)
Debug: Off
Modified Time: 2518182
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
```
here the files of the case with some data can be downloaded, the data was to large to upload directly to the gitlab [link](https://filesender.utc.fr/filesender/?s=download&token=30fc3d13-37cb-47d4-aab3-d82b8632b53e)
best regardshttps://gitlab.kitware.com/paraview/paraview/-/issues/22281Issue with representation type selection with Qt6 on Arch Linux2024-01-25T10:27:58-05:00Yvan FournierIssue with representation type selection with Qt6 on Arch LinuxHello,
On Arch Linux, building ParaView with Qt6, I have an issue with a the representation mode selection:
```plaintext
When right-clicking on a mesh ans selecting the representation type with th checkbox selection, everything is fine...Hello,
On Arch Linux, building ParaView with Qt6, I have an issue with a the representation mode selection:
```plaintext
When right-clicking on a mesh ans selecting the representation type with th checkbox selection, everything is fine.
When using the combo box (either on the toolbar or in the properties tab), nothing changes (the default remains at “Surface”).
```
The latest version I compiled (a few days ago) is:
```plaintext
Client Information:
Version: 5.11.1-1525-g2c4973080c
VTK Version: 9.2.6-4140-g40c19ea4e8
Qt Version: 6.5.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /usr/lib/python3.11
Python Library Version: 3.11.3 (main, Jun 5 2023, 09:32:32) [GCC 13.1.1 20230429]
Python Numpy Support: On
Python Numpy Path: /usr/lib/python3.11/site-packages/numpy
Python Numpy Version: 1.25.1
Python Matplotlib Support: On
Python Matplotlib Path: /usr/lib/python3.11/site-packages/matplotlib
Python Matplotlib Version: 3.7.2
Python Testing: Off
MPI Enabled: On
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: Sequential
SMP Max Number of Threads: 1
OpenGL Vendor: Intel
OpenGL Version: 4.6 (Core Profile) Mesa 23.1.6
OpenGL Renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
```
I have the same behavior with the NVIDIA driver (under optirun).
```plaintext
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 535.98
OpenGL Renderer: NVIDIA GeForce GTX 1050 with Max-Q Design/PCIe/SSE2
```
Other combo-box based settings seem to work fine
I do not observe it when building against Qt5.
Best regards,https://gitlab.kitware.com/paraview/paraview/-/issues/22280Paraview 5.9.1 on MacOS version 10.15.7 (catalina) does not add text2023-09-01T15:14:58-04:00John XiaParaview 5.9.1 on MacOS version 10.15.7 (catalina) does not add textClick Sources -->Alphabetial-->text creates the text object - but does not put it on the window - either in interactive mode or by specifying window co-ordinates. Text Prop Mode == 2D Text widget (default).Click Sources -->Alphabetial-->text creates the text object - but does not put it on the window - either in interactive mode or by specifying window co-ordinates. Text Prop Mode == 2D Text widget (default).https://gitlab.kitware.com/paraview/paraview/-/issues/22278The window arrangement dose not load the main window in the proper place when...2023-08-24T12:02:46-04:00Phil SmithThe window arrangement dose not load the main window in the proper place when recalled on Windows and MacWhen saving a window arrangement on Mac and Windows( Linux appears to work properly), if you have you views that are detached from your main window, it will not load the main window in the proper location. I tested this on ParaView v5.11...When saving a window arrangement on Mac and Windows( Linux appears to work properly), if you have you views that are detached from your main window, it will not load the main window in the proper location. I tested this on ParaView v5.11.1 Master on all three platforms. When you load the window arrangement, that has been saved, the main window will load in the center of the current display. The detached views load in the locations where they were saved. Here is an example of what I saved( I have used my Mac in this example):
![image.png](/uploads/9652f827ae25c048019c693ceaee044c/image.png)
And then this is how it Loaded:
![image.png](/uploads/148c57e4e47510966a9fb1e8ddbf21a5/image.png)
If you will notice the main window stayed where it was when ParaView was loaded, however the rest of the views loaded where they saved at. The main window should have shifted to where it was originally saved at.
I have a suggestion that will make this potentially easier to manage. We can stack the windows vertically on either side within the main window. However we can only have one column on each side of the main window. How hard would it be to be able to stack the windows side by side as well? This would correct this problem. Typically a monitor is wider than it is tall, so this would make the best use of the screen real estate.
In addition, when opening ParaView with all of the views detached, only the main window opens up. In order to get the views to appear, Load Window Arrangement or selecting each view that you want is necessary. The solution that I have suggested above will fix this problem as well, because I have noticed when you close ParaView and then re-open it, the views will remain where they were the last time they were used, as long as they are docked within the main window. This way the user will not have to perform the additional step of loading the window arrangement when he re-opens ParaView.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22277Add regression test for LAMMPS dump reader (in VisItBridge) for multiple time...2023-08-23T14:50:36-04:00Kenneth MorelandAdd regression test for LAMMPS dump reader (in VisItBridge) for multiple time stepsThe LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6...The LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6454 and https://gitlab.kitware.com/paraview/visitbridge/-/merge_requests/101. The regression test currently only tests a file with one timestep. A regression test to test for multiple time steps should be added.
Here is a small, simple LAMMPS dump file with 2 timesteps.
[lammps-multitime.dump](/uploads/9df3b301f5bf33766c7c99a28c94483d/lammps-multitime.dump)https://gitlab.kitware.com/paraview/paraview/-/issues/22275Volume rendering and Ray Tracing are SLOW2023-08-24T16:51:24-04:00W. Alan ScottVolume rendering and Ray Tracing are SLOWVolume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps...Volume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps.e.16.[0-15] Apply. Color by ids. Note dataset is only 20,000 cells and 28,000 points. Not sure if that is relevant.
* > Frame rate on my workstation is about 560 fps. Way nice.
* Volume Render.
* > Frame rate on my workstation is about 16 fps. Usable, but ouch.
* Turn off Volume Rendering, turning on Surface. Turn on Ray Tracing.
* > Frame rate on my workstation is about 22 fps. Usable, but ouch - especially as we are only ray tracing the outside surface.
* Change Surface to Volume Rendering.
* > Frame rate on my workstation is about 3-4 fps. Not really usable.
For real datasets with many, many more cells this would be basically unusable. I believe we would multiply time spent by the area (which isn't impacted by cell count) and depth (which would be impacted by cell count).
The other issue is that these renders happen every time someone changes something in state, such as changes visibility of filters.https://gitlab.kitware.com/paraview/paraview/-/issues/22274New defaut colormap2024-03-23T23:51:52-04:00W. Alan ScottNew defaut colormapPlease make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.Please make the colormap named Fast on the Presets dialog the new default map.
Issue # 22271 created the Fast color map.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22273New default palette2024-03-23T23:51:57-04:00W. Alan ScottNew default palettePlease make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.Please make the palette background color named Warm Gray Background (98,93,90) the new default.
#22270 created the palette.
Showstopper for 5.13.0.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22272Find Data Panel should be able to find all points using coords instead of jus...2023-08-25T09:24:54-04:00Phil SmithFind Data Panel should be able to find all points using coords instead of just one point per blockWhile it may be useful to find only one point per block in some cases, using the Find Data Panel, when finding data this way there should be an option to find all the points that are within the epsilon value, on all blocks. To test this ...While it may be useful to find only one point per block in some cases, using the Find Data Panel, when finding data this way there should be an option to find all the points that are within the epsilon value, on all blocks. To test this I used the can.ex2 and v5.11.1 master. Here are the steps:
1. Open can.ex2, apply
2. Select View-\>Find Data
1. Data Producer: can.ex2
2. Element Type: Point
3. Select: Point, nearest to, 0 ,0 ,0 50 for the epsilon value.
It only found one point per block
There should be an option to enable finding all points on all the blocks within this epsilon from a given starting location.
The way the Find Data Panel operates now is great for some applications, and maybe this should be the default, but there should be an option to be able to select all the points within that epsilon value.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22268Color Map horizontal scrollbar should not be present by default2023-08-18T10:31:53-04:00Phil SmithColor Map horizontal scrollbar should not be present by defaultWhen I want to change color maps or adjust something, within the color map editor, there are a series of buttons down the right-hand side of the color map. They can’t be accessed without scrolling over in the horizontal scroll bar a tiny...When I want to change color maps or adjust something, within the color map editor, there are a series of buttons down the right-hand side of the color map. They can’t be accessed without scrolling over in the horizontal scroll bar a tiny bit. It’s hidden and if you don't realize they are there, you could end up missing them. Making the pane big enough to avoid this ends up taking up a lot of precious screen real-estate.
It appears the length of the text "Enable Freehand Drawing Of Opacity Transfer Function" is causing the horizontal scroll bar to appear. Is there some shorter way of saying this? Or maybe use two lines to say it.
My users have also noticed even if they re-set the size of the pane, it does not always stay that way. Maybe it is because they need the extra screen real-estate and re-size it again, but even if that is the case, it just goes to show that we need to keep it the standard size without the horizontal scroll bar.
Another suggestion was made that we could place the buttons that are on the right hand side of the scroll bar at the top of the panel, like they were in past versions of the software, so it is not necessary to scroll horizontally to see them.
This panel should not have a horizontal scroll-bar when it is the default size. It would make it much easier for the users to use it that way.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22267vtkPVPostFilterExecutive (0x1e3ecaa0): The update extent specified in the inf...2023-08-22T06:46:29-04:00baloevtkPVPostFilterExecutive (0x1e3ecaa0): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter (0x1f196a90)When creating a programmable filter from two inputs with different extents I get the following, very annoying error message.
```
(5977.475s) [paraview ]vtkStreamingDemandDrive:878 ERR| vtkPVPostFilterExecutive (0x1b7cbb80): Th...When creating a programmable filter from two inputs with different extents I get the following, very annoying error message.
```
(5977.475s) [paraview ]vtkStreamingDemandDrive:878 ERR| vtkPVPostFilterExecutive (0x1b7cbb80): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter(0x7f6488011cf0) is 0 2304 0 127 0 202, which is outside the whole extent 0 0 0 127 0 202.
```
Within the programmable filter I do take care of the fact that the discretizations of the two inputs don't match and am well aware of the fact that the discretization of the output corresponds to that of the first input.
Here is a very basic example:
```python
# trace generated using paraview version 5.11.1
#import paraview
#paraview.compatibility.major = 5
#paraview.compatibility.minor = 11
from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
renderView1 = GetActiveViewOrCreate('RenderView')
wavelet1 = Wavelet(registrationName='Wavelet1')
wavelet1.WholeExtent = [-10, 10, -10, 10, -10, 10]
wavelet1Display = Show(wavelet1, renderView1, 'UniformGridRepresentation')
wavelet2 = Wavelet(registrationName='Wavelet2')
wavelet2.WholeExtent = [-10, 10, -10, 10, 0, 0]
wavelet2Display = Show(wavelet2, renderView1, 'UniformGridRepresentation')
programmableFilter1 = ProgrammableFilter(registrationName='ProgrammableFilter1', Input=[wavelet1, wavelet2])
programmableFilter1Display = Show(programmableFilter1, renderView1, 'UniformGridRepresentation')
renderView1.Update()
```https://gitlab.kitware.com/paraview/paraview/-/issues/22262Multi block volumes with gaps do not render correctly2023-10-19T17:54:31-04:00Jaswant Panchumarti (Kitware)Multi block volumes with gaps do not render correctlyWhen a multiblock image data is rendered with Volume representation, there is a visible glitch that appears to flip the ordering of the volumes every frame. To reproduce:
1. Create Wavelet source.
2. Apply.
3. Create another Wavelet sou...When a multiblock image data is rendered with Volume representation, there is a visible glitch that appears to flip the ordering of the volumes every frame. To reproduce:
1. Create Wavelet source.
2. Apply.
3. Create another Wavelet source.
4. For the second wavelet, adjust the extent values for the x-axis. Choose values such that the wavelet does not overlap or touch the first wavelet. Ex: 40, 60
![image](/uploads/1e81f184b3602d032f6743557950e635/image.png)
5. Apply
6. Create a Group DataSets filter.
7. Select Wavelet1 and Wavelet2 using Ctrl + click and create a new GroupDatasets filter.
8. Apply
9. Change Representation to Volume and Color by RTData.
10. Move mouse in the render view.
11. See flicker.
Here's how the bug looks:
![ezgif.com-video-to-gif](/uploads/438494c0f9e6c8939627dfa4da2824f2/ezgif.com-video-to-gif.gif)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22261Filter/Source Snap to Mesh Keyboard Shortcut Not Working in LICs Visualization2023-08-16T08:16:46-04:00Elio XhemalajFilter/Source Snap to Mesh Keyboard Shortcut Not Working in LICs VisualizationWhen creating a new filter or source that has snap / snap to mesh capabilities using keyboard shortcuts ('1'/Ctrl+1','2'/Ctrl+2', or 'P'), pressing the keyboard shortcut does not work when representation is set to Surface LIC to define P...When creating a new filter or source that has snap / snap to mesh capabilities using keyboard shortcuts ('1'/Ctrl+1','2'/Ctrl+2', or 'P'), pressing the keyboard shortcut does not work when representation is set to Surface LIC to define Point1/Point2.
- Issue seen with creating line sources, clip, and slice
Reverting the source to Surface, Surface with Edges, or any other representation works as intended. Surface LICs is the only representation that generates the issue.
Tested on ParaView 5.11.1 on Windows 10.https://gitlab.kitware.com/paraview/paraview/-/issues/22260Speed up sideset reads in the IOSS reader/library reading Exodus2023-08-10T13:08:57-04:00W. Alan ScottSpeed up sideset reads in the IOSS reader/library reading ExodusWe found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLO...We found a major performance degredation in the IOSS reader/library. This was mostly solved in #22227, by changing
`dbase->set_surface_split_type(Ioss::SPLIT_BY_TOPOLOGIES);` to `dbase->set_surface_split_type(Ioss::SPLIT_BY_ELEMENT_BLOCKS);` This changed the performance degredation from about 2 orders of magnitude slower to 4x slower. We still want to discuss, research and possibly implement speeding current code up to the speeds of the Exodus reader/library.
Here is a comment from Greg Sjaardema from #22227:
OK, I think the issue is that the caching that IOSS does is to check whether the current side's parent element is from the same element block as the previous side's parent element. The sidesets in this model somewhat follow that assumption, but do switch back and forth a few/many times which results in a new query of the element block connectivity.
So, we aren't seeing 199,427 exodus calls, but we aren't seeing 2 either...
There are a few ways to fix this. I need to see what would be the least intrusive and behavior changing...
1. Can sort the elements (based on internal id, not global id) in the SideBlock lists which would guarantee an orderly progression through the element blocks.
1. Could process the sideblock element lists multiple times -- once per block. Fairly easy, but need to calculate some offsets based on the face node counts to know where to store the connectivity when skpping over elements that are not in the current element block. Not too difficult, but some added bookkeeping.
1. Cache element connectivity for multiple element blocks instead of just the "current" block. Uses more memory.
1. If sidesets use the SPLIT_BY_ELEMEMT_BLOCK method for generating homogenous sideblocks, then process in element block order by default.
@spiros.tsalikis @gsjaardema5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22258Streamlines not all rendering on MacOS-arm architecture2023-08-16T08:18:00-04:00Julien FaustyStreamlines not all rendering on MacOS-arm architectureUsing the script and data in this archive: [missing_streamlines_macos_arm.tar.gz](/uploads/f48555666f40576d48199c3e00db9150/missing_streamlines_macos_arm.tar.gz), some streamlines that render on linux and MacOS-x86 don't appear when rend...Using the script and data in this archive: [missing_streamlines_macos_arm.tar.gz](/uploads/f48555666f40576d48199c3e00db9150/missing_streamlines_macos_arm.tar.gz), some streamlines that render on linux and MacOS-x86 don't appear when rendering on MacOS-arm.
Reference image:
![image](/uploads/59c503376229ce5e803b813af745452f/image.png)
MacOS-arm image:
![image](/uploads/5c534fce5f5be188a1b57d2debc77ef3/image.png)
## Steps to reproduce
* `cd missing_streamlines_macos_arm/script`
* `pvbatch missing_streamlines_macos_arm.py`
* look at the images generated in `missing_streamlines_macos_arm/output`https://gitlab.kitware.com/paraview/paraview/-/issues/22255Custom axes titles are not working consistently2023-08-16T08:23:14-04:00Utkarsh AyachitCustom axes titles are not working consistentlyversion: 5.11.0
os: windows 11
Steps:
* Start ParaView in builtin mode. Load **NonOrthogonalSource** plugin.
* Create "Sheared Wavelet" source from Sources menu
* Check **Enable Axis Titles** on the `Properties` panel.
* Hit **Apply*: w...version: 5.11.0
os: windows 11
Steps:
* Start ParaView in builtin mode. Load **NonOrthogonalSource** plugin.
* Create "Sheared Wavelet" source from Sources menu
* Check **Enable Axis Titles** on the `Properties` panel.
* Hit **Apply*: what was expected that is that the X/Y/Z labels on the orientation widget would reflect the chosen axes labels. They dont.
* Turn no **Axes Grid**: correctly shows axes labels. Turn off to avoid overlap with next step.
* Turn on **Data Axes Grid**: incorrectly shows axes labels.https://gitlab.kitware.com/paraview/paraview/-/issues/22254When creating two Box sources, with the Boxes not centered on the origin, sel...2023-08-16T08:23:38-04:00Phil SmithWhen creating two Box sources, with the Boxes not centered on the origin, selecting the Outline representation is incorrect.Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illu...Steps to reproduce:
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
* Representation to outline
* Select Box from the sources menu
* For illustration purposes change the Y and Z Length to 100000, X Length to 0; center to 0,0,10000
* Apply
This appears to work correctly on either builtin or when connected to the server of your choice. I think it is working correctly when builtin is being used, because the dementions of both boxes are the same, but I could be incorrect. This only happens when there is an offset to the center of the box.
I also noticed that when connected to a server and outline is selected as the representation for Box1, the bottom of the box gets elongated. This may be the expected behavior, because the center is off, but then the builtin would be incorrect, because it dose not elongate the outline under the same circumstances.
Thanks,
\-Phil5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22253Sample over Line artifacts for P3 tets2023-08-03T15:25:50-04:00Jed BrownSample over Line artifacts for P3 tets`Sample Uniformly` yields no data (#22252 ).
## `Sample at Cell Boundaries`
![image](/uploads/c896531d73d9e78cdfb701467754524d/image.png)
## `Sample at Segment Centers`
![image](/uploads/f4f110d1709e250954ab50f06b879751/image.png)
...`Sample Uniformly` yields no data (#22252 ).
## `Sample at Cell Boundaries`
![image](/uploads/c896531d73d9e78cdfb701467754524d/image.png)
## `Sample at Segment Centers`
![image](/uploads/f4f110d1709e250954ab50f06b879751/image.png)
## With tetrahedralize filter (suggested by @dcthomp )
![image](/uploads/bed31cdaccd63ed05ecc26b85c0f0327/image.png)
https://drive.google.com/file/d/1XLpKZ_YGDQynpOqBPcfipF4NVhDxL8JY/view?usp=drive_link
Cc: @c.wetterer-nelsonhttps://gitlab.kitware.com/paraview/paraview/-/issues/22252Plot over line with Sample Uniformly yields no data for high order elements2023-08-03T15:25:50-04:00Jed BrownPlot over line with Sample Uniformly yields no data for high order elementsThis uses Q3 quad elements. The `Sample at Cell Boundaries` and `Sample at Segment Centers` behaves correctly (but loses high order information).
![image](/uploads/f8964a6a0758ed019543c7e015cd3e5b/image.png)
https://drive.google.com/fi...This uses Q3 quad elements. The `Sample at Cell Boundaries` and `Sample at Segment Centers` behaves correctly (but loses high order information).
![image](/uploads/f8964a6a0758ed019543c7e015cd3e5b/image.png)
https://drive.google.com/file/d/1r5EEL4Yke4eyR-g1-QcTF_ump_mQywT1/view?usp=drive_link