hi Matt & all,
I just had a query from one of my users which prompted me to see if any
progress had been made on the issue below - using PETSc to get the
number of time steps in an HDF5 file.
I can't see anything new in PETSc on this - I did try using
PetscViewerHDF5ReadSizes() to see if
unsubscribe
"You know the number of cells if you can read connectivity. Do you mean that
the format does not tell you
the number of vertices?"
Sort of...
So, the format does provide the number of vertices, however, due to the way I
read the data in parallel I don't know immediately how many local vertices
On Wed, May 1, 2024 at 4:23 PM Ferrand, Jesus A.
wrote:
> Matt:
>
> My bad again, I need to clarify something that I just realized doesn't
> make sense.
> I said: "The nature of the I/O makes it so that I need to read the
> connectivity before I get a semblance of buffer sizes."
> Scratch that,
Matt:
My bad again, I need to clarify something that I just realized doesn't make
sense.
I said: "The nature of the I/O makes it so that I need to read the connectivity
before I get a semblance of buffer sizes."
Scratch that, obviously, if I can read the connectivity, I know the buffer
sizes.
Matt:
"I do not understand the "flag check". What is that?"
My bad, I should have referred to the "dm->setupcalled".
I believe this PetscBool is checked by the other DM (not just DMPlex)
APIs.
The subsequent checks for dm->setupcalled == PETSC_TRUE is what I meant
to say.
On Wed, May 1, 2024 at 3:34 PM Ferrand, Jesus A.
wrote:
> Dear PETSc team: For a project that I'm working on, I need to manually
> build a DMPlex. From studying the source code of the various APIs in which
> the plex is built from some supported file format, I get that the workflow
> is this:
Dear PETSc team:
For a project that I'm working on, I need to manually build a DMPlex.
>From studying the source code of the various APIs in which the plex is built
>from some supported file format, I get that the workflow is this:
1.
DMPlexSetChart() <-- Input nCells + nVerts
2.
Hi Satish,
Many thanks for the interesting response. I'll see if I can figure out
something useful to do for our goals (a reliable spack package for our
simulator, which is dependent on bringing in
the exact right petsc build as dependency), but as you say, maintaining
these things and accounting
