Re: [petsc-users] Installation issue of 3.18.* and 3.19.0 on Apple systems

Great! I created MR for this change https://gitlab.com/petsc/petsc/-/merge_requests/6289 Satish On Thu, 6 Apr 2023, Kaus, Boris wrote: > Apologies, mistake on my side. Yes this works - thanks a lot for your help! > > Boris > > On 6. Apr 2023, at 00:56, Satish Balay wrote: > > This is

Re: [petsc-users] How to use PETSc real version and complex version simultaneously?

Thanks for the hint.I did a naive test and managed to use the same function with different typedefs. Basically, it is relied on that C has no name mangling while C++ has name mangling. Could this trick applies to PETSc? The files for the test are attached. The procedure for compilation is in the

Re: [petsc-users] Question about NASM initialization

Ok, thanks for the clarification. On Thu, Apr 6, 2023 at 10:25 AM Matthew Knepley wrote: > On Thu, Apr 6, 2023 at 10:21 AM Takahashi, Tadanaga wrote: > >> I am following up from the last inquiry. I read the source code nasm.c >> and

Re: [petsc-users] Question about NASM initialization

On Thu, Apr 6, 2023 at 10:21 AM Takahashi, Tadanaga wrote: > I am following up from the last inquiry. I read the source code nasm.c > and it looks > like sub-snes iteration is being initialized with a scatter call from the > previous

Re: [petsc-users] Question about NASM initialization

I am following up from the last inquiry. I read the source code nasm.c and it looks like sub-snes iteration is being initialized with a scatter call from the previous solution. In other words, if I use Newton's method for the local

Re: [petsc-users] Installation issues based on Petsc-pardiso et metis

On Thu, Apr 6, 2023 at 5:21 AM ziming xiong wrote: > Hello, > I want configure Petsc with pardiso and metis , but there is still error, > This seems like a fundamental misunderstanding. There are two ways to run on a Windows machine: 1) You can use Windows compilers and generate .lib

Re: [petsc-users] Installation issue of 3.18.* and 3.19.0 on Apple systems

Apologies, mistake on my side. Yes this works - thanks a lot for your help! Boris On 6. Apr 2023, at 00:56, Satish Balay wrote: This is strange. I can trigger the error with: - v = tuple([int(a) for a in platform.mac_ver()[0].split('.')]) + v = tuple([int('')]) and this fix