1. 25 Feb, 2019 1 commit
  2. 04 Oct, 2018 1 commit
  3. 24 Aug, 2018 1 commit
  4. 05 Jun, 2018 1 commit
  5. 08 Jan, 2018 1 commit
  6. 18 Oct, 2017 1 commit
  7. 20 Sep, 2017 1 commit
    • Kenneth Moreland's avatar
      Update copyright for Sandia · c3a3184d
      Kenneth Moreland authored
      Sandia National Laboratories recently changed management from the
      Sandia Corporation to the National Technology & Engineering Solutions
      of Sandia, LLC (NTESS). The copyright statements need to be updated
      accordingly.
      c3a3184d
  8. 25 May, 2017 1 commit
  9. 18 May, 2017 2 commits
  10. 16 Nov, 2016 1 commit
    • Kenneth Moreland's avatar
      Remove exports for header-only functions/methods · fdaccc22
      Kenneth Moreland authored
      Change the VTKM_CONT_EXPORT to VTKM_CONT. (Likewise for EXEC and
      EXEC_CONT.) Remove the inline from these macros so that they can be
      applied to everything, including implementations in a library.
      
      Because inline is not declared in these modifies, you have to add the
      keyword to functions and methods where the implementation is not inlined
      in the class.
      fdaccc22
  11. 20 Apr, 2016 1 commit
  12. 12 Aug, 2015 1 commit
    • Kenneth Moreland's avatar
      The use of is_sorted in Benchmarker.h was ambiguous · c637bf94
      Kenneth Moreland authored
      Benchmarker provides its own implementation of is_sorted since this
      method was not introduced until C++11 and not all compilers necessarily
      support it. However, for those that did, the system is_sorted conflicted
      with the provided is_sorted. To get around the problem, specify the full
      namespace of the is_sorted being used (which is standard practice in
      VTK-m anyway).
      c637bf94
  13. 03 Aug, 2015 1 commit
  14. 31 Jul, 2015 1 commit
  15. 28 Jul, 2015 1 commit
    • Will Usher's avatar
      Measurement and general improvements to the benchmark suite · e982ebe4
      Will Usher authored
      - A warm up run is done and not timed to allow for any allocation of
        room for output data without accounting for it in the run times.
      Previously this time spent allocating memory would be included in the
      time we measured for the benchmark.
      
      - Benchmarks are run multiple times and we then compute some statistics
        about the run time of the benchmark to give a better picture of the
      expected run time of the function. To this end we run the benchmark
      either 500 times or for 1.5s, whichever comes sooner (though these are
      easily changeable). We then perform outlier limiting by Winsorising the
      data (similar to how Rust's benchmarking library works) and print out
      the median, mean, min and max run times along with the median absolute
      deviation and standard deviation.
      
      - Because benchmarks are run many times they can now perform some
        initial setup in the constructor, eg. to fill some test input data
      array with values to let the main benchmark loop run faster.
      
      - To allow for benchmarks to have members of the data type being
        benchmarked the struct must now be templated on this type, leading to
      a bit of awkwardness. I've worked around this by adding the
      `VTKM_MAKE_BENCHMARK` and `VTKM_RUN_BENCHMARK` macros, the make
      benchmark macro generates a struct that has an `operator()` templated on
      the value type which will construct and return the benchmark functor
      templated on that type. The run macro will then use this generated
      struct to run the benchmark functor on the type list passed. You can
      also pass arguments to the benchmark functor's constructor through the
      make macro however this makes things more awkward because the name of
      the MakeBench struct must be different for each variation of constructor
      arguments (for example see `BenchLowerBounds`).
      
      - Added a short comment on how to add benchmarks in
        `vtkm/benchmarking/Benchmarker.h` as the new system is a bit different
      from how the tests work.
      
      - You can now pass an extra argument when running the benchmark suite to
        only benchmark specific functions, eg. `Benchmarks_TBB
      BenchmarkDeviceAdapter ScanInclusive Sort` will only benchmark
      ScanInclusive and Sort. Running without any extra arguments will run all
      the benchmarks as before.
      e982ebe4