> On Apr 8, 2018, at 7:17 PM, Rongliang Chen wrote:
>
> Thanks Barry. I will try it but it seems highly nontrivial.
The first time you do it it seems overwhelming but once you get the hang of
it it is actually pretty simple and very powerful. Much better
than
Thanks Barry. I will try it but it seems highly nontrivial.
Best,
Rongliang
On 04/08/2018 11:18 PM, Smith, Barry F. wrote:
On Apr 7, 2018, at 11:03 PM, Rongliang Chen wrote:
Hi Barry,
I tried the petsc-3.7.7 and my code works fine. Any suggestions for debug this?
> On Apr 7, 2018, at 11:03 PM, Rongliang Chen wrote:
>
> Hi Barry,
>
> I tried the petsc-3.7.7 and my code works fine. Any suggestions for debug
> this? Thanks.
Works for 3.7.7 but not 3.8? I'm afraid you'll need to use git bisect, this
will tell you exactly
Hi Barry,
I tried the petsc-3.7.7 and my code works fine. Any suggestions for
debug this? Thanks.
Best,
Rongliang
On 04/08/2018 11:22 AM, Smith, Barry F. wrote:
On Apr 7, 2018, at 10:11 PM, Rongliang Chen wrote:
Thanks Barry! I created the
> On Apr 7, 2018, at 10:11 PM, Rongliang Chen wrote:
>
> Thanks Barry! I created the ISLocalToGlobalMapping after I loaded in the mesh
> and before the matrix creation. The block size for the
> ISLocalToGlobalMappingCreate is 7. In my code, the mapping is already in
Thanks Barry! I created the ISLocalToGlobalMapping after I loaded in the
mesh and before the matrix creation. The block size for the
ISLocalToGlobalMappingCreate is 7. In my code, the mapping is already in
the form that one number per block since the petsc-3.6 requests this. So
when I updated
Hi Barry,
Thanks for your reply. I checked the isrow with ISView (see bellow for
the output) and I found that the output of the 3.6 (output-3.6.txt) and
3.8 (output-3.8.txt) are totally different. I do not know why. By the
way, the block size of my code should be 7 but the output of the isrow
For BAIJ matrices with ASM preconditioner the index sets that define the ASM
blocks must contain all the points in a block or none of them. The code is
detecting this is not the case; I don't know why this would be different
between 3.8 and 3.6
You can use the option -start_in_debugger