ParaView 3 Telecon 12-16-2010: Difference between revisions
(Created page with '{| cellpadding="2" cellspacing="4" |- ! style="background:#abcdef" | Item ! style="background:#abcdef" | People ! style="background:#abcdef" | Description |- | 1 || Moreland || P…') |
No edit summary |
||
Line 5: | Line 5: | ||
! style="background:#abcdef" | Description | ! style="background:#abcdef" | Description | ||
|- | |- | ||
| 1 || Moreland || Project Randy | | 1 || Moreland, Nathan || Project Randy | ||
|- | |- | ||
| 2 || | | 2 || Greg Weirs || CTH Tracer data | ||
|- | |- | ||
| 3 || | | 3 || Mauldin, Alan || Visit bridge/data files | ||
|- | |- | ||
| 4 || | | 4 || Pebay || Statistics package | ||
|- | |- | ||
| 5 || | | 5 || Mauldin, Weirs || Prism | ||
|- | |- | ||
| 6 || | | 6 || Alan, kitware || ParaView 3.10 Release | ||
|- | |- | ||
| 7 || | | 7 || Mauldin || ParaView roadmap? | ||
|- | |- | ||
| 8 || | | 8 || Moreland || Warning when ProcessRequests modifies itself | ||
|- | |- | ||
| 9 || Moreland || | | 9 || Moreland || Book omissions and errata | ||
|- | |- | ||
| 10 || Moreland || | | 10 || Moreland || Stronger Dashboard | ||
|- | |- | ||
| 11 || | | 11 || branchy workflow | ||
|- | |- | ||
| 12 || | | 12 || Geveci || ParaView + ADIOS | ||
* Test consolidation | * Test consolidation | ||
* Boiling the frog coverage | * Boiling the frog coverage | ||
Line 38: | Line 36: | ||
'''Today:''' | '''Today:''' | ||
Ken has been emailing | Ken has been emailing a proposal around. Help, support needed? | ||
Nathan: in situ on which multicores? In situ project on vtksnl? | |||
Alan: zia app stuff done? | Alan: zia app stuff done? | ||
Need good I/O comparisons between solver output and coprocessing output. | Need good I/O comparisons between solver output and coprocessing output. | ||
Line 55: | Line 47: | ||
'''Previously:''' | '''Previously:''' | ||
== CTH tracer data == | == CTH tracer data == | ||
Line 73: | Line 52: | ||
== VISIT bridge/data files == | == VISIT bridge/data files == | ||
== Statistics Package == | == Statistics Package, min/max == | ||
work in parallel | |||
select data filter | select data filter | ||
complex filter interface | |||
== PRISM == | == PRISM == | ||
== ParaView 3.8.1 Release == | == ParaView 3.8.1 Release == | ||
Line 123: | Line 90: | ||
Branchy workflow. Tie in to stronger dashboard. | Branchy workflow. Tie in to stronger dashboard. | ||
== ParaView + ADIOS == | |||
'''Today:''' | |||
'''Previously:''' | |||
adios is in mainstream paraview--young project |
Revision as of 11:50, 16 December 2010
Item | People | Description |
---|---|---|
1 | Moreland, Nathan | Project Randy |
2 | Greg Weirs | CTH Tracer data |
3 | Mauldin, Alan | Visit bridge/data files |
4 | Pebay | Statistics package |
5 | Mauldin, Weirs | Prism |
6 | Alan, kitware | ParaView 3.10 Release |
7 | Mauldin | ParaView roadmap? |
8 | Moreland | Warning when ProcessRequests modifies itself |
9 | Moreland | Book omissions and errata |
10 | Moreland | Stronger Dashboard |
11 | branchy workflow | |
12 | Geveci | ParaView + ADIOS
|
Project Randy
Today:
Ken has been emailing a proposal around. Help, support needed?
Nathan: in situ on which multicores? In situ project on vtksnl?
Alan: zia app stuff done?
Need good I/O comparisons between solver output and coprocessing output.
Can we distribute PHASTA with coprocessing adapter?
Previously:
CTH tracer data
VISIT bridge/data files
Statistics Package, min/max
work in parallel select data filter complex filter interface
PRISM
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.
ParaView + ADIOS
Today:
Previously:
adios is in mainstream paraview--young project