[petsc-dev] MUMPS and 64 bit indices
Barry Smith
bsmith at mcs.anl.gov
Mon Dec 15 20:40:57 CST 2014
> On Dec 15, 2014, at 5:57 PM, Matthew Knepley <knepley at gmail.com> wrote:
>
> On Mon, Dec 15, 2014 at 4:17 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
> I cannot fix this. There is a cycle in the dependencies if I introduce libraryOptions inside package.py so package.py cannot do the consistency check, but it should so it is totally screwed.
>
> Matt could fix it but he'd probably have to fuck up the nice simplicity of the code that is there now :-(!
>
> We were already using a mechanism to get around this circularity. Comments on the aesthetic import welcome.
I think the trauma of seeing the provides interface destroyed part of my brain years ago, hence I didn't realize it could be used here.
So, yah, if this works its fine and the way to go.
Thanks
Barry
>
> https://bitbucket.org/petsc/petsc/branch/knepley/fix-configure-package-check
>
> Matt
>
>
> Barry
>
> > On Dec 15, 2014, at 3:42 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >
> >
> >> On Dec 15, 2014, at 3:16 PM, Garth N. Wells <gnw20 at cam.ac.uk> wrote:
> >>
> >> It's possible to configure PETSc with the options
> >>
> >> --with-64-bit-indices --download-mumps
> >>
> >> and compile and run, but it doesn't look like the MUMPS interface supports 64 bit indices. Should the above combination throw an error at configure time?
> >
> > Yes, there is commented code in the consistency check, I cannot remember why it was commented.
> >
> > # if self.double and not self.scalartypes.precision.lower() == 'double':
> > # raise RuntimeError('Cannot use '+self.name+' withOUT double precision numbers, it is not coded for this capability')
> > # if not self.complex and self.scalartypes.scalartype.lower() == 'complex':
> > # raise RuntimeError('Cannot use '+self.name+' with complex numbers it is not coded for this capability')
> > # if self.libraryOptions.integerSize == 64 and self.requires32bitint:
> > # raise RuntimeError('Cannot use '+self.name+' with 64 bit integers, it is not coded for this capability')
> >
> >>
> >> (On a side note, SuperLU_dist and Umfpack are flaky with 64 bit indices, which seems largely related to calling ParMETIS/METIS).
> >
> > Hmm, never heard such reports. Are you using the --download-parmetis and metis? You should be. Is it reproducible problem? We'd like to fix it.
> >
> >
> > Barry
> >
> >>
> >> Garth
> >>
> >
>
>
>
> --
> 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
More information about the petsc-dev
mailing list