@lists.sourceforge.net
Subject: Re: [Libmesh-users] Memory used by a System Object.
That warning is from PETSc and can be ignored (PETSc doesn't understand that
you're passing libMesh command-line options).
--keep-cout is the correct one.
Derek
On Thu, Aug 18, 2016 at 1:29 PM Jayaraman, Vegnesh
ma
o value)
>
>
> From: David Knezevic [david.kneze...@akselos.com]
> Sent: Thursday, August 18, 2016 12:26 PM
> To: Jayaraman, Vegnesh
> Cc: Cody Permann; libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] Memory used by a System Object.
&
>> WARNING! could be spelling mistake, etc!
>> Option left: name:--keep-cout value: True
>>
>>
>> Is there a mistake in the way i set the run time option?
>>
>> Thanks and Regards
>> Vegnesh
>>
>>
>> From: Cody Permann [codyperm...
(no value)
From: David Knezevic [david.kneze...@akselos.com]
Sent: Thursday, August 18, 2016 12:26 PM
To: Jayaraman, Vegnesh
Cc: Cody Permann; libmesh-users@lists.sourceforge.net
Subject: Re: [Libmesh-users] Memory used by a System Object.
Use --keep-cout, not --keep-o
___
> From: Cody Permann [codyperm...@gmail.com]
> Sent: Thursday, August 18, 2016 11:35 AM
> To: Jayaraman, Vegnesh; libmesh-users@lists.sourceforge.net
> Subject: Re: [Libmesh-users] Memory used by a System Object.
>
> It's a runtime option.
> On Thu, Aug 18, 2016 at
s and Regards
Vegnesh
From: Cody Permann [codyperm...@gmail.com<mailto:codyperm...@gmail.com>]
Sent: Thursday, August 18, 2016 9:36 AM
To: Jayaraman, Vegnesh;
libmesh-users@lists.sourceforge.net<mailto:libmesh-users@lists.sourceforge.net>
Subject: Re: [Libmesh-users] Memory used by a
On Thu, Aug 18, 2016 at 10:31 AM, Jayaraman, Vegnesh
wrote:
> The --keep-cout option must be set as a compilation flag for libmesh or as
> a compilation flag for my program. ?
>
It's a command line argument (runtime) to your program.
--
John
m:* Cody Permann [codyperm...@gmail.com]
> *Sent:* Thursday, August 18, 2016 9:36 AM
> *To:* Jayaraman, Vegnesh; libmesh-users@lists.sourceforge.net
> *Subject:* Re: [Libmesh-users] Memory used by a System Object.
>
> Be careful about that conclusion. libMesh suppresses stdout from a
@lists.sourceforge.net
Subject: Re: [Libmesh-users] Memory used by a System Object.
Be careful about that conclusion. libMesh suppresses stdout from all ranks
except the master. If you want to see how many times something is printing (not
the best way to debug) add "--keep-cout" on the co
Be careful about that conclusion. libMesh suppresses stdout from all ranks
except the master. If you want to see how many times something is printing
(not the best way to debug) add "--keep-cout" on the command line.
Cody
On Wed, Aug 17, 2016 at 11:13 PM Jayaraman, Vegnesh
wrote:
> I checked by
I checked by printing a statement in the constructor. And I guess, the answer
is there one copy of the ARRAY variable for the entire system.
I am planning to declare another equation systems object (with a different
mesh) within the foo system and hence I asked the question as I didnt want the
Hi
I have a basic question on the memory used :
I am creating a custom system class like :
class foo : public System
{
foo(EquationSystems& es,
const std::string& name_in,
const unsigned int number_in):
:System(es, name_in, n
12 matches
Mail list logo
