• Registered: 05-08-2011
  • Posts: 3

Topic: problems when running OOFEM

Dear Sir,

I have problems with running a test case in oofem.
I have installed the oofem-2.0-package according to the instructions and also tested the oofem package in the specific target maps, i.e. oofem and poofem. In the last step of the installation the guide is:

[4] Running oofem and oofeg
==============================================================================
The oofem program prints out the available options when run without
any option. To run a specific job, you can enter

oofem -f input_file_name

I would appreciate if I could be guided how to run a simple test case.
I have tried to copy an inputfile from the folder: /tests/sm/rigarm01.in to /targets/oofem-2.0/bin where the executable file 'oofem' is and tried to run from here. However, in this case I get the following message when I type  oofem -f rigarm01.in:
- bash: oofem: command not found

I wonder if I need to add some path into my bashrc file or ?

many thanks for your help.
kind regards
AlpCes

  • Registered: 05-08-2011
  • Posts: 3

Re: problems when running OOFEM

I also have tried to run a test case when I am in the oofem-2.0 map according to:
targets/oofem-2.0/bin/oofem -f tests/sm/cantilever_Qspace.in

In this case I get the following error message:
targets/oofem-2.0/bin/oofem: error while loading shared libraries: libmpi.so.1: cannot open shared object file: No such file or directory

I am confused, and really looking forward to a quick and simple guide.
Many THANKS!

3 Reply by bp

  • bp
  • Administrator
  • Offline
  • From: Prague, Czech Rep.
  • Registered: 02-03-2007
  • Posts: 640

Re: problems when running OOFEM

Hi,
yes, if you just want to type "oofem" and run the code, you should add the patch to oofem executable into your PATH variable. This can be done by editing your .bashrc or .profile files. Or you should specify the full path to the oofem executable.

In your second post, it seems to me that the oofem you are using has been configured to use mpi libraries (by specifying poofem target, or turning on petsc support, etc). I would recommend to start with plain serial target, configured without parallel (poofem) support. Then the example should work.

Borek

bp's Website