On 3/7/22 12:22, Stephanie Sparks wrote:
The #include declaration did not seem to work; however, as I
still get the same error.
Should I note this on the github issue?
Yes, please do.
You can just put
#define M_PI 3.14159265358979323846264338327950288
anywhere in that file (before the fir
Thank you Wolfgang!
I added #include to the sc_io.c file and that fixed the error I
was getting for that one.
The #include declaration did not seem to work; however, as I still
get the same error.
Should I note this on the github issue?
Thanks,
Stephanie
On Monday, March 7, 2022 at 7:54:42
Hi Bruno,
No, unfortunately I have not played with the parameter values. Hypre has a
set of recommended parameter values for 3D problems, but I think some are
not exposed to the deal.II interface so I have avoided digging into the
source.
I chose PETSc somewhat arbitrarily, so if you are more
On 3/4/22 16:51, Stephanie Sparks wrote:
I did try to specify C99 as you suggested
OK, good news that that worked at least.
but I get a new error now:
/home/saspark2/build2//tmp/unpack/p4est-2.3.2/sc/src/sc_io.c(581): warning
#266: function "fileno" declared implicitly
retval = fsy
Thanks Wolfgang for that suggestion.
I did try to specify C99 as you suggested but I get a new error now:
/home/saspark2/build2//tmp/unpack/p4est-2.3.2/sc/src/sc_io.c(581): warning
#266: function "fileno" declared implicitly
retval = fsync (fileno (file));
^
/home/saspar
Hermes,
The problem is that you are using a direct solver. Direct solvers
require a lot of memory because the inverse of a sparse matrix is
generally not sparse. If you use a LU decomposition, which I think
MUMPS does, you need a dense matrix to store the LU decomposition.
That's a lot of memory!
