Older versions of PETSc have generally less error checking and debug
versions have more error checking than optimized version. Once you update the
code for newer versions it should work clearly for both debug and optimized
versions of PETSc.
Barry
> On Jun 24, 2023, at 12:08 PM, Paweł S
Look for places where you call VecSetValues(), make sure that after the call
before you use the vector for some other use you call
VecAssemblyBegin/VecAssemblyEnd
> On Jun 23, 2023, at 6:57 PM, Paweł Stebliński wrote:
>
> I'm using petsc 3.19.2 --with-debuging=yes (generated executable a li
Search through all your code looking for calls to
VecGetArray()/VecRestoreArray(). For all uses where you only need to read from
the array, replace
the calls with VecGetArrayRead()/VecRestoreArrayRead(). And add the const
modifier to the array declaration.
> On Jun 24, 2023, at 5:32 AM,
Could you send us the exact error output that occurs? Cut and paste the run
command and the entire error message.
Also send the configure options you used. Have you tried configuring the
later PETSc versions with all optimization turned off; use --with-debugging=1
--with-cflags='-g -O0'
I am micromagnetic (MAGPAR) software developer. Old Magpar version has
been using petsc 3.1-p8. I have decided to upgrade to petsc 3.19.2 with
avx512 support. Unfortunately there appeared an error during software
testing. Error appeares in ranning code after proper compiling and
linking. The bu
