View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0007362 | ParaView | (No Category) | public | 2008-07-18 06:19 | 2009-05-13 13:46 | ||||
Reporter | John Biddiscombe | ||||||||
Assigned To | Utkarsh Ayachit | ||||||||
Priority | low | Severity | major | Reproducibility | N/A | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | 3.6 | Fixed in Version | |||||||
Summary | 0007362: Time modes not useful | ||||||||
Description | The fact that the time keeper/manager uses all time steps available makes it useless. When a filter modifies the output time from N steps to N/2 steps (or other), the snap to time steps feature is useless as the time values for the intermediate steps are invalid for that filter. This causes execution problems as it is triggered repeatedly with duff values A Time mode "Snap To Filter TimeSteps" which only iterates over the output steps for the selected filter/source (a drop down combo would be good) is needed. Usingf sequence mode is one way aropund it, but only if the output has regualr steps. With filkters producing log time, it's hard. TemporalSnapToTimeSteps can be used to snap to the steps wanted, but other filters still get the crap values. A new Time mode is the only solution I can see being useful | ||||||||
Tags | No tags attached. | ||||||||
Project | |||||||||
Topic Name | |||||||||
Type | |||||||||
Attached Files | |||||||||
Relationships | ||||||
|
Relationships |
Notes | |
(0015432) Utkarsh Ayachit (administrator) 2009-02-26 15:14 |
Now the context menu on the pipeline browser has a new checkbox "Ignore Time". If checked, the source will no longer be considered when determining the timesteps or timeranges for the animation. Whenever a temporal filter i.e. a filter with "TimestepValues" property is created, its input is automatically updated to "ignore time" so that the inputs time will not be considered in the animation (unless of course the user forces it). This may be a more acceptable solution than creating a new play mode (as suggedsted by BUG 0007362) or using timesteps from visible objects (as suggested by BUG 0007799). /cvsroot/ParaView3/ParaView3/Applications/OverView/Core/MainWindow.cxx,v <-- Applications/OverView/Core/MainWindow.cxx new revision: 1.2; previous revision: 1.1 /cvsroot/ParaView3/ParaView3/Qt/Components/pqClientMainWindow.cxx,v <-- Qt/Components/pqClientMainWindow.cxx new revision: 1.5; previous revision: 1.4 /cvsroot/ParaView3/ParaView3/Qt/Components/pqMainWindowCore.cxx,v <-- Qt/Components/pqMainWindowCore.cxx new revision: 1.307; previous revision: 1.306 /cvsroot/ParaView3/ParaView3/Qt/Components/pqMainWindowCore.h,v <-- Qt/Components/pqMainWindowCore.h new revision: 1.101; previous revision: 1.100 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPipelineBrowserContextMenu.cxx,v <-- Qt/Components/pqPipelineBrowserContextMenu.cxx new revision: 1.20; previous revision: 1.19 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPipelineBrowserContextMenu.h,v <-- Qt/Components/pqPipelineBrowserContextMenu.h new revision: 1.8; previous revision: 1.7 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPipelineMenu.cxx,v <-- Qt/Components/pqPipelineMenu.cxx new revision: 1.7; previous revision: 1.6 /cvsroot/ParaView3/ParaView3/Qt/Components/pqPipelineMenu.h,v <-- Qt/Components/pqPipelineMenu.h new revision: 1.7; previous revision: 1.6 /cvsroot/ParaView3/ParaView3/Qt/Components/Resources/UI/pqClientMainWindow.ui,v <-- Qt/Components/Resources/UI/pqClientMainWindow.ui new revision: 1.2; previous revision: 1.1 /cvsroot/ParaView3/ParaView3/Qt/Core/pqPendingDisplayManager.cxx,v <-- Qt/Core/pqPendingDisplayManager.cxx new revision: 1.28; previous revision: 1.27 /cvsroot/ParaView3/ParaView3/Qt/Core/pqPipelineFilter.cxx,v <-- Qt/Core/pqPipelineFilter.cxx new revision: 1.10; previous revision: 1.9 /cvsroot/ParaView3/ParaView3/Qt/Core/pqPipelineFilter.h,v <-- Qt/Core/pqPipelineFilter.h new revision: 1.8; previous revision: 1.7 /cvsroot/ParaView3/ParaView3/Qt/Core/pqTimeKeeper.cxx,v <-- Qt/Core/pqTimeKeeper.cxx new revision: 1.18; previous revision: 1.17 /cvsroot/ParaView3/ParaView3/Qt/Core/pqTimeKeeper.h,v <-- Qt/Core/pqTimeKeeper.h new revision: 1.11; previous revision: 1.10 |
(0015621) Alan Scott (manager) 2009-03-10 16:23 |
Tested as per bug number 7799. Tested client/remote server. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2008-07-18 06:19 | John Biddiscombe | New Issue | |
2008-10-14 02:24 | John Biddiscombe | Relationship added | parent of 0007799 |
2009-02-18 09:19 | Utkarsh Ayachit | Category | Development => Pending |
2009-02-20 11:19 | Ken Moreland | Assigned To | => Utkarsh Ayachit |
2009-02-20 11:20 | Ken Moreland | Priority | normal => low |
2009-02-20 11:20 | Ken Moreland | Status | backlog => tabled |
2009-02-20 11:20 | Ken Moreland | Category | Pending => 3.6 |
2009-02-26 15:14 | Utkarsh Ayachit | Note Added: 0015432 | |
2009-02-26 15:14 | Utkarsh Ayachit | Status | tabled => @80@ |
2009-02-26 15:14 | Utkarsh Ayachit | Resolution | open => fixed |
2009-03-10 16:23 | Alan Scott | Note Added: 0015621 | |
2009-03-10 16:23 | 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 |