FEAP User Forum
FEAP => FE^2 => Topic started by: cri on March 21, 2018, 08:36:30 AM
-
Dear all,
I'm trying to install the fe2 part of FEAP. I have a basic question. I have read that the basic steps should be (as FEAP_Admin suggested): (a) install an MPI library, (b) compile the files in the fe2 folder into a library, (c) build a new executable using main/feap85.f, the main FEAP archive/library, the fe2 library, and the mpi libraries. Should I have also a PETSc library as for the parallel part of FEAP?
Thank you in advance
-
petsc is optional. The only part of a petsc build that you would use with fe2feap would be the mpi compilers (assuming you built them as part of your petsc build). you only need an mpi implementation.
-
Thank you for your quick response. I have some problems in running the fe2 version, probably because I'm working on windows (I have read that the parallel part of FEAP has only been tested under unix-like environments). However I saw that in the 'pstart' routine the 'ntasks' number is set equal to 1 for the serial version, but this number has to greater than 1 for the multi-scale analysis. Where does the program set a 'ntask' number different than 1?
-
If you look in fe2/mpi_start.f you will see a call to mpi_comm_size( ).
-
Thank you, I saw that and I'm understanding how the program works.
I'm finalizing the fe2 installation, but I obtain the following error:
'error LNK2019: unresolved external symbol _CINPUT referenced in function _TINPUT tinput.obj'
Do you have any suggestions?
Thank you in advance
-
It should be loaded when you compile the x11u.c file in ./unix directory.
If you are doing a windows load then you should not have any reference to this. What is your operating system and version of compilers.
-
I'm doing a windows load and I'm using fortran in Visual Studio 2012.
-
In the fe2 directory the file 'tinput.f' has a call to 'cinput'. It is not necessary and you can change to use the 'read' line that is currently commented.
-
thank you so much. Now there are no errors!!!