Re: [petsc-users] PetscViewer with 64bit

2023-02-17 Thread Mike Michell
It works as I wanted. Thank you for the change. Mike > Okay, this works now. I'm pretty sure I tested this long ago with > connectivity using Int64 and found that didn't work. That may have been > ancient history, but I'm hesitant to revamp to match PetscInt. If doing > that, it would require

Re: [petsc-users] PetscViewer with 64bit

2023-02-16 Thread Jed Brown
Okay, this works now. I'm pretty sure I tested this long ago with connectivity using Int64 and found that didn't work. That may have been ancient history, but I'm hesitant to revamp to match PetscInt. If doing that, it would require changing the signature of DMPlexGetVTKConnectivity to use

Re: [petsc-users] PetscViewer with 64bit

2023-02-16 Thread Mike Michell
Jed, It does not work for me even with the reproducer case with the small 2D square mesh. Can you run the case that I sent and open the created "sol.vtu" file with paraview? Thanks, > Thanks, Dave. > > Mike, can you test that this branch works with your large problems? I > tested that .vtu

Re: [petsc-users] PetscViewer with 64bit

2023-02-16 Thread Jed Brown
Thanks, Dave. Mike, can you test that this branch works with your large problems? I tested that .vtu works in parallel for small problems, where works = loads correctly in Paraview and VisIt. https://gitlab.com/petsc/petsc/-/merge_requests/6081 Dave May writes: > On Tue 14. Feb 2023 at

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Dave May
On Tue 14. Feb 2023 at 21:27, Jed Brown wrote: > Dave May writes: > > > On Tue 14. Feb 2023 at 17:17, Jed Brown wrote: > > > >> Can you share a reproducer? I think I recall the format requiring > certain > >> things to be Int32. > > > > > > By default, the byte offset used with the appended

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Jed Brown
Dave May writes: > On Tue 14. Feb 2023 at 17:17, Jed Brown wrote: > >> Can you share a reproducer? I think I recall the format requiring certain >> things to be Int32. > > > By default, the byte offset used with the appended data format is UInt32. I > believe that’s where the sizeof(int) is

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Dave May
On Tue 14. Feb 2023 at 21:03, Dave May wrote: > > > On Tue 14. Feb 2023 at 17:17, Jed Brown wrote: > >> Can you share a reproducer? I think I recall the format requiring certain >> things to be Int32. > > > By default, the byte offset used with the appended data format is UInt32. > I believe

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Dave May
On Tue 14. Feb 2023 at 17:17, Jed Brown wrote: > Can you share a reproducer? I think I recall the format requiring certain > things to be Int32. By default, the byte offset used with the appended data format is UInt32. I believe that’s where the sizeof(int) is coming from. This default is

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Jed Brown
Can you share a reproducer? I think I recall the format requiring certain things to be Int32. Mike Michell writes: > Thanks for the note. > I understood that PETSc calculates the offsets for me through "boffset" > variable in plexvtu.c file. Please correct me if it is wrong. > > If plexvtu.c

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Mike Michell
Thanks for the note. I understood that PETSc calculates the offsets for me through "boffset" variable in plexvtu.c file. Please correct me if it is wrong. If plexvtu.c has a bug, it could be around "write file header" part in which the boffset is also computed. Is this correct? I am not using

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Matthew Knepley
On Tue, Feb 14, 2023 at 11:45 AM Mike Michell wrote: > I was trying to modify the header flags from "Int32" to "Int64", but the > problem was not resolved. Could I get any additional comments? > The calculated offsets are not correct I think. Matt > Thanks, > Mike > > >> Thanks for the

Re: [petsc-users] PetscViewer with 64bit

2023-02-14 Thread Mike Michell
I was trying to modify the header flags from "Int32" to "Int64", but the problem was not resolved. Could I get any additional comments? Thanks, Mike > Thanks for the comments. > To be precise on the question, the entire part of the header of the .vtu > file is attached: > > > > > >

Re: [petsc-users] PetscViewer with 64bit

2023-02-12 Thread Mike Michell
Thanks for the comments. To be precise on the question, the entire part of the header of the .vtu file is attached:

Re: [petsc-users] PetscViewer with 64bit

2023-02-12 Thread Matthew Knepley
On Sun, Feb 12, 2023 at 6:15 PM Mike Michell wrote: > Dear PETSc team, > > I am a user of PETSc with Fortran. My code uses DMPlex to handle dm > object. To print out output variable and mesh connectivity, I use VecView() > by defining PetscSection on that dm and borrow a vector. The type of the

[petsc-users] PetscViewer with 64bit

2023-02-12 Thread Mike Michell
Dear PETSc team, I am a user of PETSc with Fortran. My code uses DMPlex to handle dm object. To print out output variable and mesh connectivity, I use VecView() by defining PetscSection on that dm and borrow a vector. The type of the viewer is set to PETSCVIEWERVTK. With 32bit indices, the above