1. 26 Jan, 2018 1 commit
  2. 23 Jan, 2018 1 commit
  3. 18 Jan, 2018 7 commits
  4. 17 Jan, 2018 3 commits
  5. 16 Jan, 2018 9 commits
  6. 15 Jan, 2018 5 commits
  7. 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.
  8. 11 Jan, 2018 1 commit
  9. 10 Jan, 2018 4 commits
  10. 09 Jan, 2018 4 commits
  11. 08 Jan, 2018 4 commits
    • Robert Maynard's avatar
      Merge topic 'better_FloatingPointReturnType' · cda85450
      Robert Maynard authored
      a9e64c4b 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
      c3889a1a Give better error reporting when an Invoke parameter is wrong
      Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
      Acked-by: Robert Maynard's 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.