July 2012 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] who did this?
by Matthew Knepley 05 Jul '12

05 Jul '12

On Thu, Jul 5, 2012 at 10:37 AM, Jed Brown <jedbrown(a)mcs.anl.gov> wrote: > On Thu, Jul 5, 2012 at 5:35 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > >> >> On Jul 5, 2012, at 4:19 AM, Jed Brown wrote: >> >> > This is years old, but in any case, fixed now: >> http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e >> >> How can it possibly be years old? You're saying that this message has >> appeared every night during the nightly tests and every time someone did >> make alltests and during every test Satish made before the release? >> > > Oops, I read "hg annotate" incorrectly. It was in > > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7 > > which was merged in > > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/9dfe4a92ca2c > > I don't understand the motivation for unrolling the shell loop, but then > referencing a file that doesn't match the target name. > I unrolled the shell loop so that the shell code can be processed by Python, and eventually converted to Python tests. Matt > >> >> > >> > On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith(a)mcs.anl.gov> >> wrote: >> > >> > /bin/sh: -c: line 0: syntax error near unexpected token `done' >> > /bin/sh: -c: line 0: >> `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 >> -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out >> ex37_1.tmp || echo >> /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible >> problem with ex37_1, diffs above >> \n========================================="; done; /bin/rm -f -f >> ex37_1.tmp' >> > make[7]: [runex37] Error 2 (ignored) >> > /bin/sh: -c: line 0: syntax error near unexpected token `done' >> > /bin/sh: -c: line 0: >> `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 >> -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out >> ex37_1.tmp || echo >> /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible >> problem with ex37_1, diffs above >> \n========================================="; done; /bin/rm -f -f >> ex37_1.tmp' >> > make[7]: [runex37_1] Error 2 (ignored) >> > /bin/sh: -c: line 0: syntax error near unexpected token `done' >> > /bin/sh: -c: line 0: >> `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 >> -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out >> ex37_2.tmp || echo >> /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible >> problem with ex37_2, diffs above >> \n========================================="; done; /bin/rm -f -f >> ex37_2.tmp' >> > make[7]: [runex37_2] Error 2 (ignored) >> > >> > At least test your rule before pushing >> > >> > >> > >> > >> >> > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener

1 0

Re: [petsc-dev] who did this?
by Jed Brown 05 Jul '12

05 Jul '12

On Thu, Jul 5, 2012 at 5:35 AM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > On Jul 5, 2012, at 4:19 AM, Jed Brown wrote: > > > This is years old, but in any case, fixed now: > http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e > > How can it possibly be years old? You're saying that this message has > appeared every night during the nightly tests and every time someone did > make alltests and during every test Satish made before the release? > Oops, I read "hg annotate" incorrectly. It was in http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7 which was merged in http://petsc.cs.iit.edu/petsc/petsc-dev/rev/9dfe4a92ca2c I don't understand the motivation for unrolling the shell loop, but then referencing a file that doesn't match the target name. > > > > > > On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: > `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 > -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out > ex37_1.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_1, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_1.tmp' > > make[7]: [runex37] Error 2 (ignored) > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: > `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 > -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out > ex37_1.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_1, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_1.tmp' > > make[7]: [runex37_1] Error 2 (ignored) > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: > `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 > -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out > ex37_2.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_2, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_2.tmp' > > make[7]: [runex37_2] Error 2 (ignored) > > > > At least test your rule before pushing > > > > > > > > > >

1 0

Re: [petsc-dev] who did this?
by Satish Balay 05 Jul '12

05 Jul '12

This issue is not in petsc-3.3 but looks like it was introduced at: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/2ab3e57475d7 I switched nightly builds back from petsc33 to petsc-dev on june 27-ish.. satish On Thu, 5 Jul 2012, Barry Smith wrote: > > On Jul 5, 2012, at 4:19 AM, Jed Brown wrote: > > > This is years old, but in any case, fixed now: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e > > How can it possibly be years old? You're saying that this message has appeared every night during the nightly tests and every time someone did make alltests and during every test Satish made before the release? > > > > > > On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' > > make[7]: [runex37] Error 2 (ignored) > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' > > make[7]: [runex37_1] Error 2 (ignored) > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out ex37_2.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_2, diffs above \n========================================="; done; /bin/rm -f -f ex37_2.tmp' > > make[7]: [runex37_2] Error 2 (ignored) > > > > At least test your rule before pushing > > > > > > > > > >

1 0

Re: [petsc-dev] who did this?
by Barry Smith 05 Jul '12

05 Jul '12

On Jul 5, 2012, at 4:19 AM, Jed Brown wrote: > This is years old, but in any case, fixed now: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e How can it possibly be years old? You're saying that this message has appeared every night during the nightly tests and every time someone did make alltests and during every test Satish made before the release? > > On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' > make[7]: [runex37] Error 2 (ignored) > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' > make[7]: [runex37_1] Error 2 (ignored) > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out ex37_2.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_2, diffs above \n========================================="; done; /bin/rm -f -f ex37_2.tmp' > make[7]: [runex37_2] Error 2 (ignored) > > At least test your rule before pushing > > > >

1 0

Re: [petsc-dev] who did this?
by Jed Brown 05 Jul '12

05 Jul '12

This is years old, but in any case, fixed now: http://petsc.cs.iit.edu/petsc/petsc-dev/rev/30f9a34e118e On Wed, Jul 4, 2012 at 10:17 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec > -n 1 ./ex37 -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w > output/ex37_1.out ex37_1.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_1, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_1.tmp' > make[7]: [runex37] Error 2 (ignored) > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec > -n 1 ./ex37 -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w > output/ex37_1.out ex37_1.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_1, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_1.tmp' > make[7]: [runex37_1] Error 2 (ignored) > /bin/sh: -c: line 0: syntax error near unexpected token `done' > /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec > -n 2 ./ex37 -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w > output/ex37_2.out ex37_2.tmp || echo > /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible > problem with ex37_2, diffs above > \n========================================="; done; /bin/rm -f -f > ex37_2.tmp' > make[7]: [runex37_2] Error 2 (ignored) > > At least test your rule before pushing > > > >

1 0

who did this?
by Barry Smith 05 Jul '12

05 Jul '12

/bin/sh: -c: line 0: syntax error near unexpected token `done' /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 0 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' make[7]: [runex37] Error 2 (ignored) /bin/sh: -c: line 0: syntax error near unexpected token `done' /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 1 ./ex37 -explicit_is 1 > ex37_1.tmp 2>&1; /usr/bin/diff -w output/ex37_1.out ex37_1.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_1, diffs above \n========================================="; done; /bin/rm -f -f ex37_1.tmp' make[7]: [runex37_1] Error 2 (ignored) /bin/sh: -c: line 0: syntax error near unexpected token `done' /bin/sh: -c: line 0: `/Users/barrysmith/Src/petsc-dev/arch-gnu/bin/mpiexec -n 2 ./ex37 -explicit_is 0 > ex37_2.tmp 2>&1; /usr/bin/diff -w output/ex37_2.out ex37_2.tmp || echo /Users/barrysmith/Src/petsc-dev/src/vec/vec/examples/tests "\nPossible problem with ex37_2, diffs above \n========================================="; done; /bin/rm -f -f ex37_2.tmp' make[7]: [runex37_2] Error 2 (ignored) At least test your rule before pushing

1 0

Re: [petsc-dev] how to print with PescPrintf a PetscScalar value?
by Luigia Ambrosio 04 Jul '12

04 Jul '12

sorry... previously I had tried with a cast ... something like (PetscInt)sum... I knew PetscGetReal is a function... but I just replaced PetscInt with PetscGetReal... without moving parenthesis thanks again Luigia Ambrosio Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano Ferro Il giorno 04/lug/2012, alle ore 10:20, Jed Brown ha scritto: > On Wed, Jul 4, 2012 at 12:15 AM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com> wrote: > this is the source code (very simple) > Vec x; > PetscInt n = 10; > PetscErrorCode ierr; > PetscScalar one = 1.0; > > ierr = VecCreateMPI(PETSC_COMM_WORLD, PETSC_DECIDE, n, &x);CHKERRQ(ierr); > ierr = VecSet(x,one);CHKERRQ(ierr); > PetscScalar sum=0.0; > ierr = VecSum(x,&sum);CHKERRQ(ierr); > ierr = PetscPrintf(PETSC_COMM_WORLD,"sum %f\n",(PetscRealPart)sum); > > Use PetscRealPart(sum), it is a function, not a type. > > > CHKERRQ(ierr); puts(""); > > This puts will be issued by every process, leading to messy output, especially for larger runs. Just add a second \n to the string passed to PetscPrintf() if you want another newline. > > ... > > and this is the error message I get trying make myex > error: 'PetscRealPart' was not declared in this scope > > this is how I compile myex > myex: myex.o chkopts > -${CLINKER} -o myex myex.o ${PETSC_VEC_LIB} > ${RM} -f myex.o > > I have petsc 3.3 developer version > > Luigia Ambrosio > > Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano Ferro > > > > > Il giorno 04/lug/2012, alle ore 09:58, Jed Brown ha scritto: > >> On Tue, Jul 3, 2012 at 11:53 PM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com> wrote: >> It seems I don't have this function. I checked my configuring options, in particular >> --with-scalar-type=complex >> >> Which version of PETSc? Can you send the full error message? >> >> >> so I'm sure that a PetscScalar variable is handled as a complex number. I tried to use the PetscRealPart but it says: >> error: 'PetscRealPart' was not declared in this scope >> >> I included also the header "petscmat.h" but there isn't defined this function. >> It seems that I don't include the right header, I googled it but I didn't find it. Which header shiuld I include? >> >> That header includes petscmath.h (which you should not include directly). >> >> thanks >> >> Luigia Ambrosio >> >> Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano Ferro >> >> >> >> >> Il giorno 04/lug/2012, alle ore 09:28, Jed Brown ha scritto: >> >>> On Tue, Jul 3, 2012 at 11:26 PM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com> wrote: >>> Is there a function already avilable to get the real part of a petscscalar value? >>> >>> >>> PetscRealPart() and PetscImaginaryPart() >> >> > >

1 0

Re: [petsc-dev] how to print with PescPrintf a PetscScalar value?
by Jed Brown 04 Jul '12

04 Jul '12

On Wed, Jul 4, 2012 at 12:15 AM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com>wrote: > this is the source code (very simple) > Vec x; > PetscInt n = 10; > PetscErrorCode ierr; > PetscScalar one = 1.0; > > ierr = VecCreateMPI(PETSC_COMM_WORLD, PETSC_DECIDE, n, &x);CHKERRQ(ierr); > ierr = VecSet(x,one);CHKERRQ(ierr); > PetscScalar sum=0.0; > ierr = VecSum(x,&sum);CHKERRQ(ierr); > ierr = PetscPrintf(PETSC_COMM_WORLD,"sum %f\n",(PetscRealPart)sum); > Use PetscRealPart(sum), it is a function, not a type. > CHKERRQ(ierr); puts(""); > This puts will be issued by every process, leading to messy output, especially for larger runs. Just add a second \n to the string passed to PetscPrintf() if you want another newline. > ... > > and this is the error message I get trying make myex > error: 'PetscRealPart' was not declared in this scope > > this is how I compile myex > myex: myex.o chkopts > -${CLINKER} -o myex myex.o ${PETSC_VEC_LIB} > ${RM} -f myex.o > > I have petsc 3.3 developer version > > Luigia Ambrosio > > Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano > Ferro > > > > > Il giorno 04/lug/2012, alle ore 09:58, Jed Brown ha scritto: > > On Tue, Jul 3, 2012 at 11:53 PM, Luigia Ambrosio < > ambrosio.luigia(a)gmail.com> wrote: > >> It seems I don't have this function. I checked my configuring options, in >> particular >> --with-scalar-type=complex >> > > Which version of PETSc? Can you send the full error message? > > >> >> so I'm sure that a PetscScalar variable is handled as a complex number. I >> tried to use the PetscRealPart but it says: >> error: 'PetscRealPart' was not declared in this scope >> >> I included also the header "petscmat.h" but there isn't defined this >> function. >> It seems that I don't include the right header, I googled it but I didn't >> find it. Which header shiuld I include? >> > > That header includes petscmath.h (which you should not include directly). > > >> thanks >> >> Luigia Ambrosio >> >> Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano >> Ferro >> >> >> >> >> Il giorno 04/lug/2012, alle ore 09:28, Jed Brown ha scritto: >> >> On Tue, Jul 3, 2012 at 11:26 PM, Luigia Ambrosio < >> ambrosio.luigia(a)gmail.com> wrote: >> >>> Is there a function already avilable to get the real part of a >>> petscscalar value? >>> >>> >> PetscRealPart() and PetscImaginaryPart() >> >> >> > >

1 0

Re: [petsc-dev] how to print with PescPrintf a PetscScalar value?
by Luigia Ambrosio 04 Jul '12

04 Jul '12

this is the source code (very simple) Vec x; PetscInt n = 10; PetscErrorCode ierr; PetscScalar one = 1.0; ierr = VecCreateMPI(PETSC_COMM_WORLD, PETSC_DECIDE, n, &x);CHKERRQ(ierr); ierr = VecSet(x,one);CHKERRQ(ierr); PetscScalar sum=0.0; ierr = VecSum(x,&sum);CHKERRQ(ierr); ierr = PetscPrintf(PETSC_COMM_WORLD,"sum %f\n",(PetscRealPart)sum); CHKERRQ(ierr); puts(""); ... and this is the error message I get trying make myex error: 'PetscRealPart' was not declared in this scope this is how I compile myex myex: myex.o chkopts -${CLINKER} -o myex myex.o ${PETSC_VEC_LIB} ${RM} -f myex.o I have petsc 3.3 developer version Luigia Ambrosio Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano Ferro Il giorno 04/lug/2012, alle ore 09:58, Jed Brown ha scritto: > On Tue, Jul 3, 2012 at 11:53 PM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com> wrote: > It seems I don't have this function. I checked my configuring options, in particular > --with-scalar-type=complex > > Which version of PETSc? Can you send the full error message? > > > so I'm sure that a PetscScalar variable is handled as a complex number. I tried to use the PetscRealPart but it says: > error: 'PetscRealPart' was not declared in this scope > > I included also the header "petscmat.h" but there isn't defined this function. > It seems that I don't include the right header, I googled it but I didn't find it. Which header shiuld I include? > > That header includes petscmath.h (which you should not include directly). > > thanks > > Luigia Ambrosio > > Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano Ferro > > > > > Il giorno 04/lug/2012, alle ore 09:28, Jed Brown ha scritto: > >> On Tue, Jul 3, 2012 at 11:26 PM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com> wrote: >> Is there a function already avilable to get the real part of a petscscalar value? >> >> >> PetscRealPart() and PetscImaginaryPart() > >

1 0

Re: [petsc-dev] how to print with PescPrintf a PetscScalar value?
by Jed Brown 04 Jul '12

04 Jul '12

On Tue, Jul 3, 2012 at 11:53 PM, Luigia Ambrosio <ambrosio.luigia(a)gmail.com>wrote: > It seems I don't have this function. I checked my configuring options, in > particular > --with-scalar-type=complex > Which version of PETSc? Can you send the full error message? > > so I'm sure that a PetscScalar variable is handled as a complex number. I > tried to use the PetscRealPart but it says: > error: 'PetscRealPart' was not declared in this scope > > I included also the header "petscmat.h" but there isn't defined this > function. > It seems that I don't include the right header, I googled it but I didn't > find it. Which header shiuld I include? > That header includes petscmath.h (which you should not include directly). > thanks > > Luigia Ambrosio > > Se la gente ferisce è perchè tu sei migliore e lo capisce bene! - Tiziano > Ferro > > > > > Il giorno 04/lug/2012, alle ore 09:28, Jed Brown ha scritto: > > On Tue, Jul 3, 2012 at 11:26 PM, Luigia Ambrosio < > ambrosio.luigia(a)gmail.com> wrote: > >> Is there a function already avilable to get the real part of a >> petscscalar value? >> >> > PetscRealPart() and PetscImaginaryPart() > > >

1 0