ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-11-21T16:31:59-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/16863Cannot create `Opacity` or `Visibility` animations after loading state.2017-11-21T16:31:59-05:00Utkarsh AyachitCannot create `Opacity` or `Visibility` animations after loading state.Steps to reproduce:
1. Start ParaView, create `Sphere`, `Apply`.
2. Save state as `sphere.pvsm`.
3. From `Animation View` create a new animation track for **Sphere**:**Opacity**. Hit `Play` using the VCR controls. *<--- this should wo...Steps to reproduce:
1. Start ParaView, create `Sphere`, `Apply`.
2. Save state as `sphere.pvsm`.
3. From `Animation View` create a new animation track for **Sphere**:**Opacity**. Hit `Play` using the VCR controls. *<--- this should work as expected; you'll see the sphere go from opacity 0 to 1.*
4. Restart ParaView and load `sphere.pvsm`.
5. Now try to create a animation (similar to Step 3). ***<--- you won't be able to add a track for Opacity; this is a bug!***
This an easily testable symptom of paraview/paraview#168625.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16862After loading XML state files, certain proxies may never get deleted!2017-11-21T16:31:59-05:00Utkarsh AyachitAfter loading XML state files, certain proxies may never get deleted!After loading XML state files, certain proxies may never get deleted! While the proxies don't leak, and get cleaned up when the application quits or server disconnects, it still implies that memory won't be cleared when expected.
Step...After loading XML state files, certain proxies may never get deleted! While the proxies don't leak, and get cleaned up when the application quits or server disconnects, it still implies that memory won't be cleared when expected.
Steps to reproduce:
* Start ParaView (builtin)
* To keep things simple, close the current view, so you have an empty view and then create the `Sphere` source.
* Don't hit Apply, just save the state as One.pvsm file at this point.
Inspect the state file, at the very end, it will have something as follows:
````xml
<ProxyCollection name="pq_helper_proxies.4641">
<Item id="4652" name="RepresentationAnimationHelper"/>
</ProxyCollection>
<ProxyCollection name="sources">
<Item id="4641" name="Sphere1"/>
</ProxyCollection>
````
That's the Sphere source and it's helper proxy. If you look closely for the state of the helper proxy (search for the proxy using its id), you'll notice that it refers to the `Sphere1`'s ID as follows:
````xml
<Proxy group="misc" type="RepresentationAnimationHelper" id="4652" servers="16">
<Property name="Source" id="4652.Source" number_of_elements="1">
<Proxy value="4641"/>
</Property>
</Proxy>
````
* Delete the Sphere. Save out the state file again (Two.pvsm). Now look at the state file. Both the `RepresentationAnimationHelper` and the `Sphere1` proxies are gone. Good!
* Restart ParaView. And load One.pvsm. Delete the `Sphere1` source and save the state file (Three.pvsm). This time, in Three.pvsm while there's no `Sphere1` proxy, the `RepresentationAnimationHelper` is still present! If you look at it's state, you;ll see it's `Source` property is indeed hanging on to some proxy (which is actually the SphereSource proxy. The SphereSource won't be deleted until the application is quit!
**This is a bug!**
Another way to test this same bug is paraview/paraview#168635.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16853Cannot use texture maping and transparent rendering together2017-11-21T16:32:00-05:00Kenneth MorelandCannot use texture maping and transparent rendering togetherThere is an issue where if you apply a texture to one object and then render another object, the transparent object is rendered incorrectly. The following steps replicate the issue.
1. Create a `Sphere` source.
2. Change the `Opacity...There is an issue where if you apply a texture to one object and then render another object, the transparent object is rendered incorrectly. The following steps replicate the issue.
1. Create a `Sphere` source.
2. Change the `Opacity` of the sphere to `0.5`.
3. Create a `Plane` source. At this point, everything is working fine.
4. Load a `Texture` on the plane. Any png is fine. I used NE2_ps_bath.png, which is available as part of the ParaView test data.
Once you load the texture, you will see that the sphere is rendered incorrectly. In my version of ParaView (version 5.1.0 64-bit on Windows) I can see the NE2_ps_bath texture I loaded for the plane being mapped to the sphere. I believe the issue is that the rendering system is not correctly unloading the texture.5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16851Segfault when using "Follow Data" animation track2017-11-21T16:32:00-05:00Utkarsh AyachitSegfault when using "Follow Data" animation trackSteps to reproduce:
1. Open can.ex2, Apply
2. View | Animation View
3. Add **Camera | Follow Data**
4. Double Click on the "Camera" Track in the Animation View. In the popup dialog, hit Ok -- this will case a segfault.Steps to reproduce:
1. Open can.ex2, Apply
2. View | Animation View
3. Add **Camera | Follow Data**
4. Double Click on the "Camera" Track in the Animation View. In the popup dialog, hit Ok -- this will case a segfault.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16848Parallel Coordinates View is Broken.2017-11-21T16:32:00-05:00W. Alan ScottParallel Coordinates View is Broken.Parallel Coordinates View is broken. All I see is white.
* 5.1.2 (or master), Linux, local server.
* Change the view to be Parallel Coordinates View. All is white.
* Sources/ Wavelet, apply. You can't see anything, you can't chan...Parallel Coordinates View is broken. All I see is white.
* 5.1.2 (or master), Linux, local server.
* Change the view to be Parallel Coordinates View. All is white.
* Sources/ Wavelet, apply. You can't see anything, you can't change teh representation, you can't change the variables.
Assuming this representation is valuable, thus marking high priority. If it isn't valuable, feel free to lower priority.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16847Warning in release version of vtkRenderer2017-11-21T16:32:00-05:00W. Alan ScottWarning in release version of vtkRendererIn file /VTK/ Rendering/Core/vtkRenderer.cxx, line 1077, we are getting warnings. Is this warning necessary in production code? Seems to me that warnings should never be output in release code…
This has become a big issue for a user...In file /VTK/ Rendering/Core/vtkRenderer.cxx, line 1077, we are getting warnings. Is this warning necessary in production code? Seems to me that warnings should never be output in release code…
This has become a big issue for a user. Either fix the issue so that the warning is never called, clearly explain to the user why things are bad and what to do, or delete it (from release code).
Related bugs that can be closed when this one is fixed:
paraview/paraview#16039
paraview/paraview#15366
paraview/paraview#15124
5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16845Valgrind points out error in vtkSocketCommunicator2017-11-21T16:32:00-05:00Shawn WaldonValgrind points out error in vtkSocketCommunicatorThis was found running the pvcs.HistogramSelection test with the server processes running in valgrind. This only appeared on one of the server processes.
```
==5854== Syscall param socketcall.sendto(msg) points to uninitialised byte...This was found running the pvcs.HistogramSelection test with the server processes running in valgrind. This only appeared on one of the server processes.
```
==5854== Syscall param socketcall.sendto(msg) points to uninitialised byte(s)
==5854== at 0x7DEEB7F: send (send.c:26)
==5854== by 0x1C238365: vtkSocket::Send(void const*, int) (vtkSocket.cxx:567)
==5854== by 0x6C674A9: vtkSocketCommunicator::SendTagged(void const*, int, int, int, char const*) (vtkSocketCommunicator.cxx:745)
==5854== by 0x6C62DC0: vtkSocketCommunicator::SendVoidArray(void const*, long long, int, int, int) (vtkSocketCommunicator.cxx:292)
==5854== by 0x564C276: vtkCommunicator::Send(unsigned char const*, long long, int, int) (vtkCommunicator.h:160)
==5854== by 0x566A31A: vtkMultiProcessController::Send(unsigned char const*, long long, int, int) (vtkMultiProcessController.h:1617)
==5854== by 0x65B96E8: vtkPVSessionServer::GatherInformationInternal(unsigned int, char const*, unsigned int, vtkMultiProcessStream&) (vtkPVSessionServer.cxx:625)
==5854== by 0x65B932F: vtkPVSessionServer::OnClientServerMessageRMI(void*, int) (vtkPVSessionServer.cxx:575)
==5854== by 0x65B71BB: (anonymous namespace)::RMICallback(void*, void*, int, int) (vtkPVSessionServer.cxx:56)
==5854== by 0x6C4A4DC: vtkMultiProcessController::ProcessRMI(int, void*, int, int) (vtkMultiProcessController.cxx:768)
==5854== by 0x6C4A058: vtkMultiProcessController::ProcessRMIs(int, int) (vtkMultiProcessController.cxx:717)
==5854== by 0x69952CA: vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) (vtkTCPNetworkAccessManager.cxx:268)
==5854== Address 0x37411921 is 129 bytes inside a block of size 258 alloc'd
==5854== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==5854== by 0x5206427: __gnu_cxx::new_allocator<unsigned char>::allocate(unsigned long, void const*) (new_allocator.h:104)
==5854== by 0x52062F5: __gnu_cxx::__alloc_traits<std::allocator<unsigned char> >::allocate(std::allocator<unsigned char>&, unsigned long) (alloc_traits.h:182)
==5854== by 0x5206109: std::_Vector_base<unsigned char, std::allocator<unsigned char> >::_M_allocate(unsigned long) (stl_vector.h:170)
==5854== by 0x5205BD9: std::vector<unsigned char, std::allocator<unsigned char> >::_M_fill_insert(__gnu_cxx::__normal_iterator<unsigned char*, std::vector<unsigned char, std::allocator<unsigned char> > >, unsigned long, unsigned char const&) (vector.tcc:491)
==5854== by 0x5205857: std::vector<unsigned char, std::allocator<unsigned char> >::insert(__gnu_cxx::__normal_iterator<unsigned char*, std::vector<unsigned char, std::allocator<unsigned char> > >, unsigned long, unsigned char const&) (stl_vector.h:1073)
==5854== by 0x52055FC: std::vector<unsigned char, std::allocator<unsigned char> >::resize(unsigned long, unsigned char) (stl_vector.h:716)
==5854== by 0x11058E8F: vtkClientServerStream::Write(void const*, unsigned long) (vtkClientServerStream.cxx:245)
==5854== by 0x11062065: vtkClientServerStreamInternals::Write(vtkClientServerStream&, void const*, unsigned long) (vtkClientServerStream.cxx:181)
==5854== by 0x11064383: vtkClientServerStream& vtkClientServerStreamOperatorSL<double>(vtkClientServerStream*, double) (vtkClientServerStream.cxx:514)
==5854== by 0x11059E45: vtkClientServerStream::operator<<(double) (vtkClientServerStream.cxx:540)
==5854== by 0x697475B: vtkPVServerInformation::CopyToStream(vtkClientServerStream*) (vtkPVServerInformation.cxx:297)
```
I'm not sure if it is actually a problem or not, but it should eventually be investigated.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16837Allow user to only process subset of timesteps.2017-11-21T16:32:00-05:00W. Alan ScottAllow user to only process subset of timesteps.We need some mechanism to allow users to input and process only a subset of timesteps. An example where this is needed is in the temporal statistics filters. Users may run a simulation that settles down to a steady state, and they want...We need some mechanism to allow users to input and process only a subset of timesteps. An example where this is needed is in the temporal statistics filters. Users may run a simulation that settles down to a steady state, and they want to process the temporal statistics on that.5.2 (SC-16)Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/16835pqScalarValueListPropertyWidget should be displayable whenever DoubleVectorPr...2017-11-21T16:32:00-05:00Cory Quammencory.quammen@kitware.compqScalarValueListPropertyWidget should be displayable whenever DoubleVectorProperty is repeatableCurrently, a repeatable `DoubleVectorProperty` must also have a `DoubleRangeDomain` in order for a `pqScalarValueListPropertyWidget` to be used to represent it. The need for a `DoubleRangeDomain` prevents the `pqScalarValueListPropertyWi...Currently, a repeatable `DoubleVectorProperty` must also have a `DoubleRangeDomain` in order for a `pqScalarValueListPropertyWidget` to be used to represent it. The need for a `DoubleRangeDomain` prevents the `pqScalarValueListPropertyWidget` from being presented in some cases where it is useful.5.2 (SC-16)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16823Cannot build Catalyst examples with Catalyst editions2017-11-21T16:32:00-05:00Utkarsh AyachitCannot build Catalyst examples with Catalyst editionsAttempting to build the Catalyst examples from Paraview/Examples with Catalyst Essentials editions fails.
Examples/Catalyst/CxxOverlappingAMRExample/FEAdaptor.cxx:4:23: fatal error: vtkAMRBox.h: No such file or directory
#inc...Attempting to build the Catalyst examples from Paraview/Examples with Catalyst Essentials editions fails.
Examples/Catalyst/CxxOverlappingAMRExample/FEAdaptor.cxx:4:23: fatal error: vtkAMRBox.h: No such file or directory
#include <vtkAMRBox.h>
^
compilation terminated.
5.2 (SC-16)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/16807Crash when switching with OSPray and OpenGL2 with shadows2017-11-22T15:14:15-05:00Kitware RobotCrash when switching with OSPray and OpenGL2 with shadows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16807). Further discussion may take place here.**
---
ParaView crashes when user switches between OSPRays view and the OpenG...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16807). Further discussion may take place here.**
---
ParaView crashes when user switches between OSPRays view and the OpenGL2 one. The problem appears when turning on/off the shadows.
5.2 (SC-16)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/16787Right click menus fail with volume rendering2017-11-22T15:14:15-05:00Kitware RobotRight click menus fail with volume rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16787). Further discussion may take place here.**
---
Right click menus are failing with volume rendering. You can see this...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16787). Further discussion may take place here.**
---
Right click menus are failing with volume rendering. You can see this with can.
5.1.1, Linux, remote server.
Open can, all vars on, apply.
Paint by GlobalNodeId, Volume.
Right click the can. No menu.5.2 (SC-16)Alvaro SanchezAlvaro Sanchezhttps://gitlab.kitware.com/paraview/paraview/-/issues/167855.1.1 remote server crash2017-11-22T15:14:15-05:00Kitware Robot5.1.1 remote server crash**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16785). Further discussion may take place here.**
---
There is a fairly hard to replicate remote server crash in 5.1.1. To ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16785). Further discussion may take place here.**
---
There is a fairly hard to replicate remote server crash in 5.1.1. To replicate it, try the following:
* 8 remote ranks, 5.1.1 (basically, the release branch), Linux.
* Do stuff (Open disk_our_ref.exo, and clip?)
* Edit/ Reset Session.
* Repeaat until crash.
I have been seeing this for a while, I don't think it is new in 5.1.1.
Here is the ouptut:
```
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Extension: 154 (Uknown extension)
Minor opcode: 4 (Unknown request)
Resource id: 0x4a008ba
ERROR: In /.../5.1.1/ParaView5/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx, line 597
vtkXOpenGLRenderWindow (0x77e1590): GLEW could not be initialized.
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
X Error: GLXBadContext 169
Extension: 152 (Uknown extension)
Minor opcode: 5 (Unknown request)
Resource id: 0x4a00a94
ERROR: In /.../5.1.1/ParaView5/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 363
vtkShaderProgram (0x7a51820): 1: #version 120
2: #ifdef GL_ES
3: #if __VERSION__ == 300
4: #define attribute in
5: #define varying out
6: #endif // 300
7: #else // GL_ES
8: #define highp
9: #define mediump
10: #define lowp
11: #if __VERSION__ == 150
12: #define attribute in
13: #define varying out
14: #endif
15: #endif // GL_ES
16:
17:
18: /*=========================================================================
19:
20: Program: Visualization Toolkit
21: Module: vtkPolyDataVS.glsl
22:
23: Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
24: All rights reserved.
25: See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
26:
27: This software is distributed WITHOUT ANY WARRANTY; without even
28: the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
29: PURPOSE. See the above copyright notice for more information.
30:
31: =========================================================================*/
32:
33: attribute vec4 vertexMC;
34:
35: // frag position in VC
36: //VTK::PositionVC::Dec
37:
38: // optional normal declaration
39: //VTK::Normal::Dec
40:
41: // extra lighting parameters
42: //VTK::Light::Dec
43:
44: // Texture coordinates
45: //VTK::TCoord::Dec
46:
47: // material property values
48: //VTK::Color::Dec
49:
50: // clipping plane vars
51: //VTK::Clip::Dec
52:
53: // camera and actor matrix values
54: uniform mat4 MCDCMatrix;
55:
56: // Apple Bug
57: //VTK::PrimID::Dec
58:
59: void main()
60: {
61: //VTK::Color::Impl
62:
63: //VTK::Normal::Impl
64:
65: //VTK::TCoord::Impl
66:
67: //VTK::Clip::Impl
68:
69: //VTK::PrimID::Impl
70:
71: gl_Position = MCDCMatrix * vertexMC;
72:
73:
74: //VTK::Light::Impl
75: }
76:
ERROR: In /.../ParaView5/VTK/Rendering/OpenGL2/vtkShaderProgram.cxx, line 364
vtkShaderProgram (0x7a51820):
Segmentation fault (core dumped)
```
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16779selecting numerous points, extracting, writing remote server hangs2017-11-22T15:14:16-05:00Kitware Robotselecting numerous points, extracting, writing remote server hangs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16779). Further discussion may take place here.**
---
There is a ... what ... freeze? that occurs in ParaView when remote se...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16779). Further discussion may take place here.**
---
There is a ... what ... freeze? that occurs in ParaView when remote server, selecting numerous points, extracting these points, and trying to write these points out to a .csv file. Here is how to replicate.
* Linux, 5.0.1, remote server (I have 8 ranks).
* Open can.exo. All vars on. Apply.
* Select 3 points on the can. (I used Interactive Select Points On).
* Extract Selection.
* File/ Save Data/ .CSV/ All timesteps/ Go.
ParaView doesn't exactly crash, but it freezes and never comes back.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16775Ruler doesn't stay visible!2017-11-22T15:14:16-05:00Kitware RobotRuler doesn't stay visible!**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16775). Further discussion may take place here.**
---
The ruler doesn't stay visible as you change selected filters in the p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16775). Further discussion may take place here.**
---
The ruler doesn't stay visible as you change selected filters in the pipeline browser. This needs to be fixed.
I should give an example.
* can.exo. Apply.
* Sources/ Ruler. Apply.
* Now, select the can.
Ruler goes away. It needs to remain visible.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16766"?" on Properties panel does not work2017-11-22T15:14:16-05:00Kitware Robot"?" on Properties panel does not work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16766). Further discussion may take place here.**
---
With 5.1, hitting the "?" on the Properties panel for a source, or filter ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16766). Further discussion may take place here.**
---
With 5.1, hitting the "?" on the Properties panel for a source, or filter doesn't seem to work.
+ Create Sphere
+ Click on the "?". You expect to see docs for the Sphere. I, instead, get nothing.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16759Add ability for NAN colors to have opacity2017-11-22T15:14:16-05:00Kitware RobotAdd ability for NAN colors to have opacity**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16759). Further discussion may take place here.**
---
Please add the ability for anything that has a color mapping of NAN to als...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16759). Further discussion may take place here.**
---
Please add the ability for anything that has a color mapping of NAN to also have an opacity, and for this opacity to be able to be set to 0 (transparent).5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16758Fix 2d plots labels for one cell2017-11-22T15:14:16-05:00Kitware RobotFix 2d plots labels for one cell**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16758). Further discussion may take place here.**
---
The majority of the time, a user will want to plot data from one cell over...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16758). Further discussion may take place here.**
---
The majority of the time, a user will want to plot data from one cell over time. Further, these plots should be presentation quality. Thus, the labels need to be smart enough that they don't show average or mean in the label. For instance, do the following:
* 5.0.1, local server, Linux.
* Open can.exo. All vars on. Apply.
* Select a cell.
* Plot selection over time.
Now, look at the legend. It says the following:
>> med EQPS (Block 3: Cell Statistics)
>> avg EQPS (Block 3: Cell Statistics)
There is no medium or average needed for one cell! Further, don't put out the Block number of Cell Statistics!!
I want the line to say:
EQPS.
For multiple cells, why even say Block number or Statistics? Unless there is a good reason, remove it. Mean says all you need to say.
Further, turn off Median by default. You only need one, and make it Mean.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16747time marker broken for plot selection over time2017-11-22T15:14:16-05:00Kitware Robottime marker broken for plot selection over time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16747). Further discussion may take place here.**
---
The time marker is broken for plot selection over time. This is new in 5....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16747). Further discussion may take place here.**
---
The time marker is broken for plot selection over time. This is new in 5.0.1, it worked correctly in 4.4.0. Here is how to replicate:
* 5.0.1, local server, Linux.
* Open can.exo. All vars on. Apply.
* Move forward two timesteps.
* Select a point.
* Plot selection over time. Apply.
<<Bug>> - You will not see the time line. The reason is that it now goes from -100 to 100, and the data is too large and/or doesn't include the -100 to 100 range.
Now, lets make the 2d data have less Y axis extend.
* Unselect all variables in the Plot Selection Over Time filter.
* Select VEL(1).
Line shows up, but really short.
* Select VEL (Magnitude).
Now you can really see what is going on.
* Unselect VEL (1)
Line is no longer visible.
5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16743Add name and location of state file2017-11-22T15:14:16-05:00Kitware RobotAdd name and location of state file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16743). Further discussion may take place here.**
---
Assuming a user has loaded a state file, please add the name and location ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16743). Further discussion may take place here.**
---
Assuming a user has loaded a state file, please add the name and location of the state file to the Information tab. It can become confusing which state file was loaded.5.2 (SC-16)