> On Jan 4, 2018, at 5:10 PM, Blaise A Bourdin wrote:
>
>
>
>> On Jan 4, 2018, at 3:16 PM, Smith, Barry F. wrote:
>>
>>
>> It's changed a bit. It is better but you need to understand how the new one
>> works, so take a few minutes to see how it works
> On Jan 4, 2018, at 3:16 PM, Smith, Barry F. wrote:
>
>
> It's changed a bit. It is better but you need to understand how the new one
> works, so take a few minutes to see how it works before converting.
Got it.
An example or a link to the fortran macro definition from
It's changed a bit. It is better but you need to understand how the new one
works, so take a few minutes to see how it works before converting.
Use CHKERRA() for main Fortran problem and CHKERRQ() for subroutines.
Also look at their definitions to see how the if () business is handled.
On Thu, Jan 4, 2018 at 2:42 PM, Blaise A Bourdin wrote:
> Hi,
>
> Is SETERRQ still available in fortran? I notice that it is not used in any
> of the example, but the man page still mentions fortran. Using it in a
> fortran code leads to compiler errors.
> Am I doing something
Hi,
Is SETERRQ still available in fortran? I notice that it is not used in any of
the example, but the man page still mentions fortran. Using it in a fortran
code leads to compiler errors.
Am I doing something wrong?
MacBookGray:F90 $ cat TestSETERRQ.F90
Program TestSETERRQ
#include
Use
I just forward it to you there times, if you don't get it then send me an
alternative email to use. It is a small message and should not get blocked or
delayed.
> On Jan 4, 2018, at 11:27 AM, Franck Houssen wrote:
>
>
>
> - Mail original -
>> De: "Barry
- Mail original -
> De: "Barry F. Smith"
> À: "Franck Houssen"
> Cc: "Barry F. Smith" , "For users of the development
> version of PETSc"
> Envoyé: Jeudi 4 Janvier 2018 18:13:32
> Objet: Re:
> On Jan 4, 2018, at 11:10 AM, Franck Houssen wrote:
>
> Do you reproduce the error at your side ? Or is the pattern I use wrong ?
You should have received an email from me with a patch for PETSc code. Yes
I could reproduce, clearly our bug your code was fine.
Frank,
This is our bug. I have attached a patch and also fixed it in the PETSc
repository master branch.
apply with
patch -p1 < franck.patch
if you are using the tarball version of PETSc.
Barry
> On Jan 4, 2018, at 2:31 AM, Franck Houssen wrote:
>
> I
Do you reproduce the error at your side ? Or is the pattern I use wrong ?
Franck
- Mail original -
> De: "Franck Houssen"
> À: "Barry F. Smith"
> Cc: "For users of the development version of PETSc"
> Envoyé: Jeudi 4
I attached it in the very first mail.
Franck
>> more vecScatterGatherRoot.cpp
// How do I collect all the values from a sequential vector on the zeroth
processor into a parallel PETSc vector ?
//
// ~> g++ -o vecScatterGatherRoot.exe vecScatterGatherRoot.cpp -lpetsc -lm;
mpirun -n X
11 matches
Mail list logo