February 2017 - petsc-dev - mailman3.cels.anl.gov

Re: [petsc-dev] every test example runs in a new directory with new test harness
by Satish Balay 06 Feb '17

06 Feb '17

I just tried it - and it doesn't appear to work.. Should the keyword for 'subtest' be different than 'test:'? Satish ----------------------------------------------------- balay@asterix /home/balay/petsc (next *=) $ git diff|cat diff --git a/src/snes/examples/tutorials/ex12.c b/src/snes/examples/tutorials/ex12.c index 71166bf..c097018 100644 --- a/src/snes/examples/tutorials/ex12.c +++ b/src/snes/examples/tutorials/ex12.c @@ -1168,10 +1168,8 @@ int main(int argc, char **argv) suffix: restart_0 requires: hdf5 args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append - test: - suffix: restart_1 - requires: hdf5 - args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -f sol.h5 -restart + test: + args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -f sol.h5 -restart # Periodicity test: suffix: periodic_0 balay@asterix /home/balay/petsc (next *=) $ ./config/gmakegentest.py balay@asterix /home/balay/petsc (next *=) $ cat arch-next/tests/src/snes/examples/tutorials/runex12_restart_0.sh #!/usr/bin/env bash # This script was created by gmakegentest.py # PATH for DLLs on windows PATH="$PATH":"/home/balay/petsc/arch-next/lib" mpiexec='mpiexec' exec='../ex12' testname='runex12_restart_0' label='snes_tutorials-ex12_restart_0' runfiles='' wPETSC_DIR='/home/balay/petsc' petsc_dir='/home/balay/petsc' args='-run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append' . "${petsc_dir}/config/petsc_harness.sh" # The diff flags come from script arguments diff_exe="${petsc_dir}/bin/petscdiff ${diff_flags}" printf "ok ${label} # SKIP PETSC_HAVE_HDF5 requirement not met\n" total=1; skip=1 petsc_testend "/home/balay/petsc/arch-next/tests" exit petsc_testrun "${mpiexec} -n 1 ${exec} ${args}" ex12_restart_0.tmp ${testname}.err "${label}" '' petsc_testrun "${diff_exe} /home/balay/petsc/src/snes/examples/tutorials/output/ex12_restart_0.out ex12_restart_0.tmp" diff-${testname}.out diff-${testname}.out diff-${label} "" petsc_testend "/home/balay/petsc/arch-next/tests" balay@asterix /home/balay/petsc (next *=) $ On Mon, 6 Feb 2017, Scott Kruger wrote: > > The basic idea of running multiple commands within a single shell > script was what I called a subtest (for lack of a better word). > So: > > > test: > suffix: restart > requires: hdf5 > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet > -interpolate 1 -petscspace_order 1 > test: > args: -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append > test: > args: -f sol.h5 -restart > > The args in the subtest inherit from the parent test. This seems > to be generally useful as a testing idiom in petsc tests as this > example nicely shows. > > Each mpiexec would be tested separately and reported separately. > This would give you want you want, and should work as is. > > > Tobin pointed out that I broke the for loops and some of the subtest > functionality in some of the other feature implementations. We > have come to consensus (right, Tobin?) on the > desired functionality and implementation. A pull request > is planned this week. It doesn't affect this directly, but > should have some minor improvements (like in the reporting). > > Scott > > > On 2/6/17 7:10 AM, Matthew Knepley wrote: > > On Mon, Feb 6, 2017 at 1:05 AM, Jed Brown <jed(a)jedbrown.org > > <mailto:[email protected]>> wrote: > > > > Barry Smith <bsmith(a)mcs.anl.gov <mailto:[email protected]>> writes: > > > > > test: > > > suffix: restart_0 > > > requires: hdf5 > > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet > > > -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view > > > hdf5:sol.h5::append > > > > > > test: > > > suffix: restart_1 > > > requires: hdf5 > > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet > > > -interpolate 1 -petscspace_order 1 -f sol.h5 -restart > > > > > > See a problem? > > > > > > Should the same run of the example view the files and then load them back > > > in? versus trying to read in a data file from another run that may not > > > even have been created before and even if it was, the file was definitely > > > created in a different directory? > > > > So if write only is broken, do you want both to fail? I think it's > > better to read and write separately, with comparison using h5diff, since > > that independently tests read vs write and establishes backward > > compatibility, which you'd really like the test system to make you deal > > with explicitly. > > > > > > I know the test is broken, but I did already mail the list about this > > and was waiting for an answer > > to be worked out. > > > > I agree with Satish that running two commands would be great. I could > > rewrite the example to > > both write and load it, but it would complicate it. Also, I am trying to > > get the pattern I expect the > > user to follow for checkpointing. > > > > Matt > > > > -- > > 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] every test example runs in a new directory with new test harness
by Scott Kruger 06 Feb '17

06 Feb '17

The basic idea of running multiple commands within a single shell script was what I called a subtest (for lack of a better word). So: test: suffix: restart requires: hdf5 args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 test: args: -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append test: args: -f sol.h5 -restart The args in the subtest inherit from the parent test. This seems to be generally useful as a testing idiom in petsc tests as this example nicely shows. Each mpiexec would be tested separately and reported separately. This would give you want you want, and should work as is. Tobin pointed out that I broke the for loops and some of the subtest functionality in some of the other feature implementations. We have come to consensus (right, Tobin?) on the desired functionality and implementation. A pull request is planned this week. It doesn't affect this directly, but should have some minor improvements (like in the reporting). Scott On 2/6/17 7:10 AM, Matthew Knepley wrote: > On Mon, Feb 6, 2017 at 1:05 AM, Jed Brown <jed(a)jedbrown.org > <mailto:[email protected]>> wrote: > > Barry Smith <bsmith(a)mcs.anl.gov <mailto:[email protected]>> writes: > > > test: > > suffix: restart_0 > > requires: hdf5 > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append > > > > test: > > suffix: restart_1 > > requires: hdf5 > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -f sol.h5 -restart > > > > See a problem? > > > > Should the same run of the example view the files and then load them back in? versus trying to read in a data file from another run that may not even have been created before and even if it was, the file was definitely created in a different directory? > > So if write only is broken, do you want both to fail? I think it's > better to read and write separately, with comparison using h5diff, since > that independently tests read vs write and establishes backward > compatibility, which you'd really like the test system to make you deal > with explicitly. > > > I know the test is broken, but I did already mail the list about this > and was waiting for an answer > to be worked out. > > I agree with Satish that running two commands would be great. I could > rewrite the example to > both write and load it, but it would complicate it. Also, I am trying to > get the pattern I expect the > user to follow for checkpointing. > > Matt > > -- > 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 -- Tech-X Corporation kruger(a)txcorp.com 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 Boulder, CO 80303 Fax: (303) 448-7756

1 0

Re: [petsc-dev] every test example runs in a new directory with new test harness
by Matthew Knepley 06 Feb '17

06 Feb '17

On Mon, Feb 6, 2017 at 1:05 AM, Jed Brown <jed(a)jedbrown.org> wrote: > Barry Smith <bsmith(a)mcs.anl.gov> writes: > > > test: > > suffix: restart_0 > > requires: hdf5 > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet > -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view > hdf5:sol.h5::append > > > > test: > > suffix: restart_1 > > requires: hdf5 > > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet > -interpolate 1 -petscspace_order 1 -f sol.h5 -restart > > > > See a problem? > > > > Should the same run of the example view the files and then load them > back in? versus trying to read in a data file from another run that may not > even have been created before and even if it was, the file was definitely > created in a different directory? > > So if write only is broken, do you want both to fail? I think it's > better to read and write separately, with comparison using h5diff, since > that independently tests read vs write and establishes backward > compatibility, which you'd really like the test system to make you deal > with explicitly. > I know the test is broken, but I did already mail the list about this and was waiting for an answer to be worked out. I agree with Satish that running two commands would be great. I could rewrite the example to both write and load it, but it would complicate it. Also, I am trying to get the pattern I expect the user to follow for checkpointing. Matt -- 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] install petsc on windows 10 with mpi
by Matthew Knepley 06 Feb '17

06 Feb '17

On Sun, Feb 5, 2017 at 11:26 PM, Mohammad S Dodaran <mdodar1(a)lsu.edu> wrote: > Satish, > > Thanks for your quick response. as you see I can ls to the directory: > > ls /cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include/ > Yes, but as Satish said, there are spaces in the path above. We do not allow spaces in the path. You cannot give a path to configure with spaces. You can remove the spaces using the cygpath command that Satish showed. Please use that command. Remove the spaces from this path and give the spaceless path to configure. Thanks, Matt > mpi.f90 mpi.h mpif.h mpio.h mspms.h pmidbg.h x64/ x86/ > > > but I do not know why still it has the same problem. and my configure file > looks strange. > > Best, > > Mohammad > ------------------------------ > *From:* Satish Balay <balay(a)mcs.anl.gov> > *Sent:* Sunday, February 5, 2017 10:58:35 PM > *To:* Mohammad S Dodaran > *Cc:* petsc-dev(a)mcs.anl.gov > *Subject:* Re: [petsc-dev] install petsc on windows 10 with mpi > > Try to figureout path without spaces. > > cygpath -u `cygpath -s -m PATH` > > Make sure you can do "ls" on this path. > > And use it with petsc configure. > > balay@ps4 ~ > $ cygpath -u `cygpath -s -m /cygdrive/c/Program\ Files\ $x86$/Microsoft\ > SDKs/MPI/Include` > /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include > > balay@ps4 ~ > $ ls /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include > mpi.f90 mpi.h mpif.h mpio.h mspms.h pmidbg.h x64 x86 > > balay@ps4 ~ > $ > > For ex: - I use: > > >>>>>>>> > $ cat config/examples/arch-mswin-intel.py > #!/usr/bin/python > if __name__ == '__main__': > import sys > import os > sys.path.insert(0, os.path.abspath('config')) > import configure > configure_options = [ > '--download-fblaslapack=1', > '--with-cc=win32fe icl', > '--with-cxx=win32fe icl', > '--with-fc=win32fe ifort', > '--with-mpi-include=[/cygdrive/c/PROGRA~2/MICROS~2/ > MPI/Include/,/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include/x64]', > '--with-mpi-lib=[/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/ > msmpifec.lib,/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/msmpi.lib]', > '--with-mpiexec=/cygdrive/c/PROGRA~1/MICROS~2/Bin/mpiexec', > '--with-shared-libraries=0', > 'DATAFILESPATH=c:/cygwin64/home/petsc/datafiles', > ] > configure.petsc_configure(configure_options) > > <<<<<<<<<<< > > if you still have issues - send us configure.log for the failure. > > Satish > > On Sun, 5 Feb 2017, Mohammad S Dodaran wrote: > > > Dear Petsc developers, > > > > I am trying to install Petsc on windows 10 but I have a problem. I > installed MS-MPI v8<http://go.microsoft.com/FWLink/p/?LinkID=389556> > separately and in the configure options I use > > > > --with-mpi-include="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ > SDKs/MPI/Include" --with-mpi-lib="/cygdrive/c/Program\ Files\ > $x86$/Microsoft\ SDKs/MPI/Lib/x64/msmpi.lib" > > > > > > But it gives error which says: > > > > *************************************************************** > > ERROR in COMMAND LINE ARGUMENT to ./configure > > ------------------------------------------------------------ > ------------------- > > Invalid directory: [/cygdrive/c/Program\ Files\ $x86$/Microsoft\ > SDKs/MPI/Include for key with-mpi-include > > > > > > How should I solve it? > > > > Mohammad > > > > -- 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] partitioners that use bullshit random numbers
by Matthew Knepley 06 Feb '17

06 Feb '17

On Sun, Feb 5, 2017 at 9:40 PM, Barry Smith <bsmith(a)mcs.anl.gov> wrote: > > Is there any way we can substitute a deterministic random number > generators for the bullshit partitioning packages that insist on using > "system" non-portable random number generators? We should have tests that > use metis/parmetis and chaco or whatever but we shouldn't have to deal with > their bad decisions. Matt, what horrible partitioning is being used here? > I put in something that accepts fixed partitions, and it should be used for all parallel tests. I converted a bunch of them already, but its possible I missed this one. The workflow for conversion is a) Run the test with the -partition_view flag b) The partition of cells prints out at the top c) Copy that partition into a struct with the number of cells in one array and the cells numbers in another. You can see an example in Plex tests ex1. d) Create a Shell Partitioner. Again refer to ex1 Matt > Barry > > not ok diff-snes_tutorials-ex12_tri_bddc > # 2,12c2,11 > # < 0 KSP Residual norm 11.5911 > # < 1 KSP Residual norm 0.419162 > # < 2 KSP Residual norm 0.0466633 > # < 3 KSP Residual norm 0.00282513 > # < 4 KSP Residual norm 0.000140711 > # < 5 KSP Residual norm 2.35332e-05 > # < 6 KSP Residual norm 8.28552e-07 > # < 7 KSP Residual norm 1.43643e-08 > # < 8 KSP Residual norm 2.827e-10 > # < Linear solve converged due to CONVERGED_RTOL iterations 8 > # < 1 SNES Function norm 7.836e-10 > # --- > # > 0 KSP Residual norm 11.6648 > # > 1 KSP Residual norm 0.443991 > # > 2 KSP Residual norm 0.0393777 > # > 3 KSP Residual norm 0.00187772 > # > 4 KSP Residual norm 0.000140435 > # > 5 KSP Residual norm 1.08843e-05 > # > 6 KSP Residual norm 2.87537e-07 > # > 7 KSP Residual norm 5.20043e-09 > # > Linear solve converged due to CONVERGED_RTOL iterations 7 > # > 1 SNES Function norm 1.59735e-08 > # 18c17 > # < total number of linear solver iterations=8 > # --- > # > total number of linear solver iterations=7 > # 76,77c75,76 > # < BDDC: Global dofs sizes: all 225 interface 43 coarse 7 > # < BDDC: Coarsening ratios: all/coarse 32 interface/coarse 6 > # --- > # > BDDC: Global dofs sizes: all 225 interface 57 coarse 9 > # > BDDC: Coarsening ratios: all/coarse 25 interface/coarse 6 > # 81,84c80,83 > # < BDDC: Interior dofs : 21 49 36 > # < BDDC: Interface dofs : 15 22 17 > # < BDDC: Primal dofs : 3 4 3 > # < BDDC: Local dofs : 36 64 54 > # --- > # > BDDC: Interior dofs : 21 42 33 > # > BDDC: Interface dofs : 15 36 23 > # > BDDC: Primal dofs : 3 6 4 > # > BDDC: Local dofs : 36 78 57 > # 99,100c98,99 > # < rows=7, cols=7 > # < total: nonzeros=35, allocated nonzeros=43 > # --- > # > rows=9, cols=9 > # > total: nonzeros=61, allocated nonzeros=68 > # 115c114 > # < factor fill ratio given 5., needed 1.17143 > # --- > # > factor fill ratio given 5., needed 1.13115 > # 119c118 > # < rows=7, cols=7 > # --- > # > rows=9, cols=9 > # 121c120 > # < total: nonzeros=41, allocated nonzeros=41 > # --- > # > total: nonzeros=69, allocated nonzeros=69 > # 127,128c126,127 > # < rows=7, cols=7 > # < total: nonzeros=35, allocated nonzeros=35 > # --- > # > rows=9, cols=9 > # > total: nonzeros=61, allocated nonzeros=61 > # 130c129 > # < not using I-node routines > # --- > # > using I-node routines: found 7 nodes, limit > used is 5 > # 135c134 > # < total: nonzeros=1585, allocated nonzeros=1764 > # --- > # > total: nonzeros=1625, allocated nonzeros=1855 > > -- 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] every test example runs in a new directory with new test harness
by Jed Brown 06 Feb '17

06 Feb '17

Barry Smith <bsmith(a)mcs.anl.gov> writes: > test: > suffix: restart_0 > requires: hdf5 > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -dm_view hdf5:sol.h5 -vec_view hdf5:sol.h5::append > > test: > suffix: restart_1 > requires: hdf5 > args: -run_type test -refinement_limit 0.0 -bc_type dirichlet -interpolate 1 -petscspace_order 1 -f sol.h5 -restart > > See a problem? > > Should the same run of the example view the files and then load them back in? versus trying to read in a data file from another run that may not even have been created before and even if it was, the file was definitely created in a different directory? So if write only is broken, do you want both to fail? I think it's better to read and write separately, with comparison using h5diff, since that independently tests read vs write and establishes backward compatibility, which you'd really like the test system to make you deal with explicitly.

1 0

Re: [petsc-dev] install petsc on windows 10 with mpi
by Mohammad S Dodaran 05 Feb '17

05 Feb '17

Satish, Thanks for your quick response. as you see I can ls to the directory: ls /cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include/ mpi.f90 mpi.h mpif.h mpio.h mspms.h pmidbg.h x64/ x86/ but I do not know why still it has the same problem. and my configure file looks strange. Best, Mohammad ________________________________ From: Satish Balay <balay(a)mcs.anl.gov> Sent: Sunday, February 5, 2017 10:58:35 PM To: Mohammad S Dodaran Cc: petsc-dev(a)mcs.anl.gov Subject: Re: [petsc-dev] install petsc on windows 10 with mpi Try to figureout path without spaces. cygpath -u `cygpath -s -m PATH` Make sure you can do "ls" on this path. And use it with petsc configure. balay@ps4 ~ $ cygpath -u `cygpath -s -m /cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include` /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include balay@ps4 ~ $ ls /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include mpi.f90 mpi.h mpif.h mpio.h mspms.h pmidbg.h x64 x86 balay@ps4 ~ $ For ex: - I use: >>>>>>>> $ cat config/examples/arch-mswin-intel.py #!/usr/bin/python if __name__ == '__main__': import sys import os sys.path.insert(0, os.path.abspath('config')) import configure configure_options = [ '--download-fblaslapack=1', '--with-cc=win32fe icl', '--with-cxx=win32fe icl', '--with-fc=win32fe ifort', '--with-mpi-include=[/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include/,/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include/x64]', '--with-mpi-lib=[/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/msmpifec.lib,/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/msmpi.lib]', '--with-mpiexec=/cygdrive/c/PROGRA~1/MICROS~2/Bin/mpiexec', '--with-shared-libraries=0', 'DATAFILESPATH=c:/cygwin64/home/petsc/datafiles', ] configure.petsc_configure(configure_options) <<<<<<<<<<< if you still have issues - send us configure.log for the failure. Satish On Sun, 5 Feb 2017, Mohammad S Dodaran wrote: > Dear Petsc developers, > > I am trying to install Petsc on windows 10 but I have a problem. I installed MS-MPI v8<http://go.microsoft.com/FWLink/p/?LinkID=389556> separately and in the configure options I use > > --with-mpi-include="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include" --with-mpi-lib="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Lib/x64/msmpi.lib" > > > But it gives error which says: > > *************************************************************** > ERROR in COMMAND LINE ARGUMENT to ./configure > ------------------------------------------------------------------------------- > Invalid directory: [/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include for key with-mpi-include > > > How should I solve it? > > Mohammad >

1 0

Re: [petsc-dev] confused about DMFOREST
by Tobin Isaac 05 Feb '17

05 Feb '17

On Fri, Feb 03, 2017 at 04:52:20PM -0600, Barry Smith wrote: > > I am confused about the organization of DMFOREST, and think it could be refactored to be clearer. > > It seems DMFOREST is like an abstract based class in that it can't actually do anything itself to manage a forest. Meanwhile DMP4EST and DMP8EST provide implementations of DMFOREST for 2 and 3 dimensions. There is this weird shit DMForestRegisterType(DMType); and DMIsForest(DM,PetscBool*); to try to manage the fact that though DMP4EST and DMP8EST are conceptually subclasses of DMFOREST they are actually implemented as subclasses of DM. > > Question: Will p4est and p8est be the only implementations of DMFOREST or is there a thought there may be other implementations of DMFOREST in the future (be realistic)? Note that p4est and p8est are really a single implementation for different dimensions. > > > If the answer is: they will be the only implementations of DMFOREST then I think the code should be refactored so DMP4EST and DMP8EST as well as DMForestRegisterType(DMType); and DMIsForest() don't exist and then setup for DMFOREST directly sets the function pointers depending on the dimension to p4est or p8est functions. Much clearer conceptually. > > If the answer is: there will/should be more implementations for DMFOREST then I think the code should be refactored so that there exists a DMFORESTType, DMFORESTRegister(), DMFORESTP4EST, DMFORESTP8EST etc so that these implementations are conceptually and in the code a subclass (subtype) of DMFOREST. This would be clearer for users than the strange hybrid DMP4EST is a subclass of DMFOREST but isn't really that is currently implemented. > > In both cases the actually code changes that need to be made are relatively small. > > Am I totally missing something in my understanding? Is there a reason for this half-plant/half-animal implementation? I don't think you missed anything. I wrote DMFOREST with the intent of supporting other implementations. I know of at least one more project in the works that would be a good candidate for DMFOREST, but that doesn't mean it will get done. I think you're right that if that's the case then p4est and p8est should properly subclass. But in that case, it seems strange to me that DMFOREST implements so little of the core dm ops for its descendants. To me DMFOREST feels more like an interface than a base class. Toby > > Barry > > > >

1 0

Re: [petsc-dev] install petsc on windows 10 with mpi
by Satish Balay 05 Feb '17

05 Feb '17

Try to figureout path without spaces. cygpath -u `cygpath -s -m PATH` Make sure you can do "ls" on this path. And use it with petsc configure. balay@ps4 ~ $ cygpath -u `cygpath -s -m /cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include` /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include balay@ps4 ~ $ ls /cygdrive/c/PROGRA~2/MICROS~2/MPI/Include mpi.f90 mpi.h mpif.h mpio.h mspms.h pmidbg.h x64 x86 balay@ps4 ~ $ For ex: - I use: >>>>>>>> $ cat config/examples/arch-mswin-intel.py #!/usr/bin/python if __name__ == '__main__': import sys import os sys.path.insert(0, os.path.abspath('config')) import configure configure_options = [ '--download-fblaslapack=1', '--with-cc=win32fe icl', '--with-cxx=win32fe icl', '--with-fc=win32fe ifort', '--with-mpi-include=[/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include/,/cygdrive/c/PROGRA~2/MICROS~2/MPI/Include/x64]', '--with-mpi-lib=[/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/msmpifec.lib,/cygdrive/c/PROGRA~2/MICROS~2/MPI/lib/x64/msmpi.lib]', '--with-mpiexec=/cygdrive/c/PROGRA~1/MICROS~2/Bin/mpiexec', '--with-shared-libraries=0', 'DATAFILESPATH=c:/cygwin64/home/petsc/datafiles', ] configure.petsc_configure(configure_options) <<<<<<<<<<< if you still have issues - send us configure.log for the failure. Satish On Sun, 5 Feb 2017, Mohammad S Dodaran wrote: > Dear Petsc developers, > > I am trying to install Petsc on windows 10 but I have a problem. I installed MS-MPI v8<http://go.microsoft.com/FWLink/p/?LinkID=389556> separately and in the configure options I use > > --with-mpi-include="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include" --with-mpi-lib="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Lib/x64/msmpi.lib" > > > But it gives error which says: > > *************************************************************** > ERROR in COMMAND LINE ARGUMENT to ./configure > ------------------------------------------------------------------------------- > Invalid directory: [/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include for key with-mpi-include > > > How should I solve it? > > Mohammad >

1 0

install petsc on windows 10 with mpi
by Mohammad S Dodaran 05 Feb '17

05 Feb '17

Dear Petsc developers, I am trying to install Petsc on windows 10 but I have a problem. I installed MS-MPI v8<http://go.microsoft.com/FWLink/p/?LinkID=389556> separately and in the configure options I use --with-mpi-include="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include" --with-mpi-lib="/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Lib/x64/msmpi.lib" But it gives error which says: *************************************************************** ERROR in COMMAND LINE ARGUMENT to ./configure ------------------------------------------------------------------------------- Invalid directory: [/cygdrive/c/Program\ Files\ $x86$/Microsoft\ SDKs/MPI/Include for key with-mpi-include How should I solve it? Mohammad

1 0