ParaView 3 Telecon 09/11/2007: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
(New page: {| cellpadding="2" cellspacing="4" |- ! style="background:#abcdef" | Item ! style="background:#abcdef" | People ! style="background:#abcdef" | Description |- | 1 || Moreland || Change meet...) |
No edit summary |
||
| Line 9: | Line 9: | ||
| 2 || Moreland || Range information in Exodus Panel | | 2 || Moreland || Range information in Exodus Panel | ||
|- | |- | ||
| 3 || All || Open ParaView 3.2 Bugs | | 3 || Moreland || Adding extension on state files | ||
|- | |||
| 4 || All || Open ParaView 3.2 Bugs | |||
|} | |} | ||
Revision as of 10:41, 11 September 2007
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Change meeting day |
| 2 | Moreland | Range information in Exodus Panel |
| 3 | Moreland | Adding extension on state files |
| 4 | All | Open ParaView 3.2 Bugs |
Range information in Exodus Panel
Ken suggests getting rid of the column in the variable list in the exodus panel. The reasons are:
- This information is just a duplicate of what is in the information panel.
- I have not checked recently, but there have certainly been bugs where the data was out-of-date (i.e. gave the wrong range for the current timestep).
- It is confusing for users to have "Unavailable" next to all the variables when they first start up. I am just responding to a user who was so confused by this he thought ParaView could not read in Exodus variables.
