Hi, John
I have the following error if I compile libmesh using openmpi. I am
reposting it because this time it is different from what I posted earlier
(sorry, it did not go to libmesh-users). I have the same petsc as mentioned
in the previous post.
../configure --prefix=/opt/libmesh/1.7.0 --with-c
Hi,
There was a somewhat recent discussion about this issue on #2565 and #2827,
but as far as I know, it was never satisfactorily resolved at that time,
otherwise the update would presumably have made it into 1.6.1.
Jahrul, just to confirm, are you saying that libmesh master works for you
with In
I have a similar error with 1.6.1.tar.gz. Using git, I get 1.7.0_pre, and
following is the error. Now, I have done a fresh installation of latest
PETSc, configured libmesh using
--with-cxx=/path/to/petsc/arch-linux-c-debug/bin/mpicxx, everything else is
as before, libmesh compiled smoothly with no
I am having an issue building 1.6.1 on TACC with the intel compilers
(18.0.2)
I am getting this error:
./include/libmesh/fe_abstract.h(443): error: more than one operator "+"
matches these operands:
built-in operator "arithmetic + arithmetic"
function "operator+(const Pets
Hi All,
I figured it out. I was not calling localize from all the processor and
that could have been the problem. Nevermind the question.
Regards,
Prashant
On Sat, Jul 11, 2020 at 9:02 PM Prashant K. Jha wrote:
> Correction: For approach 1 and 2, I get error
>
> Assertion `this->verify(r.size(
Correction: For approach 1 and 2, I get error
Assertion `this->verify(r.size())' failed.
On Sat, Jul 11, 2020 at 8:55 PM Prashant K. Jha wrote:
> Hi All,
>
> I have been struggling with a very simple problem. I create a system as
> follows:
>
> EquationSystems es(mesh);
> auto &taf_sys = es.add
Hi All,
I have been struggling with a very simple problem. I create a system as
follows:
EquationSystems es(mesh);
auto &taf_sys = es.add_system("TAF");
taf_sys.add_variable("taf", FIRST);
After I solve taf_sys, I want to localize the solution of taf_sys system
(ie "taf" field) on all processors
On Tue, 28 Nov 2017, Zack Vitoh wrote:
*Question 2*
For the cases above, I noticed that I am no longer running libmesh in
parallel when I read in the mesh. I found, and tried to use
libMesh::Partitioner part();
// Partitioner()::partition_unpartitioned_elements(mesh);
// Partitioner.partition_
Hello again,
I have a few related questions, and help is, always, much appreciated!
I am using both pygmsh and meshpy to generate meshes and read them in, but
I'll focus on the former, pygmsh.
*Question 1*
For pygmsh, I can generate and read in (into libmesh) order-1 triangular
(and, I think, te
Hi Jed, hi John,
Thanks very much for your help!
I have used —with-clanguage=cxx because of the complex build. At least for my
earlier version I got an error when not using that.
I am now building PETSC without support for complex numbers and ensuring that
it uses the same compiler as libmesh
On Wed, May 18, 2016 at 3:40 PM, Kathrin Smetana wrote:
> Hi,
>
> Unfortunately I deleted the debug build in the meantime.
>
I built PETSc 3.5.3 using the same configure flags you mentioned (other
than --with-dynamic-loading and --download-umfpack=1, which did not seem to
be valid), and I could
Hi,
Unfortunately I deleted the debug build in the meantime.
Best,
Kathrin
On May 18, 2016, at 5:26 PM, John Peterson wrote:
>
>
> On Wed, May 18, 2016 at 3:04 PM, Jed Brown wrote:
> John Peterson writes:
> > It would be nice if all versions of libmesh worked with debug-enabled
> > PETS
On Wed, May 18, 2016 at 3:04 PM, Jed Brown wrote:
> John Peterson writes:
> > It would be nice if all versions of libmesh worked with debug-enabled
> > PETSc, but that's not something that gets tested very often...
>
> *tears*
>
> I'd like to know what is causing this SEGV. It shouldn't happen
On Wed, May 18, 2016 at 1:09 PM, Kathrin Smetana wrote:
> Hi John,
>
> So using the optimized version of PETSC actually solved the problem. Thank
> you very much again for your help!
>
Thanks for letting us know.
It would be nice if all versions of libmesh worked with debug-enabled
PETSc, but t
On Tue, May 17, 2016 at 3:53 PM, Kathrin Smetana wrote:
>
> I have configured PETSC with the following options:
>
> --with-mpi-dir=/home/kathrin/Implementations/mpich-install
> --download-cmake=yes --with-debugging=1 --with-shared-libraries=1
> --with-dynamic-loading=1 --download-parmetis=1 --dow
Hi John,
Thanks very much for your answer!
I have configured PETSC with the following options:
--with-mpi-dir=/home/kathrin/Implementations/mpich-install --download-cmake=yes
--with-debugging=1 --with-shared-libraries=1 --with-dynamic-loading=1
--download-parmetis=1 --download-mumps=1 --downl
On Tue, May 17, 2016 at 3:26 PM, Kathrin Smetana wrote:
> Hi John,
>
> I have now tried the PETSC versions 3.5.1, 3.5.2, and 3.5.3 and I have got
> the same error as described below for all versions. Note that I have not
> tried 3.5.4 since it has been released after the libmesh 0.9.4 release.
>
Hi John,
I have now tried the PETSC versions 3.5.1, 3.5.2, and 3.5.3 and I have got the
same error as described below for all versions. Note that I have not tried
3.5.4 since it has been released after the libmesh 0.9.4 release.
I am using MPICH 3.0.4. Could that maybe be an issue?
Do you hav
Hi John,
Thanks very much for your answer!
On May 17, 2016, at 2:59 PM, John Peterson wrote:
>
>
> On Tue, May 17, 2016 at 12:51 PM, Kathrin Smetana wrote:
>
> I have just run with the configuration above and I still do not have any
> problems in the optimized mode.
>
>
> OK, maybe I mi
On Tue, May 17, 2016 at 12:51 PM, Kathrin Smetana wrote:
>
> I have just run with the configuration above and I still do not have any
> problems in the optimized mode.
>
OK, maybe I misunderstood. The problem is only when running the dbg
executable?
I would like to stick to the llibmesh vers
Hi John,
Thank you very much for your fast reply and your help!
On May 17, 2016, at 2:42 PM, John Peterson wrote:
>
>
> On Tue, May 17, 2016 at 12:17 PM, Kathrin Smetana wrote:
> Hi all,
>
> I have just installed and configured libmesh (version 0.9.4) using PETSC
> 3.4.5. During making ch
On Tue, May 17, 2016 at 12:17 PM, Kathrin Smetana wrote:
> Hi all,
>
> I have just installed and configured libmesh (version 0.9.4) using PETSC
> 3.4.5. During making check I got the following error in introduction_ex3:
>
> [0]PETSC ERROR:
> ---
Hi all,
I have just installed and configured libmesh (version 0.9.4) using PETSC 3.4.5.
During making check I got the following error in introduction_ex3:
[0]PETSC ERROR:
[0]PETSC ERROR: Caught signal number 11 SEGV: Segme
this work
in the next couple of months.
Thanks for all the help.
Adam
> -Original Message-
> From: Roy Stogner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 01, 2008 11:41 AM
> To: John Peterson
> Cc: Adam Arbree; libmesh-users@lists.sourceforge.net
> Subject:
<[EMAIL PROTECTED]>
To: libmesh-users@lists.sourceforge.net
Sent: Tue Sep 30 18:01:40 2008
Subject: [Libmesh-users] (no subject)
I have an application where I need to solve three nearly identical systems.
For each system, the matrix entries and the rhs will be slightly different,
but the me
That is fantastic; exactly what I needed. Thank you again.
Adam
> -Original Message-
> From: Roy Stogner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 01, 2008 2:13 PM
> To: Adam Arbree
> Cc: libmesh-users@lists.sourceforge.net
> Subject: RE: [Libmesh-
On Wed, 1 Oct 2008, Adam Arbree wrote:
> That said can you give me a sense of how large the DofMap would be
> for an AMR application, say relative the matrix storage?
Depends - in serial, IIRC the matrix storage is much larger. In
parallel, that changes drastically, since PETSc parallelizes th
On Wed, 1 Oct 2008, John Peterson wrote:
> Static may not even be required. I think a single system with 3
> different matrix assembly "branches" is what you want.
John is probably exactly right. In the worst case, if one of your
systems has a constant matrix, having to reassemble it over and
> From: Kirk, Benjamin (JSC-EG) [mailto:[EMAIL PROTECTED]
> Sent: Tue 9/30/2008 8:45 PM
> To: Adam Arbree; libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] (no subject)
> One of the more hackish ways to handle the situation would be to only declare
> one syste
initial guess will be useful.
Adam
From: Kirk, Benjamin (JSC-EG) [mailto:[EMAIL PROTECTED]
Sent: Tue 9/30/2008 8:45 PM
To: Adam Arbree; libmesh-users@lists.sourceforge.net
Subject: Re: [Libmesh-users] (no subject)
By default if you declare three systems you
On Tue, 30 Sep 2008, Adam Arbree wrote:
> I have an application where I need to solve three nearly identical systems.
> For each system, the matrix entries and the rhs will be slightly different,
> but the mesh and finite element type and degree will be identical. I have
> three questions: 1) I
I have an application where I need to solve three nearly identical systems.
For each system, the matrix entries and the rhs will be slightly different,
but the mesh and finite element type and degree will be identical. I have
three questions: 1) I would like to reuse the DofMap between each of th
Hi, I inly want ot check if posting is possible now.
I am subscribed and i can login at sourceforge.
Thanks
hj
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based appl
各位老总:您们好!
诚祝:您们在2008年里;有鼠不尽的快乐!鼠不尽的收获!鼠不尽的钞票!
鼠不尽的幸福!鼠不尽的美满生活!愿:您们阖家欢乐!幸福安康!
我是(深圳市珊湖岛进出口有限公司)的负责人;可以提供:出口报关单,
核销单等等一系列手续;代理:出口报关,商检,境内外运输..等等;还可
以代办
Hi all,
I am suffering from installing PETSC the last few days. Before PETSC
was installed, libmesh examples runs well except for those need PETSC;
when PETSC was installed, configure libmesh again, it said compilation
failed, none of the example could run any more.
For installing PETSC, I ha
Michael Povolotskyi writes:
> Dear Libmesh developers, at some point it appears such a comment in
> the code (see below). Does it mean that the results obtained on a
> mesh that contains pyramids may be wrong? Or they are for sure wrong?
Hi,
I was the one to add that comment. I didn't investi
Dear Libmesh developers,
at some point it appears such a comment in the code (see below).
Does it mean that the results obtained on a mesh that contains pyramids may be wrong?
Or they are for sure wrong?
Thank you,
Michael.
Real Pyramid5::volume () const
00266 // Note: the volume returne
37 matches
Mail list logo