Instructions for Compiling FAST

[Jason.Jonkman]

Dear Dhaneesh,

The input file handling in Seismic does not appear to be very robust. Looking at the UserPtfmLd.f90 source file, the seismic input filename is hard coded and limited to 128 characters in length, including path. It appears that--due to the long pathname (with many subdirectories)--that you've exceeded the 128 character limit. I would suggest either changing the UserPtfmLd.f90 source file to use more than 128 characters or not using so many subdirectories.

Best regards,

[Dhaneesh.Machavarapu]

Sir,

I tried reducing the subdirectories so that it shouldn't exceed the character(128) limit. Even though FAST was not running. The messaged showed like this. Was it telling that there is something wrong while compiling seismic and Fast? If it is Can I know where?


C:\Users\Bhargav>E:\Seismic\FAST.exe E:\Seismic\NRELOffshrBsline5MW_Onshore.fst

Running NWTC Subroutine Library (v1.07.00b-mlb, 10-Jan-2013).

Running FAST (v7.02.00d-bjj, 20-Feb-2013).

Heading of the FAST input file: NREL 5.0 MW Baseline Wind Turbine for Use in Offshore Analysis.

Running NWTC Subroutine Library (v1.07.00b-mlb, 10-Jan-2013).

Running AeroDyn (v13.00.02a-bjj, 20-Feb-2013).
Heading of the AeroDyn input file: NREL 5.0 MW offshore baseline aerodynamic input properties;
Compatible with AeroDyn v12.58.

Running NWTC Subroutine Library (v1.07.00b-mlb, 10-Jan-2013).

Using InflowWind (v1.02.00c-bjj, 23-Apr-2013)

Assuming E:\Seismic\WindData\NoShr_12.wnd is a formatted HH wind file.

Running NWTC Subroutine Library (v1.07.00b-mlb, 10-Jan-2013).
Reading 3 lines of data from the HH wind file.


Initializing seismic parameters

forrtl: severe (408): fort: (18): Dummy character variable 'FILENAME' has length 128 which is greater than actual variable length 41

Image PC Routine Line Source
libifcoremdd.dll 642D444F Unknown Unknown Unknown
FAST.exe 00FBF544 _SEISMIC_mp_CHECK 677 UserPtfmLd_Seismic.f90
FAST.exe 00FAF828 _SEISMIC_mp_READS 219 UserPtfmLd_Seismic.f90
FAST.exe 00FE072F _USERPTFMLD 1801 UserPtfmLd_Seismic.f90
FAST.exe 010BEBAE _FASTSUBS_mp_PTFM 4698 FAST.f90
FAST.exe 01239117 _FASTSUBS_mp_RTHS 6699 FAST.f90
FAST.exe 01293F8A _FASTSUBS_mp_SOLV 7945 FAST.f90
FAST.exe 012A583A _FASTSUBS_mp_TIME 8335 FAST.f90
FAST.exe 01475E0A _MAIN__ 104 FAST_Prog.f90
FAST.exe 014808FF Unknown Unknown Unknown
FAST.exe 01482563 Unknown Unknown Unknown
FAST.exe 01482437 Unknown Unknown Unknown
FAST.exe 014822DD Unknown Unknown Unknown
FAST.exe 014825C8 Unknown Unknown Unknown
KERNEL32.DLL 75166359 Unknown Unknown Unknown
ntdll.dll 771F7C24 Unknown Unknown Unknown
ntdll.dll 771F7BF4 Unknown Unknown Unknown

[Jason.Jonkman]

Dear Dhaneesh,

As far as I can tell, there is a small bug in how strings are passed within the UserPtfmLd_Seismic.f90 source file. Changing the following line in SUBROUTINE CheckFileExists() from:

Code: Select all

CHARACTER(128), INTENT(IN )         :: fileName

to

Code: Select all

CHARACTER(*), INTENT(IN )         :: fileName

should fix this error, but there may be other bugs in the source code. My guess is this was not noticed before because the newer Fortran compilers check different things.

Best regards,

[Dhaneesh.Machavarapu]

Sir,

I made that change in UserPtfmLd_Seismic.f90 as you suggested earlier even though I was having the same problem of initializing seismic parameters. I tried to make changes to those lines mentioned in the message but it didn't work because of my poor coding skills and I was having the same message displayed in my command prompt window. As you mentioned earlier, new Fortron compilers can't check these bugs. How can I identify and fix these bugs so that I can run Fast?

Thank you.

[Jason.Jonkman]

Dear Dhaneesh,

I'm not understanding your reply. Did you change that one line of code in source file UserPtfmLd_Seismic.f90, recompile, and rerun? If so, what error message are getting?

Best regards,

[Dhaneesh.Machavarapu]

Sir,

This was the error message I was getting after changing the line to CHARACTER(*) in SUBROUTINE CheckFileExists(), SUBROUTINE ReadMotionFile() and SUBROUTINE TargetResponse() in UserPtfmLd_Seismic.f90 and then recompiling.

Initializing seismic parameters

Using Seismic file E:\Seismic\NRELOffshrBsline5MW_Onshore_Seismic.dat

Using E:\Seismic\El_Centro_0.0050_270_value.dat for X motion file

Done reading motion file: E:\Seismic\El_Centro_0.0050_270_value.dat

Using E:\Seismic\El_Centro_0.0050_180_value.dat for Y motion file

Done reading motion file: E:\Seismic\El_Centro_0.0050_180_value.dat

Using E:\Seismic\El_Centro_0.0050_180_value.dat for Z motion file

Done reading motion file: E:\Seismic\El_Centro_0.0050_180_value.dat

Done Making ACC Input file for RSPM09

Done opening target response file

Done converting units for PSA

Done making All-Files

Done making RUN1.INP

Done making RUN2.INP

Done making RUN3.INP

'rspm09.exe' is not recognized as an internal or external command,
operable program or batch file.

The input file, "E:\Seismic\El_Centro_0.0050_270_value_TGT_RUN4.unm", was not found.

Aborting FAST.

Does rspm09 application will also be generated along with FAST application after compiling? If that so I didn't found rspm09 application after compiling.

Thank you

[Jason.Jonkman]

Dear Dhaneesh,

OK, so, it looks like that one line of code change fixed the original problem you were facing.

The error regarding rspm09.exe is triggered because that executable cannot be found. rspm09.exe is an executable provided in the Seismic archive. Make sure that it is included in the search path, or simply place it in the same directory as your compiled FAST executable.

Best regards,

[Dhaneesh.Machavarapu]

Sir,

I have placed the rpsm09.exe in the same directory folder as FAST.exe which I got after compiling and tried to run fast. Even though the same error message was displayed.

'rspm09.exe' is not recognized as an internal or external command,
operable program or batch file.

The input file, "E:\Seismic\El_Centro_0.0050_270_value_TGT_RUN4.unm", was not found.

Aborting FAST.

[Jason.Jonkman]

Dear Dhaneesh,

What happens when you try to run rspm09.exe by itself. Enter rspm09 at the command prompt and type enter.

Backing up, what was the reason that you need to recompile FAST v7 with Seismic in the first place? Were you not able to use the FAST with Seismic executable (FAST.exe) provided in the archive for some reason?

Best regards,

[Dhaneesh.Machavarapu]

Sir,

When I run rspm09 itself. Run files have been generated for only x-direction MotionFile(El_Centro_0.0050_270_value). And the reason behind recompiling is nothing much, Even when I ran with FAST.exe provided in the archive I got same error, so I thought it would be better If I recompile Fast. But even after recompiling I end up getting the same error.

Can I get some help regarding this?

[Jason.Jonkman]

Dear Dhaneesh,

Are you saying you get the same error regarding rspm09.exe when you run the FAST.exe provided in the Seismic archive? But you can run rspm09.exe apart from FAST without error? That doesn't really make sense to me.

I suppose you could generate the input file for rspm09.exe ('runrspm.txt') yourself based on how it is generated automatically by FAST.exe, in which case FAST.exe will not need to call rspm09.exe.

Otherwise, I'm not sure how to help. I'm not an expert on the Seismic source code, which was developed by a subcontractor to NREL. And NREL has not yet been funded to review/improve Seismic for inclusion in more up-to-date versions of FAST / OpenFAST.

Best regards,

[Dhaneesh.Machavarapu]

Sir,

Now I was able to run rspm09.exe and Fast.exe in the archive without any error and was able to generate the output.

The turbine mass is 697460.50 kg.
The total mass is 1397460.50 kg.
WARNING message from DISCON.DLL:
Running with torque and pitch control of the NREL offshore 5MW baseline wind turbine from
DISCON.dll as written by J. Jonkman of NREL/NWTC for use in the IEA Annex XXIII OC3 studies.

Total Real Time: 53.001 seconds
Total CPU Time: 47.188 seconds
Simulated Time: 500 seconds
Time Ratio (Sim/CPU): 10.596

FAST terminated normally.

Thank you.

[Jason.Jonkman]

Yeah!

[Dhaneesh.Machavarapu]

Sir,

In the Seismic module of FAST, does the platform has particular dimensional specifications as NREL 5MW turbine?. Or we can specify platform reference point at some depth from Ground level.

Thank you.

[Jason.Jonkman]

Dear Dhaneesh,

You should be able to set the vertical location of the platform reference point (PtfmRef) in FAST v7 / Seismic to be different from 0.0, if that is what what you want. (PtfmRef = 0.0 corresponds to the ground level).

Best regards,