ParaView 3 Telecon 02-19-2009

From ParaQ Wiki
Revision as of 13:40, 19 February 2009 by Kmorel (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
Item People Description
1 Ice MARS/V&V Milestone issues
2 Moreland ParaView 3.6 Deliverables

MARS

No MARS personnel here.

Kitware Summit?

We are considering having a Kitware summit the first full week of April.

Deliverables

ParaView/Titan Chart Merger (Pat/Utkarsh)

Adding in context menus so that they work like the old ones. Also adding several of Dave Thompson's request.

Simplified Scripting (Berk/Utkarsh)

Moving forward. Most of the things left over require server manager changes.

Have done a documentation pass. The help command gives better information.

Plots Along Curves (Berk)

Not started

VisIt AVT Integration (Burlen)

It works up to the material interface reconstruction. Have to dig a bit in VisIt source code to see how it should be done. Got a custom panel working.

Still struggling with build. Got it working on Linux. Need to get it working on Windows and Mac.

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.)