Run in the debugger and step/next through the code to see what code path it
is taking and why it doesn't seem to follow the intended code path.
> On Mar 26, 2018, at 7:10 AM, Matthew Knepley wrote:
>
> On Mon, Mar 26, 2018 at 1:15 AM, TAY wee-beng
On Mon, Mar 26, 2018 at 1:15 AM, TAY wee-beng wrote:
>
> On 24/3/2018 6:00 AM, Matthew Knepley wrote:
>
> On Fri, Mar 23, 2018 at 5:23 AM, TAY wee-beng wrote:
>
>>
>> On 21/3/2018 7:47 PM, Matthew Knepley wrote:
>>
>> On Wed, Mar 21, 2018 at 4:59 AM, TAY
On 24/3/2018 6:00 AM, Matthew Knepley wrote:
On Fri, Mar 23, 2018 at 5:23 AM, TAY wee-beng > wrote:
On 21/3/2018 7:47 PM, Matthew Knepley wrote:
On Wed, Mar 21, 2018 at 4:59 AM, TAY wee-beng >
On Wed, Mar 21, 2018 at 4:59 AM, TAY wee-beng wrote:
>
> On 19/3/2018 6:32 PM, Matthew Knepley wrote:
>
> On Mon, Mar 19, 2018 at 5:19 AM, TAY wee-beng wrote:
>
>>
>> On 17/3/2018 1:15 AM, Matthew Knepley wrote:
>>
>> On Fri, Mar 16, 2018 at 12:54 PM, TAY
On 19/3/2018 6:32 PM, Matthew Knepley wrote:
On Mon, Mar 19, 2018 at 5:19 AM, TAY wee-beng > wrote:
On 17/3/2018 1:15 AM, Matthew Knepley wrote:
On Fri, Mar 16, 2018 at 12:54 PM, TAY wee-beng >
On Mon, Mar 19, 2018 at 5:19 AM, TAY wee-beng wrote:
>
> On 17/3/2018 1:15 AM, Matthew Knepley wrote:
>
> On Fri, Mar 16, 2018 at 12:54 PM, TAY wee-beng wrote:
>
>>
>> On 15/3/2018 6:21 PM, Matthew Knepley wrote:
>>
>> On Thu, Mar 15, 2018 at 3:51 PM, TAY
On 17/3/2018 1:15 AM, Matthew Knepley wrote:
On Fri, Mar 16, 2018 at 12:54 PM, TAY wee-beng > wrote:
On 15/3/2018 6:21 PM, Matthew Knepley wrote:
On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng >
> On Mar 16, 2018, at 11:54 AM, TAY wee-beng wrote:
>
>
> On 15/3/2018 6:21 PM, Matthew Knepley wrote:
>> On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng wrote:
>> Hi,
>>
>> I'm running a CFD code which solves the momentum and Poisson eqns.
>>
>> Due to
On Fri, Mar 16, 2018 at 12:54 PM, TAY wee-beng wrote:
>
> On 15/3/2018 6:21 PM, Matthew Knepley wrote:
>
> On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng wrote:
>
>> Hi,
>>
>> I'm running a CFD code which solves the momentum and Poisson eqns.
>>
>> Due to poor
On 15/3/2018 6:21 PM, Matthew Knepley wrote:
On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng > wrote:
Hi,
I'm running a CFD code which solves the momentum and Poisson eqns.
Due to poor scaling with HYPRE at higher cpu no., I decided to
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
> On Mar 15, 2018, at 1:51 AM, TAY wee-beng wrote:
>
> Hi,
>
> I'm running a CFD code which solves the momentum and Poisson eqns.
>
> Due to poor scaling with HYPRE at higher cpu no., I decided to try using
>
On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng wrote:
> Hi,
>
> I'm running a CFD code which solves the momentum and Poisson eqns.
>
> Due to poor scaling with HYPRE at higher cpu no., I decided to try using
> PETSc with boomeramg and gamg.
>
> I tested for some small cases and
On Thu, Mar 15, 2018 at 3:51 PM, TAY wee-beng wrote:
> Hi,
>
> I'm running a CFD code which solves the momentum and Poisson eqns.
>
> Due to poor scaling with HYPRE at higher cpu no., I decided to try using
> PETSc with boomeramg and gamg.
>
> I tested for some small cases and
Hi,
I'm running a CFD code which solves the momentum and Poisson eqns.
Due to poor scaling with HYPRE at higher cpu no., I decided to try using
PETSc with boomeramg and gamg.
I tested for some small cases and it work well. However, for the large
problem which has poor scaling, it gives an
14 matches
Mail list logo