ParaView 3 Telecon 07-01-2009
Item | People | Description |
---|---|---|
1 | Moreland | Project Randy |
2 | Scott | Open fragment analysis |
3 | Moreland | SciDAC & SC Tutorials |
4 | Moreland | Warning when ProcessRequests modifies itself |
5 | Moreland | Book omissions and errata |
6 | Utkarsh | Transition to git |
7 | Moreland | Stronger Dashboard
|
Project Randy
Last week:
Utkarsh recently performed two patches that should effect some performance issues when running pvserver interactive on large numbers of cores. There were apparent issues with the report progress events. One patch fixes an out-and-out problem and the other turns off progress events. Alan will test these on large core counts soon.
Nathan has been having troubles acquiring large jobs to tests his latest coprocessing code. He will work with Alan to reserve some time on a large computer.
This week:
Alan will get some time on Red Sky next week to try Utkarsh's patches. Nathan will also try running during this time.
Berk had a conversation with Randal Hand and is inspired by Alan running interactive up to 5K cores. Randal and Berk had a meeting and now have a plan forward to do the scalability tests themselves.
Pat has runs up to 8K cores. He has plans to run up to 16K (maybe 32K) very soon.
Material Interface Filter
How do we move the filter so that it is open source? We are going to rename the filter. We are going to remove references in comments and such to CTH. Then we will move it into ParaView.
After that, we should find a data set that is not CTH and not weapons related to demonstrate that it is a general purpose filter.
Tutorials
We recently had a tutorial at a DoD conference. It looks like the SciDAC tutorial is on and I just got an acceptance of the SC10 tutorial.
DoD Tutorial
Went well.
SciDAC Tutorial
- Ken Moreland and Andy Bauer
- Format will be similar to last years SC tutorial
- Should we bring a separate projector
Supercomputing Tutorial
- Ken Moreland and Andy Bauer
- CoProcessing tutorial
Warning when ProcessRequest modifies itself
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.
Book omissions and errata
Previously:
Lisa is going to create a bug-tracker like functionality for the Kitware books.
Transition to git
Branchy workflow. Tie in to stronger dashboard.
Install hooks in CMake? Marcus will be responsible for it.
Updates to the VTK submodule.