Attendees: Ken Moreland (SNL), Matt Larsen (LLNL), Rob Maynard (Kitware), Hendrik Schroots, Tom Fogal (NVIDIA), Berk Geveci (Kitware), Chris Sewell (LANL), James Kress (OU), Dave Pugmire (ORNL)
CG&A paper. One of the things left to do is to update the timings for the direct volume rendering to compare against a "reference" implementation. Hendrik is going to try to run something using existing VTK volume renderers. Berk is going to help by providing a python script that can be run using binaries distributed with ParaView.
Dave says the dataset builder classes are ready to be merged in. He will do that soon.
Chris' GTC presentation was accepted. He will be working on that and is happy to have folks participate.
We went over the current Version 1.0 ToDo List. Here is the current status.
|Settling of the core interface||Ken needs to look at dynamic cell set because it has a different than the dynamic array and is causing much more code generation.|
|Standardization of "filters"
||There is a WIP branch on the implementation of filters with a few initial filters added to it.|
|Support worklet operations that are not one-to-one output||Done|
|Basic file I/O||Done. Except Matt has been having trouble loading in VTK files. There appears to be an issue with VTK files exported from VisIt. It is probably some extra meta-data that VisIt is adding. Sujin will take a look at that.|
|Basic rendering||Not started yet. There is a Rendering Infrastructure design document. A lot of the things Matt has been working on could be used. Jeremy and Dave will use that as a start.|
|Clean up Doxygen||Need to get documentation syncing nightly.|
|User's Guide||Behind. Trying to catch up. Making some progress.|
|Prototype VTK/ParaView/VisIt integration
(Technically not part of the release, but should indicate we have viable components.)
|Eric Brugger has made some progress on integrating VTK-m into VisIt. He is able to run the marching cubes algorithm from within VisIt and generate images.|