| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0011401 | ParaView | Feature | public | 2010-11-04 15:45 | 2016-08-12 09:58 | ||||
| Reporter | David Thompson (old) | ||||||||
| Assigned To | Kitware Robot | ||||||||
| Priority | normal | Severity | major | Reproducibility | N/A | ||||
| Status | closed | Resolution | moved | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0011401: ParaView should retain common dataset/array information on its own | ||||||||
| Description | Many file formats are problematic in that they don't include metadata on arrays such as extrema (at one time step or over all time steps), vector magnitude ranges, etc. This results in ParaView spending a lot of time re-running filters that iterate over the data many times in order to obtain this information or avoiding the presentation of this information altogether. ParaView should keep track of this information itself rather than recompute it. | ||||||||
| Additional Information | One implementation option would be to create an SQLite database and store hashes as keys into array metadata. The hashes might be of * the server URL + a full file path + the modification time of the file; or * the SHA1 checksum of the file. The metadata might include just extremal values for each array (at each timestep) that has been visited or it might include: the mean, variance, skewness, and kurtosis; or enough quartiles for a CDF sparkline; or even information about interactions between arrays such as which ones are independent of each other or have strong associations. Furthermore, if a background thread could be run on a file to collect this information once the data is loaded and populate the database, it would allow the information tab in the object inspector to be much more useful and interactive; each time the inspector is made visible, it could check the database for information on the arrays in question and add display widgets when information was present. If this background process also computed SHA1 checksums of raw vtk*Array data, this kind of information could be displayed not just for files but also for the output of downstream filters. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0037894) Kitware Robot (administrator) 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. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2010-11-04 15:45 | David Thompson (old) | New Issue | |
| 2011-06-16 13:10 | Zack Galbreath | Category | Feature Request => Feature |
| 2016-08-12 09:58 | Kitware Robot | Note Added: 0037894 | |
| 2016-08-12 09:58 | Kitware Robot | Status | expired => closed |
| 2016-08-12 09:58 | Kitware Robot | Resolution | open => moved |
| 2016-08-12 09:58 | Kitware Robot | Assigned To | => Kitware Robot |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |