1. 10 Aug, 2018 1 commit
  2. 08 Aug, 2018 1 commit
  3. 01 Aug, 2018 3 commits
  4. 05 Jun, 2018 1 commit
  5. 29 May, 2018 1 commit
  6. 25 May, 2018 1 commit
  7. 24 May, 2018 1 commit
  8. 22 May, 2018 1 commit
  9. 11 May, 2018 1 commit
  10. 30 Apr, 2018 1 commit
  11. 17 Apr, 2018 1 commit
  12. 14 Mar, 2018 1 commit
  13. 05 Mar, 2018 1 commit
  14. 06 Feb, 2018 1 commit
  15. 05 Feb, 2018 4 commits
  16. 08 Jan, 2018 1 commit
  17. 14 Dec, 2017 2 commits
  18. 01 Dec, 2017 2 commits
  19. 30 Nov, 2017 1 commit
  20. 27 Nov, 2017 1 commit
  21. 25 Nov, 2017 1 commit
  22. 24 Nov, 2017 2 commits
  23. 07 Nov, 2017 1 commit
  24. 30 Oct, 2017 1 commit
  25. 26 Oct, 2017 2 commits
    • Lorenz Huedepohl's avatar
      First implementation of an autotuning procedure · 0ebe4802
      Lorenz Huedepohl authored
      To be used like this
      
         class(elpa_t), pointer      :: e
         class(elpa_autotune_t), pointer :: tune_state
      
         e => elpa_allocate()
         call e%set(...)
         [...]
         assert_elpa_ok(e%setup())
      
         tune_state => e%autotune_setup(ELPA_AUTOTUNE_FAST, ELPA_AUTOTUNE_DOMAIN_REAL)
      
         ! Autotuning loop, continues until all combinations have been tried
         do while (e%autotune_step(tune_state))
           ! Do the steps that are representative of your calculation
           call e%eigenvectors(a, ev, z, error)
         end do
      
         ! Fix best parameters, and de-allocate the autotune object
         call e%autotune_set_best(tune_state)
         call elpa_autotune_deallocate(tune_state)
      0ebe4802
    • Lorenz Huedepohl's avatar
      67c4a5dd
  26. 21 Aug, 2017 1 commit
  27. 08 Aug, 2017 1 commit
  28. 03 Aug, 2017 1 commit
    • Lorenz Huedepohl's avatar
      Fix memory leak · 72700e47
      Lorenz Huedepohl authored
      The timer object was not properly removed when elpa_destroy() was called
      on an ELPA instance, leading to a memory leak
      72700e47
  29. 30 Jul, 2017 1 commit
    • Lorenz Huedepohl's avatar
      Loop over all possible domain decompositions · fabb1c42
      Lorenz Huedepohl authored
      We got reports from a user that there were troubles with certain domain
      decompositions. So far the tests only looked at (approximately) square
      decompositions in column-major process order.
      
      Now, a new class of tests loops over all possible decompositions
      (row * col) for a given number of total tasks.
      
      So far, we can not confirm that there are any problems, all
      possibilities work as expected.
      fabb1c42
  30. 15 Jul, 2017 1 commit
  31. 07 Jul, 2017 1 commit
    • Lorenz Huedepohl's avatar
      Make procedures that are part of a generic public · c5d41b6c
      Lorenz Huedepohl authored
      This prevented compilation with Intel 2018 Beta and solves issue #54. It
      turns out you can only override type-bound procedures that are
      accessible in the module where you override them, thus they have to be
      private. A "deferred, private" type bound procedure could only be
      overriden from the same module (or a submodule thereof).
      
      Many thanks to Igor Vorobtsov from Intel for clarifying this.
      c5d41b6c