Dear all,
thanks for your assistance. I will then continue with superlu's memory
allocation!
Thanks again
Gianluca
On 3 July 2012 17:18, Xiaoye S. Li wrote:
> Yes, that limits your preallocated work array to be 2GB.
> Alternatively, you can set lwork=0, rely on superlu to do memory
> allocati
Hong,
thanks for your answer. I do not know if my problem request 64 bit support.
My understanding is that I can preallocate the working array for
superlu with the PETSc database options -mat_superlu_lwork. Following
PETSc manual, this has to be specified in bytes.
>From my point of view, the pr
On Tue, 3 Jul 2012, Barry Smith wrote:
>
> On Jul 3, 2012, at 3:08 AM, Blaise Bourdin wrote:
>
> >
> > On Jul 3, 2012, at 4:10 AM, Barry Smith wrote:
> >
> >>
> >> Blaise,
> >>
> >> I don't understand why the patch does anything:
> >>
> >> - *ierr = VecRestoreArray(*v,0);if (*ierr) return
On Jul 3, 2012, at 3:08 AM, Blaise Bourdin wrote:
>
> On Jul 3, 2012, at 4:10 AM, Barry Smith wrote:
>
>>
>> Blaise,
>>
>> I don't understand why the patch does anything:
>>
>> - *ierr = VecRestoreArray(*v,0);if (*ierr) return;
>> + PetscScalar *fa;
>> + *ierr = F90Array1dAccess(a,PETSC_
I'm trying to understand the use of null spaces. Whatever I do, it
always seem to pass the null space test. Could you please tell me
what's wrong with this example (c++, petsc-3.3-p1):
$ cat nullsp.cc
// test null space check
#include
int main(int argc, char **argv) {
PetscErrorCode ierr;
On Jul 3, 2012, at 4:10 AM, Barry Smith wrote:
>
> Blaise,
>
> I don't understand why the patch does anything:
>
> - *ierr = VecRestoreArray(*v,0);if (*ierr) return;
> + PetscScalar *fa;
> + *ierr = F90Array1dAccess(a,PETSC_SCALAR,(void**)&fa
> PETSC_F90_2PTR_PARAM(ptrd));
> + *ierr =
On Jul 3, 2012, at 4:10 AM, Barry Smith wrote:
>
> Blaise,
>
>I don't understand why the patch does anything:
>
> - *ierr = VecRestoreArray(*v,0);if (*ierr) return;
> + PetscScalar *fa;
> + *ierr = F90Array1dAccess(a,PETSC_SCALAR,(void**)&fa
> PETSC_F90_2PTR_PARAM(ptrd));
> + *ierr
-L/usr/lib/gcc/x86_64-linux-gnu/4.4.3 -L/usr/lib/x86_64-linux-gnu -lmpi_f90
> -lmpi_f77 -lifport -lifcore -lm -lm -lmpi_cxx -ldl -lmpi -lopen-rte
> -lopen-pal -lnsl -lutil -limf -lsvml -lipgo -ldecimal -lcilkrts -lstdc++
> -lgcc_s -lirc -lpthread -lirc_s -ldl
> -
>
>
> dr. ir. Christiaan Klaij
> CFD Researcher
> Research & Development
> E mailto:C.Klaij at marin.nl
> T +31 317 49 33 44
>
> MARIN
> 2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands
> T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl
>
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120703/8fb0efb4/attachment-0001.html>
vaut des fois les mondes et
> >> que les plus ardentes ambitions sont celles qui ont eu l'orgueil de
> >> l'Anonymat" -- Non omnibus, sed mihi et tibi
> >> Amedeo Modigliani
> >
> >
>
>
>
> --
> "[Je pense que] l'homme est un monde qui vaut des fois les mondes et
> que les plus ardentes ambitions sont celles qui ont eu l'orgueil de
> l'Anonymat" -- Non omnibus, sed mihi et tibi
> Amedeo Modigliani
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120703/134497e6/attachment.html>
Dear all,
I am trying to use superlu as solver for a large, sparse matrix, and I
would like to use -mat_superlu_lwork to speed up the computation. The
problem I encounter is that my lwork size I would need is greated than
the maximum value for an object of type long int and is not correctly
read b
Actually its INT_MAX.
>From superlu's dgssvx.c
>>>
* lwork (input) int
* Specifies the size of work array in bytes.
void
dgssvx(superlu_options_t *options, SuperMatrix *A, int *perm_c, int *perm_r,
int *etree, char *equed, double *R, double *C,
SuperMatrix *L, Supe
i et tibi
> Amedeo Modigliani
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120703/a049bdcd/attachment-0001.html>
Yes, that limits your preallocated work array to be 2GB.
Alternatively, you can set lwork=0, rely on superlu to do memory
allocation for you. Then you can use more than 2GB memory.
Sherry Li
On Tue, Jul 3, 2012 at 9:32 AM, Satish Balay wrote:
> Actually its INT_MAX.
>
> From superlu's dgssvx.
13 matches
Mail list logo