| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0003734 | ParaView | (No Category) | public | 2006-09-08 12:27 | 2007-10-18 13:29 | ||||
| Reporter | Timothy Shead | ||||||||
| Assigned To | Ken Moreland | ||||||||
| Priority | high | Severity | feature | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0003734: "Meta" reader for exodus restart files | ||||||||
| Description | Managing multiple restart files from a simulation is currently a pain - in general, each restart file will contain timesteps that "overlap" with the previous file. Loading multiple files, duplicating pipelines, and managing the overlapping timesteps is extremely time-consuming. We would like to explore options for improving this. Consolidating restart files into a single file without overlapping timesteps is the technically easy solution, but it may not be practical to have a duplicate of a massive dataset. We propose a "meta" reader that would act as an abstraction for a collection of restart files. The meta reader allow the user to setup a single pipeline and view their data as a single contiguous set of timesteps, but would have multiple inputs from exodus readers, one-per-restart file. The meta reader would then handle the details of reading the correct timestep from the correct input reader in response to user input. Ideally, the meta reader could be used with any type of reader that supports timesteps, not just exodus. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0005489) Timothy Shead (reporter) 2006-10-20 17:45 |
Sleezing my way out of this :) |
|
(0006419) Ken Moreland (manager) 2007-02-14 16:43 |
With the new pipeline-based time support in ParaView 3, this bug now becomes much easier to implement. |
|
(0007488) Ken Moreland (manager) 2007-04-26 12:53 |
Here is my current plan for implementing this. Modify the exodus reader to, by default, output an empty data set when it gets a request for a time value outside of the time range it is defined on. There will be an option to disable this behavior. With this behavior on, the user can simply load the multiple restarts using the typical Exodus reader, hit play, and the animation will always show the output from the file with the data defined. There are two problems with this. First, having multiple readers is a pain when trying to synchronize viewing parameters or applying filters. Second, dumps from restarts commonly have temporal overlaps. We can solve both of these problems with a temporal multiplexer filter that takes as input all of the readers and outputs only the one for which the time range is valid. |
|
(0009514) Berk Geveci (administrator) 2007-10-18 13:28 |
This is captured in another bug (search for multiplexer). |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2007-08-13 15:07 | Berk Geveci | Priority | normal => high |
| 2007-08-23 17:10 | Berk Geveci | Category | => 3.2 |
| 2007-10-18 13:28 | Berk Geveci | Note Added: 0009514 | |
| 2007-10-18 13:29 | Berk Geveci | Status | tabled => closed |
| 2007-10-18 13:29 | Berk Geveci | Resolution | open => fixed |
| 2011-06-16 13:10 | Zack Galbreath | Category | => (No Category) |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |