get_command_argument(). Since updating PETSc to version 3.21, I get some extra warnings after the output: acro018@EN438880:~$ waiwera -v 1.5.0b1 WARNING! There are options you set that were not used! WARNING! could be spelling mistake, etc! There is one unused database option. It is...
> I don't know why this should have changed, but you can either not feed -v to > PETSc (a pain probably), use PETSc's getOptions methods instead of Fortran's, > or make a dummy call PETSc's methods in addition to yours. Yes, just call PetscOptionsHasName() with -v and ign...
35 of https://urldefense.us/v3/__https://mumps-solver.org/doc/userguide_5.6.2.pdf__;!!G_uCfscf7eWS!aqzhWg_iCZLsu1jTz2sWKIpVkAIDvmvt-_4ojHy5ZtC2eWYBRlCU3zlqh72rGtso5KuDhEuf9yFxMNOGRhHoQBLH_kmf$ . Is it possible to provide these options to MUMPS via PETSc API? I can only ...
> Is it possible to provide these options to MUMPS via PETSc API? I can > only find a way to control integer and real control parameters. It is not possible, but I guess we could add something like MatMumpsSetMetisOptions(Mat A, PetscInt index, PetscInt value), just like MatMumpsS...