Shuenhoy/vtk-m2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
d24f53a64a
vtk-m2/vtkm/cont/testing/CMakeLists.txt

66 lines
2.1 KiB
CMake
Raw Normal View History

Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
##============================================================================
## Copyright (c) Kitware, Inc.
## All rights reserved.
## See LICENSE.txt for details.
## This software is distributed WITHOUT ANY WARRANTY; without even
## the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
## PURPOSE. See the above copyright notice for more information.
##
## Copyright 2014 Sandia Corporation.
## Copyright 2014 UT-Battelle, LLC.
The Copyright statement now has all the periods in the correct location.
2015-05-21 12:09:22 +00:00
## Copyright 2014 Los Alamos National Security.
Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
##
## Under the terms of Contract DE-AC04-94AL85000 with Sandia Corporation,
## the U.S. Government retains certain rights in this software.
##
## Under the terms of Contract DE-AC52-06NA25396 with Los Alamos National
## Laboratory (LANL), the U.S. Government retains certain rights in
## this software.
##============================================================================
set(headers
Add tests for DataSetBuilderExplicit. Added cont/testing/ExplicitTestData.h which includes several explicit datasets. These datasets come from VTK data generated in VisIt. The new unit tests build datasets in several different ways and do some basic validation. Add some new methods for DataSetFieldAdd class to improve usability.
2016-01-05 21:28:57 +00:00
ExplicitTestData.h
Create a class that generates small test datasets. Converted the unit tests to use this.
2015-05-18 17:17:03 +00:00
MakeTestDataSet.h
Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
Testing.h
Extend the array handle testing to be done on a per device basis. Now we test ArrayHandle with all the vtkm types to make sure all the transfer logic / access logic works for all T types.
2015-06-24 21:40:47 +00:00
TestingArrayHandles.h
Change Field and related methods to use Range and Bounds 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).
2016-05-26 22:02:30 +00:00
TestingComputeRange.h
Add in a serial device adapter and required supporting classes. We now can verify that the array handle is usable by a device adapter.
2014-02-11 17:34:56 +00:00
TestingDeviceAdapter.h
Parallel CellToPoint initial code.
2015-10-30 19:59:36 +00:00
TestingDataSetExplicit.h
TestingDataSetSingleType.h
Test all Fancy ArrayHandles and Array Portals on every device adapter. Fancy array handles being Counting, Implicit, Permutation, Transform, and Zip.
2015-05-05 18:25:48 +00:00
TestingFancyArrayHandles.h
Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
)
vtkm_declare_headers(${headers})
set(unit_tests
Add tests for ArrayHandleCartesianProduct.
2015-12-29 14:44:30 +00:00
UnitTestArrayHandleCartesianProduct.cxx
Created ArrayHandleCompositeVector. This derived array handle creates an array of vectors whose components come from other arrays of vectors. In either case ArrayHandleCompositeVector handles scalars as vectors of size 1.
2014-05-05 15:24:03 +00:00
UnitTestArrayHandleCompositeVector.cxx
Add in a serial device adapter and required supporting classes. We now can verify that the array handle is usable by a device adapter.
2014-02-11 17:34:56 +00:00
UnitTestArrayHandleCounting.cxx
Add ArrayHandleImplicit.
2015-02-13 06:24:43 +00:00
UnitTestArrayHandleImplicit.cxx
Add ArrayHandleIndex class. This is the most common use case for ArrayHandleCounting, and this class is a bit easier to use and a bit faster.
2015-09-15 04:11:09 +00:00
UnitTestArrayHandleIndex.cxx
Add ArrayHandlePermutation Also found a problem with ArrayHandle that manifests itself with derived types when you first do a PrepareForInput and then a PrepareForInPlace. The ArrayHandle assumes the data is already moved to the device and skips the in place call to the array transfer. However, this means the transfer of the derived array handle does not have a chance to set up for in place. I think the appropriate solution may be to move the appropriate logic from ArrayHandle to ArrayTransfer. I will look into that next.
2015-04-24 00:45:24 +00:00
UnitTestArrayHandlePermutation.cxx
Add ArrayHandleTransform.
2015-04-13 20:43:18 +00:00
UnitTestArrayHandleTransform.cxx
Add implicit array for uniform grid point coordinates.
2014-05-01 23:19:54 +00:00
UnitTestArrayHandleUniformPointCoordinates.cxx
add an array handle: ArrayHandleConcatenate
2016-07-15 00:16:57 +00:00
UnitTestArrayHandleConcatenate.cxx
Add ArrayPortalToIterators functionality. This moves the ability to get an iterator from an array portal out of the portal itself. The next step is to move the GetIteratorBegin/End out of ArrayPortal. This should make the implemenation a bit cleaner.
2014-09-04 17:56:15 +00:00
UnitTestArrayPortalToIterators.cxx
Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
UnitTestContTesting.cxx
Add tests for DataSetBuilderExplicit. Added cont/testing/ExplicitTestData.h which includes several explicit datasets. These datasets come from VTK data generated in VisIt. The new unit tests build datasets in several different ways and do some basic validation. Add some new methods for DataSetFieldAdd class to improve usability.
2016-01-05 21:28:57 +00:00
UnitTestDataSetBuilderExplicit.cxx
This commit has several changes. 1. Additional ASSERT calls to validate arguments in: DataSetBuilderRegular 2. Fix some untested compile errors in DataSetBuilderRectilinear 3. Added a new unit test, cont/testing/UnitTestDataSetBuilderRectilinear.cxx 4. Provided additional tests for UnitTestDataSetBuilderRegular.cxx. The new tests in (4) were also included in (3), and provide a much more robust way of validating datasets created. It has nested for loops to do an all-all test on various ways to specify the X,Y, and Z coordinates. It computes the bounds on the coordinate system and make sure they are correct. Note: The GetBounds() call for Rectilinear is not working, and is an item for future discussion. It is disabled for now.
2015-12-30 17:34:04 +00:00
UnitTestDataSetBuilderRectilinear.cxx
Change Regular to Uniform There was an inconsistency in naming classes where axes-aligned grids with even spacing were sometimes called "uniform" and sometimes called "regular". Maintain consistency by always calling them uniform.
2016-01-19 22:54:05 +00:00
UnitTestDataSetBuilderUniform.cxx
Add CellSetPermutation which allows custom iteration over a cell set. When you create a CellSetPermutation you provide an array of the cell ids that you want to iterate. This allows the user to do custom blanking of a data set, or to do multi iteration over a set of cells.
2015-09-28 17:15:26 +00:00
UnitTestDataSetPermutation.cxx
Add vtkm/cont/serial directory for the serial backend.
2016-09-28 15:38:31 +00:00
UnitTestDataSetRectilinear.cxx
Change Regular to Uniform There was an inconsistency in naming classes where axes-aligned grids with even spacing were sometimes called "uniform" and sometimes called "regular". Maintain consistency by always calling them uniform.
2016-01-19 22:54:05 +00:00
UnitTestDataSetUniform.cxx
Add in a serial device adapter and required supporting classes. We now can verify that the array handle is usable by a device adapter.
2014-02-11 17:34:56 +00:00
UnitTestDeviceAdapterAlgorithmDependency.cxx
UnitTestDeviceAdapterAlgorithmGeneral.cxx
Add a dynamic array handle. The dynamic array handle holds a reference to an array handle of an unknown type. It contains the ability to try to cast it to an instance of array handle or to try lists of types and containers. There is currently an issue that is causing the test code not to compile. It is the case that some combinations of types and containers are not compatible. For example, an implict container is bound to a certain type, and the container is undefined if they do not agree. There needs to be a mechanism to detect these invalid combinations and skip over them in the MTP for each.
2014-04-03 19:17:14 +00:00
UnitTestDynamicArrayHandle.cxx
Created DynamicCellSet The DynamicCellSet will be used in place of the pointer to a CellSet in a DataSet. This will prevent us from having to cast it all the time and also remove reliance on boost smart_ptr.
2015-07-27 16:13:27 +00:00
UnitTestDynamicCellSet.cxx
Adding vtkm::cont::RuntimeDeviceInformation. The RuntimeDeviceInformation class allows developers to check if a given device is supported on a machine at runtime. This allows developers to properly check for CUDA support before running any worklets.
2015-12-02 18:55:49 +00:00
UnitTestRuntimeDeviceInformation.cxx
Change ArrayContainerControl to Storage. After a talk with Robert Maynard, we decided to change the name ArrayContainerControl to Storage. There are several reasons for this change. 1. The name ArrayContainerControl is unwieldy. It is long, hard for humans to parse, and makes for long lines and wraparound. It is also hard to distinguish from other names like ArrayHandleFoo and ArrayExecutionManager. 2. The word container is getting overloaded. For example, there is a SimplePolymorphicContainer. Container is being used for an object that literally acts like a container for data. This class really manages data. 3. The data does not necessarily have to be on the control side. Implicit containers store the data nowhere. Derivative containers might have all the real data on the execution side. It is possible in the future to have storage on the execution environment instead of the control (think interfacing with a simulator on the GPU). Storage is not a perfect word (what does implicit storage really mean?), but its the best English word we came up with.
2014-06-23 23:33:04 +00:00
UnitTestStorageBasic.cxx
UnitTestStorageImplicit.cxx
UnitTestStorageListTag.cxx
Add Timer class. Helpful for safely timing parallel code across different devices.
2014-06-10 18:53:34 +00:00
UnitTestTimer.cxx
Add general ability to try execution on multiple devices There are various reasons why you might want to execute something but not have a specific device to execute on. To mange this, add a general function that will try a list of devices in order and attempt to run on them in order.
2016-08-15 23:15:17 +00:00
UnitTestTryExecute.cxx
Add in the minimum part of the control env to have a testable array handle.
2014-02-10 19:53:03 +00:00
)
vtkm_unit_tests(SOURCES ${unit_tests})
Reference in New Issue Copy Permalink