1. 16 Jan, 2018 1 commit
    • Robert Maynard's avatar
      vtkm::rendering has more compilation units to help out 32bit compilers · 5ecf2d11
      Robert Maynard authored
      Visual Studio default toolset uses 32bit executables for compiling which
      means that if it uses more than 4GB of memory per instance it crashes.
      By moving the ConnectivityTracer into a separate compilation unit we
      can help out the compiler.
      This also improved compilation times and library size:
      build time (j8): 48.62 real
      lib size: 6.2MB
      build time (j8): 41.31 real
      lib size: 5.0MB
  2. 15 Jan, 2018 5 commits
  3. 12 Jan, 2018 1 commit
    • Sujin Philip's avatar
      Add CellLocator · 8f78aa73
      Sujin Philip authored
      Add a general cell locator that has an optimized path for uniform grid
      datasets and uses CellLocatorTwoLevelUniformGrid for all other
      dataset types.
  4. 10 Jan, 2018 4 commits
  5. 09 Jan, 2018 4 commits
  6. 08 Jan, 2018 4 commits
    • Robert Maynard's avatar
      Merge topic 'better_FloatingPointReturnType' · cda85450
      Robert Maynard authored
       FloatPointReturnType is float if 'T' is < 32bytes instead of being double.
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Kenneth Moreland's avatarKenneth Moreland <kmorel@sandia.gov>
      Acked-by: Thomas Otahal's avatarThomas Otahal <tjotaha@sandia.gov>
      Merge-request: !1048
    • Kenneth Moreland's avatar
      Merge topic 'better-type-error-reporting' · 747c5c90
      Kenneth Moreland authored
      fe9594c1 Add hint to read source code for help
       Give better error reporting when an Invoke parameter is wrong
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: default avatarRobert Maynard <robert.maynard@kitware.com>
      Merge-request: !1022
    • Kenneth Moreland's avatar
      Add hint to read source code for help · fe9594c1
      Kenneth Moreland authored
      In trying to give error diagnostics with template definitions of invalid
      types, the user encounters some pretty confusing error messages at
      first. There is no way to get the compiler to give exactly the
      diagnostics we want in a nice readable error message, so we are putting
      some verbose instructions as comments in the code. However, a user might
      not know to look at the source code since the error happens deep in an
      unfamiliar (and complicated) class. Thus, add (yet another) error at the
      front that gives a (hopefully) clear indication to look at the source
      code for help in understanding the errors.
    • Kenneth Moreland's avatar
      Give better error reporting when an Invoke parameter is wrong · c3889a1a
      Kenneth Moreland authored
      When one of the parameters to DispatcherBase::Invoke is incorrect, you
      get an error in a strange place. It is deep in a call stack using some
      heavily templated types rather than where the Invoke is actually called.
      Formerly, the code was structured to give a very obfuscated error
      message. Try to make this easier on users by first adding helpful hints
      in the code around where the error is to explain why the error occured
      and helpful advice on how to track down the problem. Second, reconfigure
      the static_assert so that the compiler gives a readable error message.
      Third, add some auxiliary error messages that provide additional
      information about the types and classes involved in the error.
  7. 06 Jan, 2018 1 commit
  8. 04 Jan, 2018 12 commits
  9. 03 Jan, 2018 8 commits