| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0009786 | ParaView | Bug | public | 2009-10-27 18:27 | 2009-12-02 20:29 | ||||
| Reporter | Alan Scott | ||||||||
| Assigned To | Ken Moreland | ||||||||
| Priority | high | Severity | major | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 3.8 | Fixed in Version | |||||||
| Summary | 0009786: ex-timeseries doesn't work for sierra code output | ||||||||
| Description | I have a user that is trying to read multiple exodus files as time series. In other words, file 0 is time 0, file 1 is time 1. He is using the ex-timeseries reader. I have replicated at least the first layer of bugs using can, writing out numerous exodus files. I am attaching two directories to this bug, both which are wrong. The normal way that the Sierra codes write time partitioned files is as follows: can.e can.e-s0002 can.e-s0003 * Directory work1 dies when you try to read the .ex-timeseries file. It says it is looking for file s0000. * Directory work2 reads in all files at the same time, and displays them on top of each other. The goal is to be able to step from one time step to another. If this is a ParaView problem, it needs to be fixed - if this is user error, please let me know. This needs to be fixed for 3.8. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | |||||||||
| Topic Name | |||||||||
| Type | |||||||||
| Attached Files |  work.zip [^] (3,481,102 bytes) 2009-10-27 18:27 | ||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0018343) Ken Moreland (manager) 2009-11-04 13:06 |
The previous implementation assumed that the convention for restart numbers was "<name>.e-s.<rs#>" (note the "." before the restart number). These files have no "." before the number. Now also supports "<name>.e-s<rs#>". The files can now be read directly as a time series as well. For example, you can load can.e directly and ParaView will find the rest of the files and load them as a time series. Making the .ex-timeseries for file is unnecessary (assuming the timeseries follows this naming convention). Note however, that the examples attached to this bug do not load totally correctly because the files have invalid time steps. All time steps are marked as 0, so ParaView combines them all into the same time step. /cvsroot/ParaView3/ParaView3/VTK/Hybrid/vtkPExodusIIReader.cxx,v <-- vtkPExodusIIReader.cxx new revision: 1.36; previous revision: 1.35 |
|
(0018679) Alan Scott (manager) 2009-12-02 20:29 |
I am pretty sure this is fixed. If not, I will open a new bug. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2009-10-27 18:27 | Alan Scott | New Issue | |
| 2009-10-27 18:27 | Alan Scott | File Added: work.zip | |
| 2009-10-29 13:56 | Ken Moreland | Status | backlog => tabled |
| 2009-10-29 13:56 | Ken Moreland | Assigned To | => Ken Moreland |
| 2009-11-04 12:38 | Ken Moreland | Target Version | => 3.8 |
| 2009-11-04 13:06 | Ken Moreland | Note Added: 0018343 | |
| 2009-11-04 13:06 | Ken Moreland | Status | tabled => @80@ |
| 2009-11-04 13:06 | Ken Moreland | Resolution | open => fixed |
| 2009-12-02 20:29 | Alan Scott | Note Added: 0018679 | |
| 2009-12-02 20:29 | Alan Scott | Status | @80@ => closed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |