probably want to screen out faces between two ghost cells. There is a
>> DMLabel for doing that.
>>
>> 3) A PetscSection just gives the data layout over a mesh. The idea here
>> is to make it describe _exactly_ the layout you already have.
>> The DMGetGlobalVector() a
Thanks Matthew,
Yes, I will give it a try thid evening.
Thak you very much!
On Wed, 29 May 2019, 11:32 Matthew Knepley, wrote:
> On Wed, May 29, 2019 at 3:07 AM Edoardo alinovi via petsc-users <
> petsc-users@mcs.anl.gov> wrote:
>
>> Dear PETSc friends,
>>
>
Hello Mark,
Yes, there are 5 KSP calls within a time-step (3 for the solution of
momentum equation + 2 for the solution of pressure), this is the classical
non iterative PISO by Issa ( the exact sequence of operations is : solve
momentum implicitly, solve pressure-correction, momentum explicitly,
Dear Hong and Matt,
thank you for your kind replay. I have just tested your suggestions and
applied " -sub_pc_type ilu -sub_pc_factor_mat_ordering_type nd/rcm" and, in
both cases, I have found a deterioration of performances with respect to
doing nothing (thus just putting default PCBJACOBI). Is
Dear users,
I have a question about the correct use of the option
"PCFactorSetMatOrderingType" in PETSc.
I am solving a problem with 2.5M of unknowns distributed along 16
processors and I am using the block jacobi preconditioner and MPIAIJ
matrix format. I cannot figure out if the above option c