GitLab

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)

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.

These can be used internally by

  call self%set_private(name, value)

   or

  call self%get_private(name, value)

but are not valid for the self%set()/get() routines, i.e. are not
visible to users of ELPA.

This is a bit cumbersome, as it involves yet another abstract
intermediate type, but necessary due to language limitations.

Supports multiple indexes now, to be used for non-tunable 'parameters'

In order to increase type safty all ELPA2 kernels provide now
an interface. The interfaces for the C/C++ kernels are automatically
generated during the configure step