Thanks, Barry. It works!
Best,
Changqing
发件人: Barry Smith
发送时间: 2025年3月25日 3:18
收件人: Ye Changqing
抄送: Mark Adams; petsc-users@mcs.anl.gov
主题: Re: [petsc-users] Floating point exception when save complex vector into a
hdf5 file
Please switch to the m
Problem solved. I my haste clean up the code, I messed up the
definition of by rhs values. b(:) instead of b(*).
The conversion to the main branch seems to be complete and all my test
cases seem to work correctly now.
-
On 3/24/25 3:26 PM, Sanjay Govindjee wrote:
My odessy to update my code
My odessy to update my code to the main branch continues...I am now
encountering an error with VecSetValue:
[0]PETSC ERROR: VecSetValues() at
/Users/sg/petsc-3.22.4main/src/vec/vec/interface/rvector.c:926 Null
Pointer: Parameter # 4
This is on a single processor run -- I got tired of c
Thanks! I look forward to seeing the Change Note :)
Time now to perform some search and destroy through the code!
-sanjay
---
Sanjay Govindjee, PhD, PE
Horace, Dorothy, and Katherine Johnson Professor in Engineering
Distinguished Pr
Please switch to the main git branch of PETSc and try again. Some of the
code has been updated to handle the very large arrays you are working with.
Barry
> On Mar 24, 2025, at 7:57 AM, Ye Changqing wrote:
>
> Dear Mark,
>
> As suggested, I did a fresh configuration on PETSc. The pr
Ahh, you cannot use this type of construct
if (x .eq. PETSC_NULL_XXX) then
anymore.
Nor can you ever assign x = PETSC_NULL_
Instead use
if (PetscObjectIsNull(x)) then
or
if (.not. PetscObjectIsNull(x)) then
Also all PETSc objects are now null when they
I checked also that this is the first time that this part of the code is
entered. Before the call to MatCreate, all processes
are reporting Kmat is 0 (as is PETSC_NULL_MAT). All have the same
PETSC_COMM_WORLD of 0.
-
On 3/24/25 8:14 AM, Sanjay Govindjee wrote:
Hi Barry,
The call sequence ha
I take on item back...I was a failure at using the debugger. Here is
the backtrace. MatCreate seems to have valid data :/
* thread #1, queue = 'com.apple.main-thread', stop reason = signal
SIGSTOP
* frame #0: 0x7fff69d92746
libsystem_kernel.dylib`__semwait_signal + 10
Hi Barry,
The call sequence happens across several routines. I believe it is as
follows:
call PetscInitialize(PETSC_NULL_CHARACTER, ierr)
call MPI_Comm_rank(PETSC_COMM_WORLD, rank, ierr)
call MPI_Comm_size(PETSC_COMM_WORLD, ntasks, ierr)
Kmat = PETSC_NULL_MAT
i
How do you declare and initialize the matrix in usolve.F before calling
MatCreate()? You should not initialize it with any value before the call.
Barry
> On Mar 23, 2025, at 11:10 PM, Sanjay Govindjee via petsc-users
> wrote:
>
> Barry,
>
> I now have a compiled version of my code
Just to check, you want to delete the linux-oneapi-complex-opt directory
and do a fresh build when you get errors like this and you might send your
configure log.
Mark
On Mon, Mar 24, 2025 at 5:22 AM Ye Changqing
wrote:
> Dear all,
>
> I reconfigured petsc with "--with-debugging=1". It throws mo
Dear all,
I reconfigured petsc with "--with-debugging=1". It throws more messages which I
attached below.
Best,
Changqing
发件人: Ye Changqing
发送时间: 2025年3月24日 16:33
收件人: petsc-users@mcs.anl.gov
主题: Floating point exception when save complex vector into a
Dear PETSc developers,
I encountered a strange problem when I tried to save a DMDA vector into an hdf5
file, a floating point error was thrown. I can repeat the problem on the
cluster. However, the same codes run fine on my local computer.
Below the .cxx file is the minimal working example, the
13 matches
Mail list logo
