Teleconference 2016-03-16

From VTKM
Revision as of 12:42, 16 March 2016 by Kmorel (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Attendees: Ken Moreland (SNL), David Pugmire (ORNL), Chris Sewell (LANL), Rob Maynard (Kitware), Berk Geveci (Kitware), Tom Fogal (NVIDIA)

The VTK-m paper submitted to IEEE CG&A has been accepted. However, there were not enough accepted entries to justify the special edition that was planned, so it looks like the data of publication will be bumped back. Ken is preparing the final materials for the publication. He is currently collecting short bios from everyone.

We submitted a VTK-m preproposal in response to the ECP RFI. It went in Monday. We have not heard back anything about it yet.

We have gotten permission to assert copyright of VTK-m version 1.0, so we can release it when we are ready.

There are inconsistencies between the interfaces of VTKDataSetReader and VTKDataSetWriter. There does not appear to be any logical reason for the difference. It would be better if they were made to match each other.

Jeremy made a little progress on annotation.

Example for GTC tutorial: Chris is waiting for Matt's example. Chris wants to put this together next week.

Chris is working with Hamish Carr on a publication on contour trees.

Rob spending time getting VTK-m dashboard green. In some cases a bit more red.

Merged in filters branch.

We have been getting weird test failures with ICC. Were tickling a compiler bug. We updated from ICC 14 to ICC 15 and this seems to have fixed the problem. However, this also caused more things to break. We have also added a check in the code to disable vectorization on ICC 14.

Tom brought up the desire to have another code sprint/hackathon. We are thinking on the June/July time frame.

We went over the current Version 1.0 ToDo List. Here is a current snapshot.

Feature Status
Settling of the core interface Other than little things and filters, the core interface is pretty well set.
  • Rob has a question about the "dimensionality" of the cell sets. That is supposed to be the topological dimensions of the cells. This would require all the cells having the same dimensionality, which is not really being honored. This is causing some problems. Jeremy and Rob need talk about this.
    • The latest thought was to have a flag that states a mixed dimensionality flag.
  • There is a similar question about the "order" on the fields. Right now, it is not used, and we should remove it. In the future, as we implement higher order cells, we will probably have to represent the interpolation as basis functions rather than
Standardization of "filters" Done
Support worklet operations that are not one-to-one output Done
Basic file I/O Done.
Basic rendering Rendering is almost ready. Working out some build issues on the dashboard.
Clean up Doxygen Need to get documentation syncing nightly. Chuck looking into this.
User's Guide Behind. Trying to catch up. Making some progress.
Green dashboard
  • Still have problems with some CUDA dashboards
    • Mostly fixed. Might be a timeout issue.
  • There have been some interop failures.
    • Probably actually an X-windows issue. Chuck will look into this. Not currently at the top of his priority.
  • The new GCC 5.0 compiler is giving warnings in the testing code.
    • There is a merge request to address this. Most are cleaned up.
    • Still working on some failure to vectorize warnings.
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 has an initial implementation and it is working pretty well so far. He has lately added further cell type support (particularly unstructured grids).
  • Rob working on VTK/VTK-m filter integration. Can now move data between VTK and VTK-m