MPICH folks confirmed it's an MPICH problem and an issue is created at
https://github.com/pmodels/mpich/issues/6843
--Junchao Zhang
On Tue, Dec 12, 2023 at 7:53 PM Junchao Zhang
wrote:
> I was able to reproduce it. Let me ask MPICH developers.
>
> --Junchao Zhang
>
>
> On Tue, Dec 12, 2023 at
did you mean to write
type (userctx) ctx
in this example?
subroutine func(snes, x, f, ctx, ierr)
SNES snes
Vec x,f
type (userctx) user
PetscErrorCode ierr
...
external func
SNESSetFunction(snes, r, func, ctx, ierr)
SNES snes
Vec r
PetscErrorCode ierr
type (userctx) user
On Tue, Dec 1
See
https://petsc.gitlab.io/-/petsc/-/jobs/5739238224/artifacts/public/html/manual/fortran.html#ch-fortran
and https://gitlab.com/petsc/petsc/-/merge_requests/7114
> On Dec 12, 2023, at 3:22 PM, Palmer, Bruce J via petsc-users
> wrote:
>
> What do you do with something like a void pointer?
I was able to reproduce it. Let me ask MPICH developers.
--Junchao Zhang
On Tue, Dec 12, 2023 at 3:06 PM Randall Mackie
wrote:
> It now seems to me that petsc+mpich is no longer valgrind clean, or I am
> doing something wrong.
>
> A simple program:
>
>
> Program test
>
> #include "petsc/fincl
On Tue, Dec 12, 2023 at 7:28 PM MIGUEL MOLINOS PEREZ wrote:
> I meant the list of atoms which lies inside of a sphere of radius R_cutoff
> centered at the mean position of a given atom.
>
Okay, this is possible in parallel, but would require hard work and I have
not done it yet, although I think
On Tue, Dec 12, 2023 at 7:13 PM Sharan Roongta wrote:
> Thanks for the clarification.
> However, would it be more consistent to differentiate between 0D (vertex
> sets), 1D (edge sets), 2d (faces) and 3D (cell sets)?
> If I want to now apply boundary condition on a face with tag 1, it would
> con
Thanks for the clarification.
However, would it be more consistent to differentiate between 0D (vertex sets),
1D (edge sets), 2d (faces) and 3D (cell sets)?
If I want to now apply boundary condition on a face with tag 1, it would
contain the 4 edges making up that face and an additional edge wit
On Tue, Dec 12, 2023 at 5:50 PM Sharan Roongta wrote:
> Hello,
>
> I see discrepancy in the size/value of the 'Face Sets' printed in the
> current release v3.20.2 , and v3.18.6
>
> Attached is the .msh file
>
> -dm_view with v3.18.6
> DM Object: Generated Mesh 1 MPI process
> type: plex
> Gener
On Tue, Dec 12, 2023 at 12:22 PM onur.notonur via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Hi,
>
> I hope this email finds you well. I am currently working on importing an
> OpenFOAM PolyMesh into DMPlex, and I've encountered an issue. The PolyMesh
> format includes face owner cells/neighbo
On Tue, Dec 12, 2023 at 12:23 PM Brandon Denton via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Good Afternoon,
>
> I am currently working on an Inviscid Navier-Stokes problem and would like
> to apply DM_BC_NATURAL boundary conditions to my domain. Looking through
> the example files on petsc
Hello,
I see discrepancy in the size/value of the 'Face Sets' printed in the current
release v3.20.2 , and v3.18.6
Attached is the .msh file
-dm_view with v3.18.6
DM Object: Generated Mesh 1 MPI process
type: plex
Generated Mesh in 3 dimensions:
Number of 0-cells per rank: 14
Number of
It now seems to me that petsc+mpich is no longer valgrind clean, or I am doing
something wrong.
A simple program:
Program test
#include "petsc/finclude/petscsys.h"
use petscsys
PetscInt :: ierr
call PetscInitialize(PETSC_NULL_CHARACTER,ierr)
call PetscFinalize(ierr)
end program
What do you do with something like a void pointer? I’m looking at the
TaoSetObjectiveAndGradient function and it wants to pass a void *ctx pointer.
You can set this to null, but apparently you have to specify the type. What
type should I use? Is there something called PETSC_NULL_VOID or
PETSC_N
I think having a link to your fortran interface page on the C/Fortran API tab
is probably sufficient, particularly if the interfaces are similar. If
functions have significant differences between C and Fortran, it would be
helpful if the notes about it are on the page describing the function.
I
Good Afternoon,
I am currently working on an Inviscid Navier-Stokes problem and would like to
apply DM_BC_NATURAL boundary conditions to my domain. Looking through the
example files on petsc.org, I noticed that in almost all cases there are the
following series of calls.
PetscCall(DMAddBoundar
Hi,
I hope this email finds you well. I am currently working on importing an
OpenFOAM PolyMesh into DMPlex, and I've encountered an issue. The PolyMesh
format includes face owner cells/neighbor cells and face-to-vertex
connectivity. I was using the "DMPlexCreateFromCellListPetsc()" function, wh
I agree with Bruce that having a link to
https://petsc.org/release/manual/fortran/ at the top of the C/Fortran
API page (https://petsc.org/release/manualpages/) would be helpful.
The C descriptions themselves are 98% of the way there for Fortran users
(like myself). The only time that more i
It is unlikely we will ever be able to maintain full manual pages for Fortran
for all routines. But yes, the current pages are C-centric.
Do you have any suggestions on what we could add to the current manual pages
or how to format them etc that would make them better for Fortran users who
Thanks! It might be useful if there were a link to this page near the top of
the C/Fortran API page.
Bruce
From: Matthew Knepley
Date: Tuesday, December 12, 2023 at 8:33 AM
To: Palmer, Bruce J
Cc: petsc-users@mcs.anl.gov
Subject: Re: [petsc-users] Fortran Interface
Check twice before you clic
On Tue, Dec 12, 2023 at 11:27 AM Palmer, Bruce J via petsc-users <
petsc-users@mcs.anl.gov> wrote:
> Does documentation for the PETSc fortran interface still exist? I looked
> at the web pages for 3.20 (petsc.org/release) but if you go under the tab
> C/Fortran API, only descriptions for the C int
Does documentation for the PETSc fortran interface still exist? I looked at the
web pages for 3.20 (petsc.org/release) but if you go under the tab C/Fortran
API, only descriptions for the C interface are there.
Bruce Palmer
21 matches
Mail list logo
