| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0008697 | ParaView | (No Category) | public | 2009-03-06 19:51 | 2009-05-13 13:46 | ||||
| Reporter | Alan Scott | ||||||||
| Assigned To | Ken Moreland | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 3.6 | Fixed in Version | |||||||
| Summary | 0008697: (Venus) Max time is confused when opening multiple datasets. | ||||||||
| Description | Is this a bug, or just an artifact of handling restart files? can.exo has 43 time steps in it. z_pinch1.exo.8.* has 10 time steps in it. ParaView trunk, XP, local server. Open can.exo. Apply. Go to the last time step. Open z_pinch1.exo.8.*. Apply. Bug 1 - Why does ParaView show that there are now 53 time steps? Step back a few frames. Bug 2 - Notice that the can is just moving as a unit - the whole thing is not animating correctly. Only highlight z_pinch1. go to time 0. Display DISPL. Animate. Note that it animates beyond 10. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0015595) Alan Scott (manager) 2009-03-06 19:57 |
Would it be possible to have a user selectable option to keep time independently for multiple datasets, or let them stay dependent as required for restart files? |
|
(0015603) Ken Moreland (manager) 2009-03-09 11:04 |
These are not bugs. They are just artifacts from doing something completely ridiculous like opening up two completely independent data sets with two totally separate time scales. ParaView is animating by simulation time, which is the right thing to do. Not a bug 1 - ParaView is actually showing 54 time steps indexed 0 - 53. can has 44 time steps. z_pinch has 11 time steps. Both data sets report data at time 0, so these two time steps are resolved into one. 44 + 11 - 1 = 54. Not a bug 2 - The can time scale goes to 4e-3 seconds. The z_pinch1 time scale goes to 3e-9 seconds. By the time the can gets to its second time step, z_pinch1 is past its last time step. It is totally correct in the last times steps for can to be changing and z_pinch1 to not change. It is also correct at the beginning time steps for z_pinch1 to change and can1 to not change (which is what happens). |
|
(0015612) Alan Scott (manager) 2009-03-09 16:11 |
I agree with Ken, lets close this one. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-03-06 19:51 | Alan Scott | New Issue | |
| 2009-03-06 19:57 | Alan Scott | Note Added: 0015595 | |
| 2009-03-09 11:04 | Ken Moreland | Note Added: 0015603 | |
| 2009-03-09 11:04 | Ken Moreland | Status | backlog => @80@ |
| 2009-03-09 11:04 | Ken Moreland | Resolution | open => won't fix |
| 2009-03-09 11:04 | Ken Moreland | Assigned To | => Ken Moreland |
| 2009-03-09 16:11 | Alan Scott | Note Added: 0015612 | |
| 2009-03-09 16:11 | Alan Scott | Status | @80@ => closed |
| 2009-05-13 13:46 | Utkarsh Ayachit | Target Version | => 3.6 |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |