View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0012466 | ParaView | (No Category) | public | 2011-08-03 13:36 | 2014-08-29 10:59 | ||||
Reporter | Alan Scott | ||||||||
Assigned To | Utkarsh Ayachit | ||||||||
Priority | high | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 3.12 | ||||||||
Target Version | 4.2 | Fixed in Version | 4.2 | ||||||
Summary | 0012466: Plot over line should have an option to rescale every timestep | ||||||||
Description | Plot over line should have an option to rescale every timestep Windows, 3.10.1, local server. Open Can.exo. Filters/ Data Analysis/ Plot over line. Play. - feature request - note that the 2d plot does not rescale. That's generally good, but there should also be an option to have it rescale every timestep. | ||||||||
Tags | No tags attached. | ||||||||
Project | Sandia | ||||||||
Topic Name | |||||||||
Type | feature | ||||||||
Attached Files | |||||||||
Relationships | ||||||||||||||||
|
Relationships |
Notes | |
(0027307) Ken Moreland (manager) 2011-08-08 15:48 |
I completely disagree. The 2d plot should NOT rescale every time step for the same reason the color bar should NOT rescale. Rescaling the axes in the plot obfuscates the temporal trends. I consider the new behavior in 3.10 to be correct and the old behavior in 3.8 to be incorrect. |
(0027370) Alan Scott (manager) 2011-08-16 20:13 |
Hate to say it, but I totally disagree back. :-) You are trying to dictate to users how they can use the tool. I agree that the default should be as you state, but there are cases that a user does want each time step to reset - and they currently accomplish this manually. That is a miserable way to create a movie - screenshot by screenshot. Ask me for a few usecases that I have dreamed up, if you like. This is a good example of the common tug of war - do we (developers/researchers) dictate what users want because we think we know better than they do, or do we listen to users and give them what they want, even if they can misuse it? Users should have the flexibility to do either. |
(0027374) Ken Moreland (manager) 2011-08-17 10:12 |
Actually, I would characterize it differently. Should we developers provide the tools to make crappy visualizations? In general, we grudgingly say yes but by default do the right thing. Your original wording of the description of this bug was to change the permanent behavior to always change the scale for every time step. To this I strenuously, violently object. Your last note said that this behavior should really be an option that is not on by default. Although I believe that your scale resetting user is doing a lot of work to make his/her data obfuscated (we've already bantered significantly about the color scale), I don't have an objection to creating this option. I took the liberty of changing the wording of this issue's summary and description. It is no longer asking to revert the scaling behavior to 3.8 (bad, bad, bad), but asking for an option to switch to it. I think this is a fine compromise. |
(0030139) Utkarsh Ayachit (administrator) 2013-01-15 10:57 edited on: 2013-01-15 12:51 |
To some extent, ParaView already support this. Before you say anything, I admit it's not obvious to the users :), and we can add an option somewhere (probably the View Settings dialog?) for the same, but here's what we have in 3.98.0: * by default, chart view is in an "auto-scale" mode. So if you do the steps exactly as you mentioned, the chart will indeed scale to fit all data. * every time you hit "reset camera" with the chart view active, the view enters this "auto-scale" mode. * as soon as you interact with the view i.e. pan or zoom, the axis ranges that you pick as a consequence of your interaction are treated as "fixed". Now when you animate, they won't change with time. |
(0030142) Alan Scott (manager) 2013-01-15 19:32 |
OK, now I agree with Ken. Even though you (Utkarsh) are correct, both functionality is available, it is not obvious. We should do the following: * Default to not changing the axis' scaling and offset every timestep. * Give users the option to auto-scale every timestep if they desire. Place this in the View Settings Dialog. |
(0033126) Utkarsh Ayachit (administrator) 2014-07-28 22:26 |
Alan, This is the current behavior: On the "Properties" panel, under the view section for the Line Chart View, for example, there are check-boxes for "Left Axis Use Custom Range", "Right Axis Use Custom Range". When not checked, the axes is automatically scaled with the data changes. Thus, it automatically scaled over time too. Now, if user manually interacts with the view this checkbox automatically becomes checked and a "custom axes range" is setup using the axes range setup by the interaction. Now the axes is locked and won't change over time, User can of course, uncheck these "custom range" buttons and the axes will start readjusting again. Does this work as an acceptable solution? |
(0033153) Alan Scott (manager) 2014-07-30 15:00 |
I am closing this bug, since this functionality has been implemented. I added a new bug, asking that when the Axis Use Custom Range button is clicked, min and max would be preloaded with real data from the plot. Tested local server, master, Linux. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2011-08-03 13:36 | Alan Scott | New Issue | |
2011-08-08 15:48 | Ken Moreland | Note Added: 0027307 | |
2011-08-16 20:13 | Alan Scott | Note Added: 0027370 | |
2011-08-17 10:12 | Ken Moreland | Type | incorrect functionality => feature |
2011-08-17 10:12 | Ken Moreland | Note Added: 0027374 | |
2011-08-17 10:12 | Ken Moreland | Summary | Plot over line should rescale ever timestep => Plot over line should have an option to rescale every timestep |
2011-08-17 10:12 | Ken Moreland | Description Updated | |
2012-05-31 10:26 | Utkarsh Ayachit | Status | backlog => todo |
2013-01-15 10:57 | Utkarsh Ayachit | Note Added: 0030139 | |
2013-01-15 12:50 | Utkarsh Ayachit | Note Edited: 0030139 | |
2013-01-15 12:51 | Utkarsh Ayachit | Note Edited: 0030139 | |
2013-01-15 19:32 | Alan Scott | Note Added: 0030142 | |
2013-01-23 21:10 | Utkarsh Ayachit | Relationship added | related to 0013818 |
2014-01-16 17:00 | Utkarsh Ayachit | Target Version | => 4.2 |
2014-07-28 22:22 | Utkarsh Ayachit | Status | todo => gatekeeper review |
2014-07-28 22:22 | Utkarsh Ayachit | Fixed in Version | => git-master |
2014-07-28 22:22 | Utkarsh Ayachit | Resolution | open => fixed |
2014-07-28 22:22 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
2014-07-28 22:26 | Utkarsh Ayachit | Note Added: 0033126 | |
2014-07-28 22:26 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
2014-07-30 13:12 | Utkarsh Ayachit | Relationship added | related to 0014815 |
2014-07-30 14:59 | Alan Scott | Relationship added | related to 0014899 |
2014-07-30 15:00 | Alan Scott | Note Added: 0033153 | |
2014-07-30 15:00 | Alan Scott | Status | customer review => closed |
2014-08-29 10:59 | Utkarsh Ayachit | Fixed in Version | git-master => 4.2 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |