MantisBT - ParaView |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0012126 | ParaView | Bug | public | 2011-04-27 12:35 | 2011-11-01 22:08 |
|
| Reporter | Greg Weirs | |
| Assigned To | Robert Maynard | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | | OS Version | |
| Product Version | 3.10.1 | |
| Target Version | | Fixed in Version | 3.12 | |
| Project | Sandia |
| Topic Name | more-prism-support |
| Type | incorrect functionality |
|
| Summary | 0012126: Prism Slow performance for large SESAME files |
| Description | I loaded a sesame file with 1000x1000 density x temperature points and the interactive response was much slower. In addition, it seems each frame in a time series was slow; does this mean that the sesame file is being reread at each time? SESAME files do not have time, so it would be better to read it just once. |
| Steps To Reproduce | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2011-04-27 12:35 | Greg Weirs | New Issue | |
| 2011-04-28 13:44 | Robert Maynard | Assigned To | => Robert Maynard |
| 2011-04-28 13:44 | Robert Maynard | Status | backlog => tabled |
| 2011-06-07 15:06 | Robert Maynard | Note Added: 0026742 | |
| 2011-06-07 15:06 | Robert Maynard | Status | tabled => @20@ |
| 2011-06-23 16:24 | Robert Maynard | Status | backlog => todo |
| 2011-06-23 16:24 | Robert Maynard | Status | todo => active development |
| 2011-06-23 16:27 | Robert Maynard | Note Deleted: 0026742 | |
| 2011-06-23 16:29 | Robert Maynard | Note Added: 0026885 | |
| 2011-06-28 21:51 | Alan Scott | Project | => Sandia |
| 2011-06-28 21:51 | Alan Scott | Type | => incorrect functionality |
| 2011-07-19 17:19 | Robert Maynard | Topic Name | => more-prism-support |
| 2011-07-19 17:22 | Robert Maynard | Status | active development => gatekeeper review |
| 2011-07-19 17:22 | Robert Maynard | Resolution | open => fixed |
| 2011-07-21 19:18 | Utkarsh Ayachit | Note Added: 0027049 | |
| 2011-07-22 14:13 | Utkarsh Ayachit | Status | gatekeeper review => customer review |
| 2011-07-22 14:13 | Utkarsh Ayachit | Note Added: 0027065 | |
| 2011-07-29 16:18 | Utkarsh Ayachit | Fixed in Version | => 3.12 |
| 2011-11-01 22:08 | Alan Scott | Note Added: 0027645 | |
| 2011-11-01 22:08 | Alan Scott | Status | customer review => closed |
|
Notes |
|
|
(0026885)
|
|
Robert Maynard
|
|
2011-06-23 16:29
|
|
|
I have fixed this locally, just waiting for ParaView's workflow to stabilize and it will be pushed. |
|
|
|
(0027049)
|
|
Utkarsh Ayachit
|
|
2011-07-21 19:18
|
|
|
Scheduled for gatekeeper review on Jul 22, 2011 at 2 pm EDT. |
|
|
|
(0027065)
|
|
Utkarsh Ayachit
|
|
2011-07-22 14:13
|
|
|
|
|
(0027645)
|
|
Alan Scott
|
|
2011-11-01 22:08
|
|
|
I believe this is fixed. If necessary, please reopen. |
|