> El 7 jun 2017, a las 16:41, Kannan, Ramakrishnan escribió:
>
> Jose,
>
> I am running in the super computer environment. I just do a “module load
> cray-petsc-64/3.7.4.0”. I don’t compile PETSc.
> --
> Regards,
> Ramki
In
Hi Stefano
I used case B) to not change the current code significantly. Nevertheless
case A) is worth to look when the number of domains grow. In case B) I
noticed that the l2g passing to MatSetLocalToGlobalMapping must also
contain the off-proc entries, in order to assemble correctly. As you
On Wed, Jun 7, 2017 at 8:37 AM, Kannan, Ramakrishnan
wrote:
> Barry,
>
> Thanks for the kind response. I am building slepc 3.7.3 and when I
> configure –with-64-bit-indices=1, I am getting the following error.
>
> ./configure --with-64-bit-indices=1 --prefix=/lustre/atlas/proj-
This option belongs to PETSc's configure, not SLEPc's configure.
Jose
> El 7 jun 2017, a las 16:37, Kannan, Ramakrishnan escribió:
>
> Barry,
>
> Thanks for the kind response. I am building slepc 3.7.3 and when I configure
> –with-64-bit-indices=1, I am getting the following
Jose,
I am running in the super computer environment. I just do a “module load
cray-petsc-64/3.7.4.0”. I don’t compile PETSc.
--
Regards,
Ramki
On 6/7/17, 10:41 AM, "Jose E. Roman" wrote:
This option belongs to PETSc's configure, not SLEPc's configure.
Jose
Barry,
Thanks for the kind response. I am building slepc 3.7.3 and when I configure
–with-64-bit-indices=1, I am getting the following error.
./configure --with-64-bit-indices=1
--prefix=/lustre/atlas/proj-shared/csc209/ramki/slepc
ERROR: Invalid arguments --with-64-bit-indices=1
Use -h for
Which version of PETSc are you using? If you use the dev version and try to
call MatSetValues on a MATIS with a non-owned (subdomain-wise) dof it will
raise an error, as MATIS does not implement any caching mechanisms for off-proc
entries.
Off-proc entries are a concept related with the AIJ
Hello Nicolas,
I ran snes/examples/tutorials/ex1f -snes_type fas with a recent version
(3.7.6) and I confirm the problem.
The C version works fine, but the Fortran version complains about a Fortran
callback problem.
My output looks quite similar to yours ...
Best regards,
Natacha
mpirun ex1f
On 7 Jun 2017, at 07:57, TAY wee-beng
> wrote:
Hi,
I have been PETSc together with my CFD code. There seems to be a bug with the
Intel compiler such that when I call some DM routines such as
DMLocalToLocalBegin, a segmentation violation will occur
Hi,
I have been PETSc together with my CFD code. There seems to be a bug
with the Intel compiler such that when I call some DM routines such as
DMLocalToLocalBegin, a segmentation violation will occur if full
optimization is used. I had posted this question a while back. So the
current
10 matches
Mail list logo