- 05 Jun, 2019 1 commit
-
-
Andreas Marek authored
-
- 29 May, 2019 1 commit
-
-
Andreas Marek authored
-
- 05 Mar, 2019 1 commit
-
-
Andreas Marek authored
-
- 01 Mar, 2019 1 commit
-
-
Andreas Marek authored
-
- 20 Feb, 2019 1 commit
-
-
Andreas Marek authored
-
- 28 Nov, 2018 1 commit
-
-
Pavel Kus authored
-
- 20 Nov, 2018 1 commit
-
-
- 18 Oct, 2018 1 commit
-
-
Andreas Marek authored
-
- 23 Nov, 2017 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 18 Nov, 2017 2 commits
-
-
Andreas Marek authored
-
Andreas Marek authored
-
- 26 Oct, 2017 1 commit
-
-
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)
-
- 07 Jul, 2017 1 commit
-
-
Lorenz Huedepohl authored
-
- 18 May, 2017 1 commit
-
-
Lorenz Huedepohl authored
We decided not to provide this information via the key/value store, but rather to use the ftimings module for that. @loh will take care to implement ftimings in the new API @amarek wants to port the legacy API so that the old global module variables still contain valid values
-
- 16 May, 2017 2 commits
-
-
Lorenz Huedepohl authored
Still missing is the compatibility layer, currently it only compiles when configure is called with --disable-legacy Also, a more general solution to parameter passing via environment variables would be nice.
-
Lorenz Huedepohl authored
-