FEAP in batch mode

[Camilo Valencia]

Hello all

I am running FEAP in batch mode. Is there any way to run it without seeing the graphic user interface?

Regards
Camilo Valencia

[Prof. R.L. Taylor]

You can try the following:

1. Use the pstart.f from 'unix' directory instead of the one in the 'windows' directory.

2. Compile the program without files from the 'plot directory'

3. Use the dummy  'pplotf.f' file in the 'main' directory.

Sorry I cannot test as I do not have a windows machine available right now.

You will not be able to get any graphics output with this form.

There are two graphics interfaces available on windows: One uses files in 'window1' and the other form 'window2',
which are you using?

[Camilo Valencia]

Hello Prof. Taylor.

Thank you for your ansewr. I am using the files from the 'windows1' directory.

[Prof. R.L. Taylor]

FEAP allows a form with 'window2'  that may let you see more of your text inputs.  It still is a QuickWin development so takes over the screen.  You would have to build a 'console' application with no graphics to have it in its own window   FEAPpv only has the one form and you need to delete graphics to get the console application.

[M. Kurdi]

Dear Sir,
I tried the steps recommended for getting FEAP to run from script file, but I would like to describe them from my point of view before asking my question.
1. I deleted pstart.f from windows directory, then replaced the file with pstart.f from unix directory.
2. Deleted the 'plot directory' from the lib83 project solution.
3. Created a new directory called main in the lib83 project solution and inserted the dummy file pplot.f which is available in the main directory of feap ver83 directory. (also tried inserting pplot.f in the main directory under the contact directory).
4. Build lib83 project (this step was successful)
5. Build feap project (this step resulted in linking errors due to missing plot files.

Step 5 does not work. It seems that the plot files are needed. Attached is the output. Any recommendations to resolve this?

Thanks for your help,

Mohammad

[Prof. R.L. Taylor]

Can you send a list of the files that you say are missing.  There are probably several files in windows and/or windows2/1 that are also graphics files

[M. Kurdi]

I was able to build the executable successfully in the graphic mode. These problems arise in due to removing the plot directory. I should have all the files as this is academic license. How can I find out the missing files? Thanks.

[FEAP_Admin]

The question is not what files are missing.  It is to make sure that you remove all the files that have calls to graphics routines.
The build error should tell you what is be searched for an not found...these will names of files that are still be referred in other
parts of the libraries.   Likely something out of the windows folders.

The fix is to create dummy *.f files for whatever it complains about.

[M. Kurdi]

Thanks. Will try this out.

[FEAP_Admin]

It is clear that you are not using a dummy pplotf.f since you are receiving unsatisfied external errors from pplotf.f!

[M. Kurdi]

I was using the dummy pplotf.f file. The problem is that I didn't build the library correctly. I was building using the "build solution" option in Visual Studio whereas I needed to build the library instead, so the new dummy pplotf.f is used. All due to incorrect interpretation of the "build" options in studio.
So I in addition to pplotf.f the following fortran files in the plot directory must be created as dummy and added to the source code to replace the deleted plot directory:
UPLTLIB
FPPLCL
FPPLCL
ETCLP
PDEFM
PLTORD
PLTORD
PPBOX
PLFTYP
PLTSTR
PLBORD
PFEAP
VECP
FPPCOL
PLTSYM
PLTSYM
ZOOM
PLOTL
PLTLFL
FPPSIN
FPPSDU
FPTPLT
FPPLPS

This implementation now works. However the main questions is why would we want to remove the plotting capability from FEAP. Is it possible to run in batch mode with no graphics then when needed call the graphic functions?

[Prof. R.L. Taylor]

In windows it is currently not possible to run as you describe with a single compile.  You would need to build two programs: one with graphics and one without.

In the Unix build you do not get graphics unless you include it in your solution.  Thus, a single build suffices.