May 2023 - petsc-users - mailman3.cels.anl.gov

How to combine different element types into a single DMPlex?
by Eric Chamberland 01 Aug '24

01 Aug '24

Hi, while playing with DMPlexBuildFromCellListParallel, I noticed we have to specify "numCorners" which is a fixed value, then gives a fixed number of nodes for a series of elements. How can I then add, for example, triangles and quadrangles into a DMPlex? Thanks, Eric -- Eric Chamberland, ing., M. Ing Professionnel de recherche GIREF/Université Laval (418) 656-2131 poste 41 22 42

4 13

HDF5 corruption
by Adrian Croucher 13 May '24

13 May '24

hi, One of the users of my PETSc-based code has reported that HDF5 output files can be corrupted and unusable if e.g. the run is killed. I've just done a bit of reading about this and it appears to be a known issue with HDF5. Some people suggest flushing the HDF5 file periodically to help prevent data loss. I had a look at PetscViewerFlush() but it doesn't seem to be implemented for the HDF5 viewer- is that correct? I am currently calling PetscViewerHDF5Open() once at the start of the run and closing it at the end. Some other people suggest doing this before and after each write instead. Is there likely to be a significant performance penalty in doing that? I gather HDF5 journaling has been promised for a while to get around this problem but as far as I can see it hasn't materialised yet... Regards, Adrian -- Dr Adrian Croucher Senior Research Fellow Department of Engineering Science University of Auckland, New Zealand email: a.croucher(a)auckland.ac.nz tel: +64 (0)9 923 4611

4 17

Fortran Interface NULL object / Casting
by Nicholas Arnold-Medabalimi 23 Feb '24

23 Feb '24

Hi Petsc Users I am trying to use DMAddField in a Fortran code. I had some questions on casting/passing NULL. I follow how to pass NULL for standard types (INT, CHAR, etc). Is there a method/best practice for passing NULL for Petsc type arguments? (In this case DMAddLabel I'd want to pass NULL to a DMLabel Parameter not an intrinsic type) For the 2nd question, In some cases in C we would cast a more specific object to Petsc Object DMAddField(dm, NULL, (PetscObject)fvm); (where fvm is a PetscFVM type) Is there a method or practice to do the same in Fortran. Thanks Nicholas -- Nicholas Arnold-Medabalimi Ph.D. Candidate Computational Aeroscience Lab University of Michigan

3 2

Scalable Solver for Incompressible Flow
by Blauth, Sebastian 31 Jul '23

31 Jul '23

Hello, I am having a problem using / configuring PETSc to obtain a scalable solver for the incompressible Navier Stokes equations. I am discretizing the equations using FEM (with the library fenics) and I am using the stable P2-P1 Taylor-Hood elements. I have read and tried a lot regarding preconditioners for incompressible Navier Stokes and I am aware that this is very much an active research field, but maybe I can get some hints / tips. I am interested in solving large-scale 3D problems, but I cannot even set up a scaleable 2D solver for the problems. All of my approaches at the moment are trying to use a Schur Complement approach, but I cannot get a good preconditioner for the Schur complement matrix. For the velocity block, I am using the AMG provided by hypre (which seems to work fine and is most likely not the problem). To test the solver, I am using a simple 2D channel flow problem with do-nothing conditions at the outlet. I am facing the following difficulties at the moment: - First, I am having trouble with using -pc_fieldsplit_schur_precondition selfp. With this setup, the cost for solving the Schur complement part in the fieldsplit preconditioner (approximately) increase when the mesh is refined. I am using the following options for this setup (note that I am using exact solves for the velocity part to debug, but using, e.g., gmres with hypre boomeramg reaches a given tolerance with a number of iterations that is independent of the mesh) -ksp_type fgmres -ksp_rtol 1e-6 -ksp_atol 1e-30 -pc_type fieldsplit -pc_fieldsplit_type schur -pc_fieldsplit_schur_fact_type full -pc_fieldsplit_schur_precondition selfp -fieldsplit_0_ksp_type preonly -fieldsplit_0_pc_type lu -fieldsplit_1_ksp_type gmres -fieldsplit_1_ksp_pc_side right -fieldsplit_1_ksp_max_it 1000 -fieldsplit_1_ksp_rtol 1e-1 -fieldsplit_1_ksp_atol 1e-30 -fieldsplit_1_pc_type lu -fieldsplit_1_ksp_converged_reason -ksp_converged_reason Note, that I use direct solvers for the subproblems to get an ideal convergence. Even if I replace the direct solver with boomeramg, the behavior is the same and the number of iterations does not change much. In particular, I get the following behavior: For a 8x8 mesh, I need, on average, 25 iterations to solve fieldsplit_1 For a 16x16 mesh, I need 40 iterations For a 32x32 mesh, I need 70 iterations For a 64x64 mesh, I need 100 iterations However, the outer fgmres requires, as expected, always the same number of iterations to reach convergence (as expected). I do understand that the selfp preconditioner for the Schur complement is expected to deteriorate as the Reynolds number increases and the problem becomes more convective in nature, but I had hoped that I can at least get a scaleable preconditioner with respect to the mesh size out of it. Are there any tips on how to achieve this? My second problem is concerning the LSC preconditioner. When I am using this, again both with exact solves of the linear problems or when using boomeramg, I do not get a scalable solver with respect to the mesh size. On the contrary, here the number of solves required for solving fieldsplit_1 to a fixed relative tolerance seem to behave linearly w.r.t. the problem size. For this problem, I suspect that the issue lies in the scaling of the LSC preconditioner matrices (in the book of Elman, Sylvester and Wathen, the matrices are scaled with the inverse of the diagonal velocity mass matrix). Is it possible to achieve this with PETSc? I started experimenting with supplying the velocity mass matrix as preconditioner matrix and using use_amat, but I am not sure where / how to do it this way. And finally, more of an observation and question: I noticed that the AMG approximations for the velocity block became worse with increase of the Reynolds number when using the default options. However, when using -pc_hypre_boomeramg_relax_weight_all 0.0 I noticed that boomeramg performed way more robustly w.r.t. the Reynolds number. Are there any other ways to improve the AMG performance in this regard? Thanks a lot in advance and I am looking forward to your reply, Sebastian -- Dr. Sebastian Blauth Fraunhofer-Institut für Techno- und Wirtschaftsmathematik ITWM Abteilung Transportvorgänge Fraunhofer-Platz 1, 67663 Kaiserslautern Telefon: +49 631 31600-4968 sebastian.blauth(a)itwm.fraunhofer.de https://www.itwm.fraunhofer.de

7 27

TS failed due to diverged_step_rejected
by Tu, Jiannan 09 Jun '23

09 Jun '23

My code uses TS to solve a set of multi-fluid MHD equations. The jacobian is provided with function F(t, u, u'). Both linear and nonlinear solvers converge but snes repeats itself until gets "TSStep has failed due to diverged_step_rejected." Is it because I used TSStep rather than TSSolve? I have checked the condition number. The condition number with pc_type asm is about 1 (without precondition it is about 4x10^4). The maximum ratio of off-diagonal jacobian element over diagonal element is about 21. Could you help me to identify what is going wrong? Thank you very much! Jiannan --------------------------------------------------------------------------------------------------- Run command with options mpiexec -n $1 ./iditm3d -ts_type arkimex -snes_tyep ngmres -ksp_type gmres -pc_type asm \ -ts_rtol 1.0e-4 -ts_atol 1.0e-4 -snes_monitor -snes_rtol 1.0e-4 -snes_atol 1.0e-4 \ -snes_converged_reason The output message is Start time advancing ... 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 1.673091274668e-03 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 8.715428433630e-02 1 SNES Function norm 4.995727626692e-04 2 SNES Function norm 5.498018152230e-08 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 2 0 SNES Function norm 3.237461568254e-01 1 SNES Function norm 7.988531005091e-04 2 SNES Function norm 1.280948196292e-07 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 2 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 4.881903203545e-04 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 7.562592690785e-02 1 SNES Function norm 1.143078818923e-04 2 SNES Function norm 9.834547907735e-09 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 2 0 SNES Function norm 2.683968949758e-01 1 SNES Function norm 1.838028436639e-04 2 SNES Function norm 9.470813523140e-09 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 2 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 1.821562431175e-04 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 1.005443458812e-01 1 SNES Function norm 3.633336946661e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 1.515368382715e-01 1 SNES Function norm 3.389298316830e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 4.541003359206e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 1.713800906043e-01 1 SNES Function norm 1.179958172167e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.020265094117e-01 1 SNES Function norm 1.513971290464e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 6.090269704320e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.136603895703e-01 1 SNES Function norm 1.877474016012e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 3.127812462507e-01 1 SNES Function norm 2.713146825704e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 2.793512213059e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.205196267430e-01 1 SNES Function norm 2.572653773308e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 3.260057361977e-01 1 SNES Function norm 2.705816087598e-06 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 2.764855860446e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.212505522844e-01 1 SNES Function norm 2.958996472386e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 3.273222034162e-01 1 SNES Function norm 2.994512887620e-05 Nonlinear solve converged due to CONVERGED_FNORM_ABS iterations 1 0 SNES Function norm 2.274473072186e+03 1 SNES Function norm 3.317240589134e-04 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 2.213246532918e-01 1 SNES Function norm 2.799468604767e-04 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 3.274570888397e-01 1 SNES Function norm 3.066048050994e-04 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 2.274473072189e+03 1 SNES Function norm 2.653507278572e-03 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 2.213869585841e-01 1 SNES Function norm 2.177156902895e-03 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 3.275136370365e-01 1 SNES Function norm 1.962849131557e-03 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 2.274473072218e+03 1 SNES Function norm 5.664907315679e-03 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 2.223208399368e-01 1 SNES Function norm 5.688863091415e-03 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 3.287121218919e-01 1 SNES Function norm 4.085338521320e-03 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 2.274473071968e+03 1 SNES Function norm 4.694691905235e-04 Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 1 0 SNES Function norm 2.211786508657e-01 1 SNES Function norm 1.503497433939e-04 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 0 SNES Function norm 3.272667798977e-01 1 SNES Function norm 2.176132327279e-04 Nonlinear solve converged due to CONVERGED_SNORM_RELATIVE iterations 1 [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: [0]PETSC ERROR: TSStep has failed due to DIVERGED_STEP_REJECTED [0]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting. [0]PETSC ERROR: Petsc Release Version 3.16.6, Mar 30, 2022 [0]PETSC ERROR: ./iditm3d on a named office by jtu Fri Feb 17 11:59:43 2023 [0]PETSC ERROR: Configure options --prefix=/usr/local --with-mpi-dir=/usr/local --with-fc=0 --with-openmp --with-hdf5-dir=/usr/local --download-f2cblaslapack=1 [0]PETSC ERROR: #1 TSStep() at /home/jtu/Downloads/petsc-3.16.6/src/ts/interface/ts.c:3583

5 26

Petsc ObjectStateIncrease without proivate header
by Pichler, Franz 06 Jun '23

06 Jun '23

Hello, i am using petsc in a single cpu setup where I have preassembled crs matrices that I wrap via PetSC's MatCreateSeqAIJWithArrays Functionality. Now I manipulate the values of these matrices (wohtout changing the sparsity) without using petsc, When I now want to solve again I have to call PetscObjectStateIncrease((PetscObject)petsc_A); So that oetsc actually solves again (otherwise thinking nothing hs changed , This means I have to include the private header #include <petsc/private/petscimpl.h> Which makes a seamingless implementation of petsc into a cmake process more complicate (This guy has to be stated explicitly in the cmake process at the moment) I would like to resolve that by "going" around the private header, My first intuition was to increase the state by hand ((PetscObject)petsc_A_aux[the_sys])->state++; This is the definition of petscstateincrease in the header. This throws me an error: invalid use of incomplete type 'struct _p_PetscObject' compilation error. Is there any elegeant way around this? This is the first time I use the petsc mailing list so apologies for any beginners mistake I did in formatting or anything else. Best regards Franz Pichler

2 2

Using SNESSHELL as a wrapper for a CFD solver.
by Kenneth C Hall 31 May '23

31 May '23

Hi, I am doing a number of problems using PETSc/SLEPc, but I also work on some non-PETSc/SLEPc flow solvers. I would like to use PETSc as a wrapper for this non-PETSc flow solver for compatibility, so I can use the tolerance monitoring, options, viewers, and for direct comparison to PETSc methods I am using. Here is what I am trying to do… I have a CFD solver that iterates with a nonlinear iterator of the form x := N(x). This can be expressed in a fortran routine of the form, SUBROUTINE MySolver(x) or SUBROUTINE MySolver(x,y) In the first case, x is over written. In the second, y = N(x). In any event, I want to do something like what is shown in the subroutine at the bottom of this email. The code below “works” in the sense that MySolver is called, but it is called exactly *once*. But MyMonitor and MyConverged are *not* called. Again, I want to iterate so MySolver should be called many times, as should MyMonitor and MyConverged. The SNESView before and after SNESSolve looks like this: SNES Object: 1 MPI process type: shell SNES has not been set up so information may be incomplete maximum iterations=50, maximum function evaluations=10000 tolerances: relative=1e-50, absolute=1e-10, solution=1e+06 total number of function evaluations=0 norm schedule ALWAYS SNES Object: 1 MPI process type: shell maximum iterations=50, maximum function evaluations=10000 tolerances: relative=1e-50, absolute=1e-10, solution=1e+06 total number of function evaluations=0 norm schedule ALWAYS Any suggestions on how to do what I am trying to accomplish? Thanks. Kenneth Hall #include <petsc/finclude/petsc.h> #include "macros.h" MODULE SolveWithSNESShell_module USE MyPetscModule CONTAINS ! !==================================================================================================== SUBROUTINE MySolver(snes, x, ierr) !==================================================================================================== !! !! !==================================================================================================== ! USE MyPetscModule IMPLICIT NONE ! !.... declared passed variables SNES :: snes Vec :: x PetscErrorCode :: ierr ! !.... code to find residual x := N(x) !.... (or alternatively y := N(x)) END SUBROUTINE MySolver ! !==================================================================================================== SUBROUTINE MyMonitor(snes, its, rnorm, ierr) !==================================================================================================== !! !! !==================================================================================================== ! USE MyPetscModule IMPLICIT NONE ! !.... Declare passed variables SNES :: snes PetscInt :: its PetscReal :: rnorm PetscErrorCode :: ierr ! !.... Code to print out convergence history !.... Code to print out convergence history END SUBROUTINE MyMonitor !==================================================================================================== SUBROUTINE MyConverged(snes, it, xnorm, ynorm, znorm, reason, ierr) USE MyPetscModule IMPLICIT NONE SNES :: snes PetscInt :: it,ctx PetscReal :: xnorm, ynorm, znorm KSPConvergedReason :: reason PetscErrorCode :: ierr ! ... add convergence test here ... ! set reason to a positive value if convergence has been achieved END SUBROUTINE MyConverged END MODULE SolveWithSNESShell_module ! !==================================================================================================== SUBROUTINE SolveWithSNESShell !==================================================================================================== !! !! !==================================================================================================== ! USE SolveWithSNESShell_module IMPLICIT NONE ! !.... Declare passed variables INTEGER :: level_tmp ! !.... Declare local variables INTEGER :: iz INTEGER :: imax INTEGER :: jmax INTEGER :: kmax SNES :: snes KSP :: ksp Vec :: x Vec :: y PetscViewer :: viewer PetscErrorCode :: ierr PetscReal :: rtol = 1.0D-10 !! relative tolerance PetscReal :: atol = 1.0D-50 !! absolute tolerance PetscReal :: dtol = 1.0D+06 !! divergence tolerance PetscInt :: maxits = 50 PetscInt :: maxf = 10000 character(len=1000):: args ! !.... count the number of degrees of freedom. level = level_tmp n = 0 DO iz = 1, hb(level)%nzone imax = hb(level)%zone(iz)%imax - 1 jmax = hb(level)%zone(iz)%jmax - 1 kmax = hb(level)%zone(iz)%kmax - 1 n = n + imax * jmax * kmax END DO n = n * neqn ! !.... Initialize PETSc PetscCall(PetscInitialize(PETSC_NULL_CHARACTER, ierr)) ! !.... Log PetscCall(PetscLogDefaultBegin(ierr)) ! !.... Hard-wired options. ! PetscCall(PetscOptionsInsertString(PETSC_NULL_OPTIONS, "command line style option here" , ierr)) ! !.... Command line options. call GET_COMMAND(args) PetscCall(PetscOptionsInsertString(PETSC_NULL_OPTIONS, args, ierr)) ! !.... view command line table PetscCall(PetscViewerASCIIOpen(PETSC_COMM_SELF, PETSC_VIEWER_STDOUT_SELF, viewer, ierr)) PetscCall(PetscOptionsView(PETSC_NULL_OPTIONS, viewer, ierr)) PetscCall(PetscViewerDestroy(viewer, ierr)) ! !.... Create PETSc vectors PetscCall(VecCreateSeq(PETSC_COMM_SELF, n, x, ierr)) PetscCall(VecCreateSeq(PETSC_COMM_SELF, n, y, ierr)) PetscCall(VecSet(x, 0.0d0, ierr)) PetscCall(VecSet(y, 0.0d0, ierr)) !.... SNES context PetscCall(SNESCreate(PETSC_COMM_SELF, snes, ierr)) PetscCall(SNESSetType(snes, SNESSHELL, ierr)) PetscCall(SNESShellSetSolve(snes, MySolver, ierr)) !!!! PetscCall(SNESSetFunction(snes, x, MySolver, PETSC_NULL_INTEGER, ierr)) !!!! this line causes a segmentation error if uncommented. PetscCall(SNESSetConvergenceTest(snes, MyConverged, 0, PETSC_NULL_FUNCTION, ierr)) ! !.... Set SNES options PetscCall(SNESSetFromOptions(snes, ierr)) !.... Set tolerances PetscCall(SNESSetTolerances(snes, rtol, atol, dtol, maxits, maxf, ierr)) ! !.... SNES montior PetscCall(SNESMonitorSet(snes, MyMonitor, PETSC_NULL_INTEGER, PETSC_NULL_FUNCTION,ierr)) ! !.... Set the initial solution CALL HBToVecX(x) ! !.... View snes context PetscCall(SNESView(snes, viewer, ierr)) ! !.... Solve SNES problem PetscCall(SNESSolve(snes, PETSC_NULL_VEC, x, ierr)) ! !.... View snes context PetscCall(SNESView(snes, viewer, ierr)) ! !.... dump the logs ! call PetscLogDump(ierr) ! Why does this cause error ! !.... Destroy PETSc objects PetscCall(SNESDestroy(snes, ierr)) PetscCall(VecDestroy(x, ierr)) PetscCall(VecDestroy(y, ierr)) PetscCall(PetscViewerDestroy(viewer, ierr)) ! !.... Finish PetscCall(PetscFinalize(ierr)) END SUBROUTINE SolveWithSNESShell

3 8

PetscSF "One-Sided" vs. "Two-Sided"
by Ferrand, Jesus A. 31 May '23

31 May '23

Dear PETSc team: For one of my applications, I need to know which owned DAG points in a (DMPlex) are other ranks' ghosts. Say, rank-0 has some point "x" (which it owns) and it shows up in, say, rank-1 as a ghost numbered "y". Then, if I inspect the "Point" PestcSF, in rank-1 there should be a leaf for "y" that records rank-0 and the value of "x", right? However, back in rank-0, the same PetscSF has no record that "x" is "y" in rank-1 (and potentially "z","a","b",... in additional ranks). Is this what, in PetscSF terminology, is referred to as "One-Sided"? If so, I think what I am really asking is how can I obtain a "Two-Sided" version of the PointSF? Sincerely: J.A. Ferrand Embry-Riddle Aeronautical University - Daytona Beach - FL Ph.D. Candidate, Aerospace Engineering M.Sc. Aerospace Engineering B.Sc. Aerospace Engineering B.Sc. Computational Mathematics Phone: (386)-843-1829 Email(s): ferranj2(a)my.erau.edu jesus.ferrand(a)gmail.com

2 1

Multiple points constraint in parallel
by YuSh Lo 31 May '23

31 May '23

Hi, I have some multiple points constraint input as follows, A_1 a_4 B_2 b_5 C_3 c_6 each columns are stored in different IS. After dmplex distribute, they will be renumbered and distribution to certain processors. I have two questions: (1) I need both complete ISs are all the processors. Can I just do ISALLGather()? (2) Although renumbered, will the original order remain(ABC and abc)? If the number is the node number, after distribution and I do an ISALLGather() will I have the following on each processor? A_3 a_1 B_4 b_2 C_6 c_5 (I randomly renumber them) This is what I can come up with now. Is there any better way to do it? Thanks, Josh

2 5

ask for the ERROR MESSAGE
by ziming xiong 31 May '23

31 May '23

Hello, I created a code for solving the finite element method using the PCBDDC method according to ex71, but I got the following error at the end, I can't find out the cause of the error, can you tell me what the error is based on the error message? (PS. I have tried: Mat AA. PetscCall(MatConvert(A, MATAIJ, MAT_INITIAL_MATRIX, &AA)). to change the matrix type and then solve for AA, it works fine) [0]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [1]PETSC ERROR: --------------------- Error Message -------------------------------------------------------------- [0]PETSC ERROR: [1]PETSC ERROR: Error in external library Error in external library [0]PETSC ERROR: [1]PETSC ERROR: Error in query to SYEV Lapack routine 0 Error in query to SYEV Lapack routine 0 [0]PETSC ERROR: [1]PETSC ERROR: See https://petsc.org/release/faq/ for trouble shooting. See https://petsc.org/release/faq/ for trouble shooting. [0]PETSC ERROR: [1]PETSC ERROR: Petsc Development GIT revision: unknown GIT Date: unknown Petsc Development GIT revision: unknown GIT Date: unknown [0]PETSC ERROR: [1]PETSC ERROR: test_petsc_fem.exe on a arch-mswin-c-debug named lmeep-329 by XiongZiming Wed May 31 16:52:36 2023 test_petsc_fem.exe on a arch-mswin-c-debug named lmeep-329 by XiongZiming Wed May 31 16:52:36 2023 [0]PETSC ERROR: [1]PETSC ERROR: Configure options --with-cc=/cygdrive/f/post_doc_C++/petsc_new/petsc-main/lib/petsc/bin/win32fe/win_cl --with-cxx=/cygdrive/f/post_doc_C++/petsc_new/petsc-main/lib/petsc/bin/win32fe/win_cl --with-fc=0 --download-metis --with-shared-libraries=0 --with-mpi-include="[/cygdrive/c/PROGRA~2/Intel/MPI/Include,/cygdrive/c/PROGRA~2/Intel/MPI/Include/x64]" --with-mpi-lib="-L/cygdrive/c/PROGRA~2/Intel/MPI/lib/x64 msmpifec.lib msmpi.lib" --with-mpiexec=/cygdrive/c/PROGRA~1/Microsoft_MPI/Bin/mpiexec --with-blaslapack-lib="-L/cygdrive/c/PROGRA~2/Intel/oneAPI/mkl/latest/lib/intel64 mkl_intel_lp64_dll.lib mkl_sequential_dll.lib mkl_core_dll.lib" --with-64-bit-indices --with-mkl_pardiso-dir=/cygdrive/c/PROGRA~2/Intel/oneAPI/mkl/latest Configure options --with-cc=/cygdrive/f/post_doc_C++/petsc_new/petsc-main/lib/petsc/bin/win32fe/win_cl --with-cxx=/cygdrive/f/post_doc_C++/petsc_new/petsc-main/lib/petsc/bin/win32fe/win_cl --with-fc=0 --download-metis --with-shared-libraries=0 --with-mpi-include="[/cygdrive/c/PROGRA~2/Intel/MPI/Include,/cygdrive/c/PROGRA~2/Intel/MPI/Include/x64]" --with-mpi-lib="-L/cygdrive/c/PROGRA~2/Intel/MPI/lib/x64 msmpifec.lib msmpi.lib" --with-mpiexec=/cygdrive/c/PROGRA~1/Microsoft_MPI/Bin/mpiexec --with-blaslapack-lib="-L/cygdrive/c/PROGRA~2/Intel/oneAPI/mkl/latest/lib/intel64 mkl_intel_lp64_dll.lib mkl_sequential_dll.lib mkl_core_dll.lib" --with-64-bit-indices --with-mkl_pardiso-dir=/cygdrive/c/PROGRA~2/Intel/oneAPI/mkl/latest [0]PETSC ERROR: [1]PETSC ERROR: #1 PCBDDCConstraintsSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\impls\bddc\bddcprivate.c:5975 #1 PCBDDCConstraintsSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\impls\bddc\bddcprivate.c:5975 [0]PETSC ERROR: [1]PETSC ERROR: #2 PCSetUp_BDDC() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\impls\bddc\bddc.c:1659 #2 PCSetUp_BDDC() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\impls\bddc\bddc.c:1659 [0]PETSC ERROR: [1]PETSC ERROR: #3 PCSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\interface\precon.c:994 #3 PCSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\pc\interface\precon.c:994 [1]PETSC ERROR: [0]PETSC ERROR: #4 KSPSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\ksp\interface\itfunc.c:406 #4 KSPSetUp() at F:\post_doc_C++\petsc_new\petsc-main\src\ksp\ksp\interface\itfunc.c:406 [1]PETSC ERROR: [0]PETSC ERROR: #5 petsc_calcul_part_DMDA() at petsc_DMDA.cpp:285 #5 petsc_calcul_part_DMDA() at petsc_DMDA.cpp:285 [1]PETSC ERROR: [0]PETSC ERROR: #6 main() at ..\Main.cpp:281 #6 main() at ..\Main.cpp:281 [1]PETSC ERROR: [0]PETSC ERROR: No PETSc Option Table entries No PETSc Option Table entries [1]PETSC ERROR: [0]PETSC ERROR: ----------------End of Error Message -------send entire error message to petsc-maint(a)mcs.anl.gov---------- ----------------End of Error Message -------send entire error message to petsc-maint(a)mcs.anl.gov---------- job aborted: [ranks] message [0-1] application aborted aborting MPI_COMM_SELF (comm=0x44000001), error 76, comm rank 0 ---- error analysis ----- [0-1] on lmeep-329 test_petsc_fem.exe aborted the job. abort code 76 ---- error analysis ----- Ziming XIONG

2 1