parfeap 8.5 on Ubuntu

[Prof. S. Govindjee]

strange you see this with 3.8.3 -- I did not.  But I know the problem occurs with version 3.9.0.
the fix is to rename mpi_start to mpi_start_feap.  do this throughout the whole code.

[blackbird]

Maybe this is an issue of MPICH version? I configured the petsc today and the log says, mpich-3.3a2 has been found in git and installed.

I changed the subroutine name (in $FEAPHOME8_5/parfeap/mpi_start.F and $FEAPHOME8_5/program/mpi_start.f) and the respective call in ($FEAPHOME8_5/unix/pstart.f) - now my benchmark problem is working fine.

Many Thanks!

[Prof. S. Govindjee]

Could be.  I normally use openmpi for the MPI interface, previously v1.8.3 but now v3.0.1.
FEAP version 8.6 will have these updates made to it.

[arktik]

Hi,

I just wanted to add here that I faced very similar problems with parallel feap installation using petsc-3.9.2. Those problems were also resolved by following the above discussion. Thanks.

Here is a summary of to do tasks for someone who is facing similar problems:
1. create module pfeapc.F to replace common block pfeapc.h.

Code: [Select]

     
      module pfeapc
#     include  <petsc/finclude/petscksp.h>
      use petscksp

      Vec      :: rhs, sol, xvec, diag
      Vec      :: yvec, zvec
      Vec      :: Mdiag, Msqrt
      Mat      :: Kmat, Mmat, Pmat
      KSP      :: kspsol, ksp

      end module pfeapc
2. find all subroutines where pfeapc.h header file is used.

Code: [Select]

grep -r 'pfeapc' ver85/
3. Add use pfeapc and comment include "pfeapc.h" in those subroutines.
4. Find all subroutines where mpi_start routine is used.

Code: [Select]

grep -r 'mpi_start' ver85/
5. Rename mpi_start to mpi_start_feap in all those subroutines as well as makefiles.
6. make install in parfeap directory.

[Prof. R.L. Taylor]

You need to change the name of our routine.  Later releases will use mpi_start_feap.F as the name.

[blackbird]

Could be.  I normally use openmpi for the MPI interface, previously v1.8.3 but now v3.0.1.
FEAP version 8.6 will have these updates made to it.

Dear Prof. Govindjee,

could you please give a little bit more detailed information on how to use openmpi with feap. Specifically, when petsc is configured, the option --download-mpich is organizing the mpi installation. Which steps are required for openmpi instead?

[Prof. S. Govindjee]

change to --download-openmpi instead of --download-mpich

[JStorm]

Please, can you provide a FEAP 8.5 release which contains all necessary changes to run ParFEAP 8.5? It is not just two or three changes and the explanation is distributed over several forum threads. Would be really nice to have a clear and unique code basis for discussion.

[Prof. R.L. Taylor]

we renamed to mpi_start_feap to avoid the conflict.  Be sure to do in both serial and parallel code where used.

[JStorm]

I think that these changes affect about 50% of the parfeap files, due to adding use pfeapc and removing include "pfeapc.h" There are also changes necessary at FEAP regarding PETSc 3.8 (http://feap.berkeley.edu/forum/index.php?topic=1880.msg7528#msg7528).

I would like to ask politely to provide a new FEAP 8.5 release with these changes. I believe that we will have issues with reporting bugs and posting FEAP improvements, if we use different code bases.

[Prof. S. Govindjee]

Yes it is a bit of a challenge to keep up with the recent releases of petsc, though following the release notes it is certainly possible to make the updates.

We are actively working on a new release (8.6) which will play nice with the latest petsc release.