ParaView 3 Telecon 03-20-2008
| Item | People | Description |
|---|---|---|
| 1 | Chart Task Force | VTK/ParaView Charts |
| 2 | Shead | GUI Plugins |
| 3 | All | ParaView 3.4 Deliverables |
| 4 | Karelitz | MARS issues |
| 5 | Karelitz | V&V Milestone |
| 6 | Scott | Multiblock use cases |
| 7 | Geveci | Ideas about testing |
VTK/ParaView Charts
Been working on selection this past week. Had to make whole selection model, yada, yada. Can select some series on line chart. Some issues with making it more easily picked. Need to add point selection.
Pan and zoom now working.
GUI Plugins
After charts.
Deliverables
Multiblock (Utkarsh, Berk, ETI)
Spreadsheet view selections should work. Can select cells and points in multiblock. Not yet able to select entire block. Working on labels in multiblock.
Next working on an extract filter that extracts a block.
Pat is working on a filter to append everything to be able to volume render multi block.
Exodus reader is for the most part working. There are some deadlocks in some tests.
SILO Reader (Pat)
Reader is in ParaView. There is a CMake variable to link to the SILO library. Pat waiting for feedback.
Selection (Berk, Utkarsh)
See multiblock. Not going to get to performance performance.
ParaView/Titan Chart Merger (Jeff, Utkarsh, Philippe, ETI)
See above.
Volume Rendering Algorithm Chooser (Pat)
Pat has started.
Plot multiple points/cells over time (Berk)
After multiblock and selection work.
In queue.
Textures (Utkarsh)
Done unless there is time to implement assigning any array to texture coordinates.
2D Image View type (Utkarsh)
Nothing new.
Box and Sphere Widgets (Will)
Will said he is working on it. Should be working before the release.
Custom filter cleanup (Utkarsh)
Done unless we have time left over.
MARS Issues
Now have a new thing to do. Involves extracting surfaces and writing files like stl.
Stl writer should come next week. Right now, Lisa is outputing vtp files and using a script to convert to stl. It works OK, except that Cubit is crashing on this input. More specifically, it crashes after the data load but during the meshing of the surface.
V&V Milestone
There is a new filter called CTH Fragment Connect that has some bugs that works, in limited contexts, to track data on some sample data.
Multiblock Use Cases
Alan Scott has user that works on heat issues of cars. He has the following main use case.
- Input file format - Exodus files.
- Primary block selection use case - He will read in all of the data for the whole car, and then select a subset of the blocks, representing what he is interested in.
- Notice that as blocks are turned on and off, they will retain their previous "state". For instance, if a block is being colored by temperature, and it is de-selected, then re-selected, it is still coloring by temperature.
- He would like to be able to select groups of blocks as follows:
- Select All
- Select None
- <CTRL>-click select blocks or any other reasonable way of selecting multiple blocks. Used to select engine hoses that are out of order (blocks 10, 20, 30).
- <SHFT>-click select blocks or any other way to turn on a group of blocks with one click. Used to turn on all blocks of the car engine (blocks 110-350)..
- Invert selection. Useful for setting all blocks of the engine to temperature, then all other blocks of the car to grey.
- Visible. This turns on blocks for everything that is visible, even if it is off the screen. Example: Rubber band surface select a hose. Make only that cell visible. Make all blocks visible that are selected, giving you the hose.
- Invisible. Opposite of above. Make the hose invisible.
- Showing. This turns on blocks for anything that is actually displaying in the viewport (window). Everything else visible, but not showing in the viewport, is turned off. Used if you zoom in on the alternator and want to remove everything else.
- Rubber band select, only select blocks that have all cells inside of the rubber band. Useful for the alternator.
- Rubber band select, select blocks that have any cells inside of the rubber band. Useful for the gas line to the fuel tank.
- He would like to be able to color by one block type, then color by another block type. For instance, color all parts in the car by material type, such as steel, aluminum, plastic, etc. Then, color the engine by temperature. Display both. Another example would be color all car parts grey (for context), but color the engine by temperature.
- He would like to be able to turn on multiple blocks, for instance 50 blocks that make up the engine. Then, he would like to group these blocks together with a name - "Engine". He would like to use this superblock as he does any other block further down the pipeline.
After some talking about this, it sounds like a good first step is to have a different type of extract block filter that will allow the user to partition the blocks and have multiple outputs, one for each block. That way, you could apply separate viewing parameters on each (including visibility) as well as attach further processing on each partition.
Ideas about testing
Did not get to.
