- Jun 06, 2016
-
-
Kenneth Moreland authored
Fix minor issues with building with OSMesa See merge request !440
-
Kenneth Moreland authored
It is necessary for the OSMesa test, and will probably be needed for tests in the future.
-
Kenneth Moreland authored
There was an error in the CMakeLists.txt in the rendering tests where the include directory was linked in instead of the OSMesa library. It was a simple mistake of typing the wrong CMake variable.
-
- Jun 03, 2016
-
-
a0af013c Auto-detection of cuda version requires usage of a working directory. Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !439
-
1d379db4 Allow people to build rendering without mesa. Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !438
-
Kenneth Moreland authored
Rename rendering classes Per our discussion in our last technical meeting, we are renaming several of the rendering classes to be more clear and consistent with other software products. See merge request !437
-
Robert Maynard authored
Without a working directory specified, the executable will be output to what-ever working directory cmake-gui was launched from. In most cases when CMake is the 'system' version, this is a directory that you don't have write access to.
-
Robert Maynard authored
-
- Jun 02, 2016
-
-
Kenneth Moreland authored
The word surface is more often used for something like a polygonal mesh, so this name is quite confusing. Canvas is consistent with a conventional name in GUI widget APIs.
-
Kenneth Moreland authored
The rendering classes do not actually manage windows, and window was not descriptive of what this class was doing. We decided that the class was mostly analogous to what we call a "view" in ParaView.
-
Kenneth Moreland authored
This name was chosen to reflect the analogous name in VTK.
-
Kenneth Moreland authored
This name was chosen to reflect the analogous name in VTK.
-
Kenneth Moreland authored
Make sure all header files are listed with build This should help ensure that all files are properly installed. See merge request !436
-
Kenneth Moreland authored
-
Kenneth Moreland authored
Not having them could cause compiler issues.
-
Kenneth Moreland authored
For header files, this only adds the file to IDE file lists, which is convenient but not critical. However, the test did find a ligit error in the hello_world example where the TBB build was actually using the serial device adapter.
-
Kenneth Moreland authored
-
Kenneth Moreland authored
The benchmarking header files were not listed. Not a huge deal since these files do not need to be installed, but they should be listed anyway. Changed the vtkm_save_benchmarks CMake macro to be able to list headers. Also moved everything from BenchmarkDeviceAdapter.h to BenchmarkDeviceAdapter.cxx. Since this code shouldn't need to be included by anything except this benchmark, there is no need to have it in a header file. Plus, the build changes would mean that any change in the header (where most of the source was) could cause all code in this directory to recompile. I do not want to set that precedent.
-
Kenneth Moreland authored
The test is a simple CMake script that finds all files in the build directory with certain extensions (.h, .cxx, etc.) and makes sure that the filename is listed somewhere in the CMakeLists.txt file of the same directory. If the filename is listed in the CMakeLists.txt file, then there is a good chance it is being addressed by the build. This should help catch when header files are not being installed. It also should help verify that test builds are being done on all files. It will also highlight dead source files.
-
Kenneth Moreland authored
delete the vtkm::filter::FieldTypes header. See merge request !434
-
- Jun 01, 2016
-
-
Kenneth Moreland authored
Fix minor compile issues with font classes See merge request !435
-
Kenneth Moreland authored
These compile warnings include implicit conversion from signed to unsigned, a shadowed variable, and an unused static function.
-
Kenneth Moreland authored
Not all systems put their OpenGL headers in a directory named GL. (In particular, OSX decides to be different.) The vtkm/rendering/internal/ OpenGLHeaders.h header takes care of including the OpenGL header on all platforms.
-
Kenneth Moreland authored
This is required for installing the files. It is also useful for developers because it adds the files to IDEs and creates test builds for the header files. Those test builds highlighted some missing includes.
-
Robert Maynard authored
The header is used by nothing, and contains an old version of the FieldMetadata class.
-
Jeremy Meredith authored
Adding text annotations to rendering This adds bitmap font support and two types of text annotations - screen space text and world-space billboard text - as well as enables the labels in the axes. See merge request !423
-
Jeremy Meredith authored
-
Jeremy Meredith authored
-
Kenneth Moreland authored
Reader should name fields only with their field name The Legacy VTK file reader was augmenting all the field names with the type of field. For example, if you had a point scalar field named "elevation", it would be loaded as "SCALARS:elevation". This is bad for two reasons. First, it is downright confusing. A tool like ParaView or VisIt will tell me the field is named "elevation", but VTK-m will report that field does not exist. Second, the writer does not follow the same convention. Thus, if you have a loop of read file, modify, write file, you could end up with fields named "SCALARS:SCALARS:SCALARS:...". See merge request !432
-
Kenneth Moreland authored
Fix endian flip when reading vector arrays The legacy VTK file reader has a condition to flip the bytes in values when the endian does not match the current system. The problem was that when reading in a vector, the flip was happening on all bytes of a Vec. This caused the last components of the Vec to be flipped with the first components. Instead, we want each component to be flipped independently. See merge request !433
-
- May 31, 2016
-
-
Kenneth Moreland authored
The legacy VTK file reader has a condition to flip the bytes in values when the endian does not match the current system. The problem was that when reading in a vector, the flip was happening on all bytes of a Vec. This caused the last components of the Vec to be flipped with the first components. Instead, we want each component to be flipped independently.
-
Jeremy Meredith authored
Conflicts: vtkm/rendering/RenderSurfaceGL.h vtkm/rendering/Window.h
-
Kenneth Moreland authored
The Legacy VTK file reader was augmenting all the field names with the type of field. For example, if you had a point scalar field named "elevation", it would be loaded as "SCALARS:elevation". This is bad for two reasons. First, it is downright confusing. A tool like ParaView or VisIt will tell me the field is named "elevation", but VTK-m will report that field does not exist. Second, the writer does not follow the same convention. Thus, if you have a loop of read file, modify, write file, you could end up with fields named "SCALARS:SCALARS:SCALARS:...".
-
317a48d4 Prefer using PointCount instead of FromCount in cell based worklets. Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: Kenneth Moreland <kmorel@sandia.gov> Merge-request: !431
-
Kenneth Moreland authored
Create Range and Bounds helper classes See merge request !429
-
Robert Maynard authored
The PointCount name is far more descriptive and helps readers understand what the content of the variable is.
-
- May 29, 2016
-
-
Kenneth Moreland authored
In addition to this being necessary to be compatible with recent changes, it makes for cleaner declaration of these values.
-
Kenneth Moreland authored
First, be more explicit when we mean a range of values in a field or a spacial bounds. Use the Range and Bounds structs in Field and CoordinateSystem to make all of this more clear (and reduce a bit of code as well).
-
Kenneth Moreland authored
This is a simple struct that defines min and max values over X, Y, and Z to define an axis-aligned bounding box.
-
Kenneth Moreland authored
This is a simple struct that has a min and max scalar value to represent a range of scalar values. It also comes with several helper methods.
-