Difference between revisions of "Teleconference 2016-05-25"
(Created page with "Attendees: Ken Moreland (SNL), Alok Hota (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Jeremy Meredith (ORNL), Chris Sewell (LANL), Rob Maynard (Kitware) The dejagore dashb...") |
|||
| Line 4: | Line 4: | ||
The dejagore dashboard is having the CUDA memory issue again. Apparently upgrading the card did not solve the problem. Rob is going to disable all other dashboards to see if we still have the problem. | The dejagore dashboard is having the CUDA memory issue again. Apparently upgrading the card did not solve the problem. Rob is going to disable all other dashboards to see if we still have the problem. | ||
| − | + | The recent labeling contributions need a set of bitmap fonts. To handle this, there is an array in the source that defines the bitmap. There are two issues with introducing this. The first is that these fonts have their own license. Mixing that with our own code with our own license might not be a good idea. The second issue is that if the array is in a header, then you replicate the array in every object file that includes the header. | |
| + | |||
| + | One solution suggested was to create a TPL directory in VTK-m. You could declare a different license under that directory. Also, we could build to its own library, thus circumnavigating the bloating issue. | ||
Release readiness | Release readiness | ||
| + | |||
| + | Code sprint? | ||
Revision as of 13:12, 25 May 2016
Attendees: Ken Moreland (SNL), Alok Hota (SNL), Matt Larsen (LLNL), Eric Bruger (LLNL), Jeremy Meredith (ORNL), Chris Sewell (LANL), Rob Maynard (Kitware)
The dejagore dashboard is having the CUDA memory issue again. Apparently upgrading the card did not solve the problem. Rob is going to disable all other dashboards to see if we still have the problem.
The recent labeling contributions need a set of bitmap fonts. To handle this, there is an array in the source that defines the bitmap. There are two issues with introducing this. The first is that these fonts have their own license. Mixing that with our own code with our own license might not be a good idea. The second issue is that if the array is in a header, then you replicate the array in every object file that includes the header.
One solution suggested was to create a TPL directory in VTK-m. You could declare a different license under that directory. Also, we could build to its own library, thus circumnavigating the bloating issue.
Release readiness
Code sprint?
