1. 18 Nov, 2016 1 commit
  2. 14 Nov, 2016 1 commit
  3. 11 Nov, 2016 2 commits
  4. 02 Nov, 2016 1 commit
  5. 01 Nov, 2016 1 commit
  6. 25 Oct, 2016 1 commit
  7. 17 Aug, 2016 1 commit
  8. 05 Aug, 2016 1 commit
  9. 04 Aug, 2016 1 commit
  10. 14 Jun, 2016 2 commits
  11. 09 Jun, 2016 2 commits
  12. 30 May, 2016 1 commit
  13. 25 May, 2016 2 commits
  14. 24 May, 2016 1 commit
  15. 19 May, 2016 1 commit
  16. 18 May, 2016 1 commit
  17. 23 Apr, 2016 1 commit
  18. 22 Apr, 2016 1 commit
  19. 19 Apr, 2016 1 commit
  20. 18 Apr, 2016 2 commits
  21. 15 Apr, 2016 1 commit
  22. 14 Apr, 2016 1 commit
  23. 13 Apr, 2016 2 commits
  24. 12 Apr, 2016 1 commit
  25. 01 Apr, 2016 1 commit
  26. 29 Mar, 2016 1 commit
  27. 18 Mar, 2016 1 commit
    • Andreas Marek's avatar
      Allow ELPA to be build with single and double precision symbols in one · 647aa5a8
      Andreas Marek authored
      library
      
      It the configure option "--enable-single-precision" is specified,
      ELPA will also be build for single precision usage. The double precision
      and single precision will be available at the same time with names
      "solve_evp_real_1stage_double" or "solve_evp_real_1stage_single" and
      so on...
      
      This change immplied some major refactoring of the ELPA code:
      1.) functions/procedures had to be renamed with suffix "_double"
      
      2.) If necessary the same functions have to be available with suffix
      "_single"
      
      3.) Variable kind definitions have to be consistent with the
      intented use
      
      To avoid uneccessary code duplication this is done (most of the time)
      with preprocessor string substitution.
      
      The documentation has been updated.
      
      NOT SUPPORTED are at the moment:
      
      - single precision usage of ELPA2 with kernels, others than "generic"
        and "generic_simple"
      
      - single precision usage of GPU
      647aa5a8
  28. 26 Feb, 2016 1 commit
  29. 24 Feb, 2016 2 commits
    • Andreas Marek's avatar
      Add migration notice · 31a03aa2
      Andreas Marek authored
      31a03aa2
    • Andreas Marek's avatar
      Optional build of ELPA without MPI · 49f119aa
      Andreas Marek authored
      The configure flag "--enable-shared-memory-only" triggers a build
      of ELPA without MPI support:
      
      - all MPI calls are skipped (or overloaded)
      - all calls to scalapack functions are replaced by the corresponding
        lapack calls
      - all calls to blacs are skipped
      
      Using ELPA without MPI gives the same results as using ELPA with 1 MPI
      task!
      
      This version is not yet optimized for performance, here and there some
      unecessary copies are done.
      
      Ths version is intended for users, who do not have MPI in their
      application but still would like to use ELPA on one compute node
      49f119aa
  30. 17 Feb, 2016 1 commit
    • Andreas Marek's avatar
      Single precision support for ELPA2 · 940b8f26
      Andreas Marek authored
      ELPA2 can now be build (as ELPA1) for single precision calculations.
      The ELPA2 kernles which are implemented in assembler, C, or C++ have NOT
      yet been ported.
      
      Thus at the moment only the GENERIC and GENERIC_SIMPLE kernels support
      single precision calculations
      940b8f26
  31. 12 Feb, 2016 1 commit
    • Andreas Marek's avatar
      Single precision support for ELPA2 · 56043bdc
      Andreas Marek authored
      ELPA2 can now be build (as ELPA1) for single precision calculations.
      The ELPA2 kernles which are implemented in assembler, C, or C++ have NOT
      yet been ported.
      
      Thus at the moment only the GENERIC and GENERIC_SIMPLE kernels support
      single precision calculations
      56043bdc
  32. 05 Feb, 2016 1 commit
  33. 13 Jan, 2016 1 commit