Skip to content
Snippets Groups Projects
  1. Dec 05, 2016
    • Markus Blatt's avatar
      Support various numeric types for SuperLU at once. · d1dcb220
      Markus Blatt authored and Christoph Grüninger's avatar Christoph Grüninger committed
      Previously, we only supported one numeric type (float, double, complex<float>,
      or complex<double>) that the user could select via a cryptic preprocessor
      define. This was done this way because when including SuperLU headers we
      would otherwise have multiply defined structs in SuperLU. At least in 4.3
      GlobalLU_t is defined in slu_sdefs.h, slu_ddefs.h, slu_cdefs.h, and
      slu_zdefs.h
      
      With this commit we do not include the problematic SuperLU headers anymore.
      Instead why define the functions called by us with extern C within DUNE.
      In addition we now provide all the numeric types for which SuperLU drivers are
      found at the same time.
      
      Hopefully this will also fix problems with multiply defined BLAS routines experienced
      with arpack and SuperLU.
      d1dcb220
  2. Nov 25, 2016
  3. Nov 22, 2016
  4. Nov 17, 2016
    • Dominic Kempf's avatar
      Merge branch 'feature/fix-amg-umfpack-when-using-float' into 'master' · 1eafb167
      Dominic Kempf authored
      [bugfix] This fixes an issue when UMFPack is found and AMG with field type float is used.
      
      The selection of UMFPack as a direct solver does not only depend on UMFPack being found, but also whether the field type is double or complex<double>. Otherwise UMFPack cannot be used as a coarse solver in AMG. This PR fixes this issue.
      
      @markus.blatt: Please take a look at this. 
      @smuething: Please take a look at this. 
      
      See merge request !51
      1eafb167
    • Ansgar Burchardt's avatar
      Merge branch 'feature/move-implementation-to-imp' into 'master' · ec617e3b
      Ansgar Burchardt authored
      Move various implementation classes into the 'Imp' namespace
      
      There are various classes in dune-istl that are effectively implementation
      classes internal to dune-istl. A few of them are base_array_unmanaged,
      base_array_window, compressed_base_array_unmanaged,block_vector_unmanaged,
      BlockVectorWindow, compressed_block_vector_unmanaged, CompressedBlockVectorWindow
      
      See #22 for a brief
      discussion.
      
      This patch moves the classes into the namespace 'Imp'.  That way it is
      clear that they are internal.
      
      All code outside of dune-istl using those classes will break, but does
      such code really exist?
      
      See merge request !65
      ec617e3b
    • Oliver Sander's avatar
      Move various implementation classes into the 'Imp' namespace · 13ec7d1b
      Oliver Sander authored and Ansgar Burchardt's avatar Ansgar Burchardt committed
      There are various classes in dune-istl that are effectively implementation
      classes internal to dune-istl. A few of them are base_array_unmanaged,
      base_array_window, compressed_base_array_unmanaged,block_vector_unmanaged,
      BlockVectorWindow, compressed_block_vector_unmanaged, CompressedBlockVectorWindow
      
      See #22 for a brief
      discussion.
      
      This patch moves the classes into the namespace 'Imp'.  That way it is
      clear that they are internal.
      
      All code outside of dune-istl using those classes will break, but does
      such code really exist?
      13ec7d1b
  5. Nov 15, 2016
  6. Nov 11, 2016
  7. Nov 10, 2016
  8. Nov 08, 2016
    • Markus Blatt's avatar
      Merge branch 'feature/remove-forbidden-downcast' into 'master' · d487fef6
      Markus Blatt authored
      Remove forbidden downcast
      
      This removes several constructors and assignments from base class in the class hierarchy around `base_array`. These removed methods are all implemented using a downcast which may result in undefined behaviour.
      Since they are not used anywhere in the core modules we can maybe remove them. According to @markus.blatt  these base classes are all meant to be internal.
      
      This may cause problems if user code explicitly uses the raw base classes and these methods. However, such user code would only be valid if the passed base class reference is actually an upcasted derived class which is very unlikely.
      
      See merge request !66
      d487fef6
  9. Oct 25, 2016
  10. Oct 24, 2016
  11. Oct 21, 2016
  12. Oct 19, 2016
    • Carsten Gräser's avatar
      Merge branch 'feature/fix-implicit-buildmode-doc' into 'master' · 47fc9a57
      Carsten Gräser authored
      Fix implicit buildmode documentation and adjust test accordingly
      
      This basically turns the issue #21 into a feature by correctly describing the constraints of the implicit build mode and the meaning of its parameters. This invalidates the test against the old interface description which is hence dropped by this MR. As a consequence the bcrsimplicitbuild-test passes again.
      
      See merge request !63
      47fc9a57
  13. Oct 18, 2016
  14. Oct 17, 2016
  15. Oct 12, 2016
  16. Sep 20, 2016
  17. Sep 16, 2016
  18. Sep 13, 2016
  19. Sep 12, 2016
  20. Aug 20, 2016
    • Oliver Sander's avatar
      Merge branch 'bugfix/matrix-transpose' into 'master' · 82b8300d
      Oliver Sander authored
      Fix broken Matrix::transpose()
      
      
      Due to a confusion between the number of lines N and the number of columns M, `Matrix::transpose()` gave wrong results for matrices with N != M.
      
      This also adds a testcase demonstrating the problem to matrixtest.cc.
      
      See merge request !56
      82b8300d
Loading