MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012383ParaView(No Category)public2011-07-20 10:552016-08-12 09:58
ReporterGeorge Zagaris 
Assigned ToGeorge Zagaris 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
ProjectAMR Streaming
Topic Name
Typeusability
Summary0012383: Caching of AMR blocks (geometry+data) on AMR reader
DescriptionThe demand-driven AMR infrastructure, implemented in vtkAMRBaseReader, supports upstream requests from the pipeline that specify which blocks are to be loaded.
However, when the user performs actions within the paraview user-interface that can trigger multiple such requests, it can lead to an overwhelming amount of I/O for multiple requests of the same data. One solution to minimize the I/O and avoid reading data that has already been read is to cache AMR blocks in a separate data-structure, e.g., a vtkAMRDataSetCache, that will be an ivar of the vtkAMRBaseReader.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-07-20 10:55George ZagarisNew Issue
2011-07-20 10:55George ZagarisAssigned To => George Zagaris
2011-07-20 10:56George ZagarisStatusbacklog => todo
2011-07-20 10:56George ZagarisStatustodo => active development
2011-10-14 11:50George ZagarisNote Added: 0027575
2011-10-14 11:50George ZagarisStatusactive development => todo
2013-03-04 10:19Utkarsh AyachitStatustodo => backlog
2016-08-12 09:58Kitware RobotNote Added: 0038011
2016-08-12 09:58Kitware RobotStatusbacklog => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved

Notes
(0027575)
George Zagaris   
2011-10-14 11:50   
This is done for Enzo and Flash. Needs more testing and cleanup so I am pushing this back in todo for now.
(0038011)
Kitware Robot   
2016-08-12 09:58   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.