|[eigen] UmfPackSupport vs SuperLUSupport: input matrix|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: [eigen] UmfPackSupport vs SuperLUSupport: input matrix
- From: Philippe Marti <philippe.marti@xxxxxxxxx>
- Date: Mon, 15 Apr 2013 18:39:41 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=L9X4EfvlNBSyliNrOvjYRm/twtXI7pdbYXAPY6dfqdQ=; b=UjJYRsAt6rEPbRiFz+3KC54OyUrxFp8fQCnF4DgBaNFVmkH9cjM8NOpox9SWL1dN9Z tJRKFqcTB3xztlArXco6bjJ/U2a2fclRN+YFcd4Kh87nIEeVWa8YdwpNSsb+XeSRvvxT ZO0Ndo+RUZZPvPc1bd0BBbtFjVQPvzKhNhbv1p+MSsHEJQesYciIaGmpVVY6RaKoDEie XWQOkxeVsG662gzQ8k17F0hmNBNy/68Xr4z1renNX30eWr1HAAiTVewi9XtOPublN9Zl 94T7dwooyUKvmtpojtcHrNZNCl/e7wfWZRiZtz0WFgvbpHbnu+FkaJ1id99/gNrrl6kx DkFA==
The two sparse solvers provided by UmfPackSupport and SuperLUSupport deal differently with the input storage (at least if the input matrix is compressed and column major). UmfPackSupport only stores the pointers to the data while SuperLUSupport stores a copy of the data. Meaning that I can't really replace one by the other without either wasting memory or have some solver depend code. Did I miss something in the code?
Has this been done on purpose? I couldn't find anything about this in the documentation.