ParaView 3 Telecon 02-12-2009

From ParaQ Wiki
Jump to navigationJump to search
Item People Description
1 Ice MARS/V&V Milestone issues
2 Berk Plugin Testing
3 Moreland ParaView 3.6 Deliverables

MARS

No new issues.

Plugin Testing

If you turn on examples, some plugin testing is done.

Utkarsh will look into adding extensions to pvtest to allow you to specify a plugin.

Deliverables

ParaView/Titan Chart Merger (Pat/Utkarsh)

Starting work on options dialog. After that, start trying it out.

Dave Thompson has list of features he would like to see for the dialog.


Simplified Scripting (Berk/Utkarsh)

Now back to working on the simple module. Got the array selection for coloring working better. Now you just have to specify the name of the array. You no long have to provide point or cell data. More like the GUI now.

Selection of proxy properties with domains is now possible by just setting by the name.

The active view/pipeline object is now synchronized.

Properties of fixed length now return what you think. Input properties can be accessed directly as proxies.

Temporal Cleanup (Berk)

  • Show temporal bounds of all datasets in statistics view (or elsewhere)
  • Show continuous data set temporal bounds in info page
  • Plot/Probe over time, results should very in Sequence, Snap, and Real Time modes

Not started yet. John Biddiscombe has been looking at it.

Plots Along Curves (Berk)

Not started

VisIt AVT Integration (Burlen)

Working to make sure that it works on all platforms (Windows, Linux, Mac). Will then work on integrating it with the ParaView build.

Getting material stuff working.

Working on AMR.

Statistics (Phillipe)

Phillipe is not comfortable with running statistics on point data in parallel because points are replicated, and the replicated data can skew the statistics. As a compromise, we decided to only allow users to run statistics on cell data. Cell data is not replicated. If a user needs statistics on point data, they will have to explicitly convert them to cells, which signals a change in the data.

There is also an issue with accessing vectors in columns of tables. The design really assumes that each components is going to be in its own array. To make matters worse, the current implementation of getting a vtkVariant of a tuple is really slow. In the short term, we will continue to read tuples as vtkVariant. We should also look at that code and make it more efficient. In the long term, we are looking into implementing arrays that have different striding than that currently implemented in the vtkDataArray classes. When that is implemented, we can break up these vectors into separate arrays with shallow copies. (This would probably happen in the data-set-to-table filter.)

Particle Support (Zhanping/John Biddiscombe)

  • Provide a particle representation that renders points more intelligently
    • Spheres with size vs. squares of pixel width
    • Optional sizing based on a scalar
    • Appropriate alpha blending (at least when particles are small)
    • Splatting?
  • Filters for meshless data? (Need to get customer requirements.)
    • Sampling point cloud?
    • Surface extraction?

Not started yet.

Retrieved from "http://www.paraview.org/ParaView/index.php?title=ParaView_3_Telecon_02-12-2009&oldid=6126"