1. 21 May, 2015 1 commit
  2. 22 Oct, 2014 1 commit
  3. 24 Jun, 2014 1 commit
    • Kenneth Moreland's avatar
      Change ArrayContainerControl to Storage. · 21823500
      Kenneth Moreland authored
      After a talk with Robert Maynard, we decided to change the name
      ArrayContainerControl to Storage. There are several reasons for this
      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
      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
      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.
  4. 15 May, 2014 1 commit
    • Kenneth Moreland's avatar
      Add classes to manage point coordinates. · 7d769a8f
      Kenneth Moreland authored
      Each type of point coordinates has its own class with the name
      PointCoordinates*. Currently there is a PointCoordiantesArray that contains
      an ArrayHandle holding the point coordinates and a PointCoordinatesUniform
      that takes the standard extent, origin, and spacing for a uniform rectilinear
      grid and defines point coordiantes for that. Creating new PointCoordinates
      arrays is pretty easy, and we will almost definitely add more. For example,
      we should have an elevation version that takes uniform coordinates for
      a 2D grid and then an elevation in the third dimension. We can probably
      also use a basic composite point coordinates that can build them from
      other coordinates.
      There is also a DynamicPointCoordinates class that polymorphically stores
      an instance of a PointCoordinates class. It has a CastAndCall method that
      behaves like DynamicArrayHandle; it can call a functor with an array handle
      (possible implicit) that holds the point coordinates.
  5. 30 Apr, 2014 1 commit
    • Kenneth Moreland's avatar
      Add DynamicTransform class. · dac47ee5
      Kenneth Moreland authored
      This is used with the FunctionInterface::DynamicTransformCont method to
      convert a call of arguments using dynamic array handles to a function
      templated on concrete types.
  6. 03 Apr, 2014 2 commits
    • Kenneth Moreland's avatar
      Add a mechanism to check whether an array handle is valid · c4ecdbad
      Kenneth Moreland authored
      Use this mechanism in the dynamic array handle to skip over trying
      invalid array handle types (and thereby incurring a compiler error even
      though we never intended to use these classes).
    • Kenneth Moreland's avatar
      Add a dynamic array handle. · d309fa7a
      Kenneth Moreland authored
      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.