ParaView 3 Telecon 01-13-2011
| 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
|
notes today:
version 3.10, 3.10.1
march meeting in san diego? ken--oscar? no, nothing
berk, made plans around it
greg--cth, prism cth may have an issue but not paraview, greg thinks holding off checking in prism view autoscaling in view
particles get into 3.10--exodus particles--alex brown; 2/3 terrabyte rocket sled hitting water
particles in exodus
working on getting berk 2 cth experts on thursday afternoon
statistics find data box--
doesn't have notion of min/max
in situ nathan, ken
phillipe statistics
ken asked about funding; about 1fte worth of person through end of Jan, contract resets, out to (rhondas?) desk
Project Randy
Today:
may need help later on feature comparison table, time to go
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? was run on ciello unclassified, passed;
Need good I/O comparisons between solver output and coprocessing output.
Can we distribute PHASTA with coprocessing adapter?
Previously:
CTH tracer data
starting to get particle and tracer data issues from users particle data isn't working one dataset is 200 gig in size Alan working
VISIT bridge/data files
works, but issues with updates on silo (not paraview) silo is file format that visit reads, sort of separate library
Statistics Package, min/max
work in parallel select data filter complex filter interface
touches lots of things, not in 3.10, hoepfully in 3.10.1
PRISM
ParaView 3.10 Release
waiting for hdf5 to move over vtk moving of whole directory selection bug (selection points) mesa issue (alan, jeff)
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, branchy workflow, topics, masternext
Previously:
Branchy workflow. Tie in to stronger dashboard.
dashboard greenness!
maintainers? slowdown in development?
Berk
data in paraview/baseline paraview
ParaView + ADIOS
Today:
Previously:
adios is in mainstream paraview--young project
vtkArray
shallow copy vs. deep copy design doc on paraview's developer wiki
