ParaView 3 Telecon 12-02-2010
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Project Randy |
| 2 | Moreland | SC Tutorial |
| 3 | Greg Weirs | CTH Tracer data |
| 4 | Mauldin | Visit bridge/data files |
| 5 | Pebay | Statistics package |
| 6 | Mauldin, Weirs | Prism |
| 7 | Geveci | ParaView + ADIOS |
| 8 | Scott | ParaView 3.8.1 Release |
| 9 | Moreland | Documenting Plugins |
| 10 | Moreland | Warning when ProcessRequests modifies itself |
| 11 | Moreland | Book omissions and errata |
| 12 | Utkarsh | Transition to git |
| 13 | Moreland | Stronger Dashboard
|
Project Randy
Today:
Ken has been emailing an abstrct(?) around. Help, support needed?
Call to everyone: a list of features to put in a comparative matrix between ParaView Coprocessing and other solutions.
Nathan: in situ on which multicores?
Getting on to Cielito or Cielo?
Alan: zia app stuff done?
Any related meetings at supercomputing?
Need good I/O comparisons between solver output and coprocessing output.
Can we distribute PHASTA with coprocessing adapter?
Previously:
turn into more of a kitware/sandia project with roadmap
Supercomputing Tutorial
Today: any report?
Previously:
We got permission to distribute PHASTA as an example for integration. However, the only compelling use cases use a commercial solver. There is some completely open solver, but it has no real compelling use case.
oakridge booth--jaguar, adios, staging, paraview
CTH tracer data
VISIT bridge/data files
Statistics Package
select data filter complext filter interface
PRISM
ParaView + ADIOS
Today:
Previously:
modifying reader so that it can suck data through staging? jaguar issues? oakridge booth? demo at supercomputing?
adios is in mainstream paraview--young project
ParaView 3.8.1 Release
Today any machines with problems?
Documenting Plugins
The new rule should be that if a plugin is distributed with the ParaView binaries, it must have a wiki page documenting it. These wiki pages will then be integerated in the new ParaView electronic book.
Warning when ProcessRequest modifies itself
Previously:
A while ago we talked about adding a check to the executive that issues a warning if it detects that its MTime changes during a call to ProcessRequest. Whatever happened to that? I just spent 2 days tracking down a parallel pipeline update problem that would have been quickly alerted had this been in place (and was easily fixed once I put my own check in place).
Berk suggested first adding the check only to ParaView. We will see how that works, and then possibly move to VTK. Kitware will take care of that.
On Berk's todo list. Berk is working on proposals for the ARB. One is to change the modularization of VTK. The other is to yank out VTK 4.0 compatibility, which will allow us to clean up vtkExecutive change.
Book omissions and errata
Previously:
Lisa is going to create a bug-tracker like functionality for the Kitware books.
Transition to git
Previously:
Branchy workflow. Tie in to stronger dashboard.
