On Mon, 7 Dec 2009 10:53:10 -0500, Alex Peyser peyser.alex at gmail.com wrote:
I've had endless trouble integrating petsc into my system because the object-
oriented C is both only partially object oriented while simultaneously
making access to the underlying functionality obscure.
Okay, I'm
This whole thread has been really interesting. I'm interested in
Barry's suggestion, and I know a handful of people not on the list who
would also be interested. I've got a couple of questions/responses
to the MatSetValues, point-wise physics, and support tools issues
that were raised.
libfast in: /home/buildbot/slave/build/
x86_linux_single_nosched_gcc-4.1_gfortran-4.1_python-2.5_openmpi/PETSc/
dev/default-825/src/ts/impls/explicit/ssp ssp.c: In function
'PetscErrorCode SSPStep_RK_3(_p_TS*, PetscReal, PetscReal, _p_Vec*)':
ssp.c:101: warning: converting to 'PetscInt'
attachment was scrubbed...
URL:
http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20091207/4954adf3/attachment.html
What flags were used to build this, (it hasn't been showing up in the
nightlies)? One of the warnings is definitely harmless, the other was
actually an unused variable (it was hanging around from the more
sophisticated implementation).
I just pushed a patch to eliminate the warnings.
Jed
Sorry, it is
http://www.geodynamics.org:8009/PETSc%20dev%20x86%20linux%20single%20nosched%20gcc-4.1%20gfortran-4.1%20python-2.5%20openmpi/builds/825/step-shell_3/0
Barry
On Dec 7, 2009, at 3:39 PM, Jed Brown wrote:
What flags were used to build this, (it hasn't been showing up in the
On Dec 7, 2009, at 9:53 AM, Alex Peyser wrote:
Have y'all considered a different approach?
I've had endless trouble integrating petsc into my system because
the object-
oriented C is both only partially object oriented while
simultaneously
making access to the underlying functionality
