Instructions for Compiling FAST

Provide feedback, request enhancements, and get help with wind-turbine computer-aided engineering tools.

Moderators: Bonnie.Jonkman, Jason.Jonkman

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Thu Jan 10, 2013 11:19 am

Dear Ramzan,

The ifort warning appears because your COMPOPTS variable doesn't contain spaces between the various compiler switches. Your code:

Code: Select all

SET COMPOPTS=/threads/O2/inline:speed/traceback/Qzero/Qsave/real_size:32/assume:byterecl
should instead be:

Code: Select all

SET COMPOPTS=/threads /O2 /inline:speed /traceback /Qzero /Qsave /real_size:32 /assume:byterecl


However, it looks to me that the bigger issue is these two errors in the NWTC Library's SysIVF.f90 file:
C:\Documents and Settings\Ramzan\Desktop\NTWC_Library\Source\SysIVF.f90(552): Error: Not a valid value for the char-expr in this connect-spec. ['STREAM'] OPEN( Un, FILE=TRIM( OutFile ), STATUS='UNKNOWN', FORM='UNFORMATTED' , ACCESS='STREAM', IOSTAT=IOS )
--------------------------------------------------------------------------------
C:\Documents and Settings\Ramzan\Desktop\NTWC_Library\Source\SysIVF.f90(594): Error: Not a valid value for the char-expr in this connect-spec. ['STREAM'] OPEN( Un, FILE=TRIM( InFile ), STATUS='OLD', FORM='UNFORMATTED', ACCESS='STREAM', IOSTAT=IOS, ACTION='READ' )


Apparently your older compiler doesn't like the "STREAM" access, which is a standard Fortran 2003 feature. I tested this on IVF 10.1 (and it worked) before we moved to the new standard method, but it looks like you have IVF 10.0. So, you can either (1) update your compiler with a newer version or (2) change the ACCESS='STREAM' in SysIVF.f90 as indicated below:

Line 552 for IVF 10.0 >>

Code: Select all

OPEN( Un, FILE=TRIM( OutFile ), STATUS='UNKNOWN', FORM='BINARY' , ACCESS='SEQUENTIAL', RECL=RecLen , IOSTAT=IOS )

Line 594 for IVF 10.0 >>

Code: Select all

OPEN( Un, FILE=TRIM( InFile ), STATUS='OLD', FORM='BINARY', IOSTAT=IOS, ACTION='READ'  )


Hope that helps.

P.S. Thanks, Mark, for helping to answer some compiling questions!
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Ramzan.Luhur
Posts: 10
Joined: Tue Jan 08, 2013 3:30 am
Organization: University of Oldenburg
Location: Germany

Re: Instructions for Compiling FAST

Postby Ramzan.Luhur » Wed Jan 16, 2013 8:46 am

Dear Mark and Bonnie,

Thanks for the guidance and sorry for late response due to undergoing a scheduled minor surgery.
I have tried your suggestions and got rid of very few initial errors specially connected to SysIVF.90 by trying Bonnie's (2) Option "change of ACCESS='STREAM'". However still getting the series of errors as in text file attached herewith.

TemporaryOutput.txt
(36.25 KiB) Downloaded 535 times


I have not yet tried with Bonnie's (1) option i.e. "update your compiler with a newer version"

Best regards,
Ramzan

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Wed Jan 16, 2013 9:56 am

Hi Ramzan,

The first error in your file now says it can't open the compiled ModMesh module file. ModMesh.f90 is a new file in recent versions of the NWTC Library, which wasn't available when the version of FAST you have was released.

I'd recommend downloading an older version of the NWTC Library and compiling with that... the FAST website should tell you what version it was compiled with.

You can also add the ModMesh.f90 file to the compile script, but the library has undergone a lot of changes recently, and you may have to update a few more things in the code to get it to work.
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Ramzan.Luhur
Posts: 10
Joined: Tue Jan 08, 2013 3:30 am
Organization: University of Oldenburg
Location: Germany

Re: Instructions for Compiling FAST

Postby Ramzan.Luhur » Wed Jan 16, 2013 11:57 am

Dear Bonnie,

Thanks a lot. It worked now by downloading the older version of NWTC_Library as suggested by you.
The compilation takes 3 to 4 minutes in my case.

Best regards,
Ramzan

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Fri Apr 19, 2013 1:26 am

Hi,

I'm doing my final year proyect. I'm trying to study de forces in the box of a wind turbine offshore. I have to use Fast and ADAMS. First of all, I run a file with the Fast.exe and I get another file with .adm extension that I have to introduce in ADAMS/view. If I open ADAMS with this file and try to run, I have lots of problems with the subroutines.
With the A2AD I run the CompileLinkA2AD.bat and I get de file ADAMS.f90, that I have to compile it to get the .dll that I have to introduce in ADAMS/view. This file, I try to compile it with Force 2.0, but there's lots of incompatibilities, so I download the Intel Visual Fortran , and the Microsoft Visual Studio 2010. I open de ADAMS.f90 with the Microsoft Visual Studio and I get this error when I try to debugg:

[i]Error 2 This number is outside the allowable range for 32-bit signed integers C:\Documents and Settings\Lucia\Mis documentos\Visual Studio 2010\Projects\ConsoleApplication2\ConsoleApplication2\Program.fs 358 34 ConsoleApplication2[i]

I don't know what I have to do. I don't know if I have to do other things to can run the ADAMS/view with the Fast files. I don´t know if the file that i get with A2AD is not the correct and I have to find other. I don´t know how to compile well.

Somebody could help me, please?

Thanks, Lucia.

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Mon Apr 22, 2013 10:35 am

Lucia,

Compiling the DLL for Adams can be tricky because you need to make sure all of the versions of the software you are linking together are compatible. The CompileLinkA2AD.bat script is designed to compile the A2AD/AeroDyn/InflowWind/NWTC Subroutine library (etc) source files and link them with Adams files to create a DLL. You should not compile the Adams.f90 file in Visual Studio.

Which versions of FAST and Adams are you using?
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Tue Apr 23, 2013 1:26 am

Boniie,

First of all thanks. I'm using the Adams 2005, the Intel Visual Fortran 2013, and the Fast, I'm using the last version that you can dowloand.

Other problem that I have is the wind files. When I edit the compile_ Fast.bat I have to change the local paths:

SET Wind_Files=
SET Wind_Files=%Wind_Files% "%Wind_Loc%\SharedInflowDefs.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\HHWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\FFWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\HAWCWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\FDWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\CTWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\UserWind.f90"
SET Wind_Files=%Wind_Files% "%Wind_Loc%\InflowWindMod.f90"

But when I downloaded Fast with its files, the wind file is called by the turbSim and there isn't the same files that in the wind files, so I dont know if I have to change everything.

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Tue Apr 23, 2013 2:52 pm

Hi, Lucia.

I do not think Adams 2005 will work with IVF 2013. You will probably have to use an older version of the compiler (or ask the support personel at MSC.Adams if they can help). We use Adams 2008 with IVF 10.1 and/or 11.1. We have had trouble using IVF 12 because the compiler uses some libraries that Adams doesn't know about when it tries to link everything together.

The wind files mentioned in the compile script are found in the InflowWind archive; they are not TurbSim source files. The instructions in the first post of this thread show you which lines in the Compile_FAST.bat script that you will have to change. You shouldn't have to change any other lines.

Hope that helps.
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Wed Apr 24, 2013 1:31 am

Thanks Bonnie, it's perfect that you help me.

When I run de compilelinkA2AD.bat appears the file ADAMS.f90, is this that I have to compile to create a .dll? I try to open with de Microsoft Visual studio, but I have lots of problems so I think that you're right and the problems is the incompatibility of the programs. Do you know other way to do it?

Thats so much.

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Wed Apr 24, 2013 10:55 am

The ADAMS2AD CompileLinkA2AD.bat script does several things:
  • Sets up the paths and variables that are necessary when you call the Intel Fortran Compiler compiler from the command line,

  • Concatenates all of the source files that are needed into two files: (1) Adams.f90, which contains all of the free-format Fortran files and (2) Adams.f, which contains the fixed-format Fortran files,
  • Compiles Adams.f90 and Adams.f (using the Intel Fortran Compiler) to create the object files Adams.obj and Adamsf.obj,
  • Links Adams.obj and Adamsf.obj with Adams libraries (which is done by calling Adams 2008r1) to create the DLL (called Adams08r1.dll unless you change it in CompileLinkA2AD.bat), and
  • Deletes the intermediate files that are created when compiling (i.e., deletes all of the *.mod and *.obj files).
All of the compiling and linking is done in this script--you do not have to open Visual Studio at all.

You need to have compatible versions of Adams and the IVF compiler, otherwise you will just be frustrated and wasting time with this. I think you should be able to use Adams 2005, but you will have to change CompileLinkA2AD.bat to use it instead of Adams 2008r1. And as I mentioned earlier, you will need an older version of the compiler (I think IVF 10.1 will work).

If you can use Adams 2008 and aren't making changes to any of the A2AD source code, you can use the dlls supplied in the A2AD archive instead of trying to compile them.
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Fri May 03, 2013 2:06 am

Hello,

I continue with the problems in ADAMS and the compatibilities with the comlers, but now, I've other problem whith Fast. When I execute the file CompileLinkA2AD.bat , I asociate with the Intel Visual Fortran 2013 and with ADAMS, but in de cmd appears :


Compiling ADAMS2AD and AeroDyn routines to create ADAMS.obj:
"ifort" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
"ifort" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
Linking ADAMS2AD and AeroDyn routines with ADAMS 2005r2:
"ADAMS05r2" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
No se encuentra C:\Documents and Settings\Lucia\Escritorio\PROYECTO\ADAMSADAMS\D
LL\*.mod
No se encuentra C:\Documents and Settings\Lucia\Escritorio\PROYECTO\ADAMSADAMS\D
LL\*.obj



But I download the compiler that the Fast user guide said, I don't know why ifort is not recognized.

Thanks.

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Fri May 03, 2013 1:33 pm

For clarification, CompileLinkA2AD.bat is not part of FAST; rather it is part of a different simulator called ADAMS2AD (A2AD). So, I assume you mean that you are having trouble with Adams2AD when you say,
I continue with the problems in ADAMS and the compatibilities with the comlers, but now, I've other problem whith Fast.


ifort won't be recognized unless you have correctly called the compiler's batch script, which sets the necessary environment variables. The instructions for compiling FAST from the command line discuss how this should be done; see the section called "Set Compiler Variables" in the document listed in the first post of this thread: viewtopic.php?f=4&t=642#p2386
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Wed May 15, 2013 2:10 am

Hi,

I don't know why I can't advance. I cotinue with the CompilelinkAD2A. I think that I've changed everything that it's necessary.

Code: Select all

@ECHO OFF
REM ----------------------------------------------------------------------------
REM                   set compiler internal variables
REM ----------------------------------------------------------------------------
REM    You can run this bat file from the IVF compiler's command prompt (and not
REM    do anything in this section). If you choose not to run from the IVF command
REM    prompt, you must call the compiler's script to set internal variables.
REM    TIP: Right click on the IVF Compiler's Command Prompt shortcut, click
REM    properties, and copy the target (without cmd.exe and/or its switches) here:
REM .............................................................................
REM See this forum topic for instructions and help with setting the compiler
REM internal variables in this script:
REM    https://wind.nrel.gov/forum/wind/viewtopic.php?f=4&t=642
REM .............................................................................

IF "%INTEL_SHARED%"=="" CALL "CALL "C:\Archivos de programa\Intel\Composer XE 2013\bin\IFORTVARS.bat"

REM ----------------------------------------------------------------------------
REM -------------------- LOCAL VARIABLES ---------------------------------------
REM ----------------------------------------------------------------------------

SET ROOT_NAME=ADAMS

REM ----------------------------------------------------------------------------
REM -------------------- LOCAL PATHS ------------------------------------------
REM ----------------------------------------------------------------------------

REM --USERS WILL NEED TO EDIT THESE PATHS TO POINT TO FOLDERS ON THEIR LOCAL MACHINES:
REM A2AD_Loc     is the location of the ADAMS-to-AeroDyn source files.
REM AeroDyn_Loc  is the location of the AeroDyn source files.
REM Wind_Loc     is the location of the InflowWind souce files.
REM FAST_LOC     is the location of the FAST source files: FFTMod.f90, HydroCalc.f90, fftpack.f, UserSubs.f90, and possibly PitchCntrl_ACH.f90, UserVSCont_KP.f90, and/or BladedDLLInterface.f90.
REM NWTC_Lib_Loc is the location of the NWTC subroutine library files.
REM ----------------------------------------------------------------------------

REM NOTE: DO NOT USE QUOTATION MARKS HERE (AROUND THE PATH NAMES)
REM       OR THE FILE CONCATENATION BELOW WILL NOT WORK

SET NWTC_Lib_Loc=C:\Documents and Settings\Lucia\Escritorio\PROYECTO\NWTC_Lib\source
SET AeroDyn_Loc=C:\Documents and Settings\Lucia\Escritorio\PROYECTO\AERODYN\Source
SET Wind_Loc=C:\Documents and Settings\Lucia\Escritorio\PROYECTO\inflowWind\Source
SET FAST_Loc=C:\Documents and Settings\Lucia\Escritorio\PROYECTO\FAST\Source
SET A2AD_Loc=C:\Documents and Settings\Lucia\Escritorio\PROYECTO\ADAMSADAMS\Source

REM ----------------------------------------------------------------------------
REM -------------------- LIST OF ALL SOURCE FILES ------------------------------
REM -------- please note that all source files must have a blank line ----------
REM --------   at the end so that they can be concatenated properly   ----------
REM ----------------------------------------------------------------------------

SET NWTC_Files=
SET NWTC_Files=%NWTC_Files%   "%NWTC_Lib_Loc%\SingPrec.f90"
SET NWTC_Files=%NWTC_Files% + "%A2AD_Loc%\SysIVF_ADAMS.f90"
SET NWTC_Files=%NWTC_Files% + "%NWTC_Lib_Loc%\NWTC_IO.f90"
SET NWTC_Files=%NWTC_Files% + "%NWTC_Lib_Loc%\NWTC_Num.f90"
SET NWTC_Files=%NWTC_Files% + "%NWTC_Lib_Loc%\NWTC_Aero.f90"
SET NWTC_Files=%NWTC_Files% + "%NWTC_Lib_Loc%\ModMesh.f90"
SET NWTC_Files=%NWTC_Files% + "%NWTC_Lib_Loc%\NWTC_Library.f90"

SET Wind_Files=
SET Wind_Files=%Wind_Files%   "%Wind_Loc%\SharedInflowDefs.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\HHWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\FFWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\HAWCWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\FDWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\CTWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\UserWind.f90"
SET Wind_Files=%Wind_Files% + "%Wind_Loc%\InflowWindMod.f90"


SET AeroDyn_Files=
SET AeroDyn_Files=%AeroDyn_Files%   "%AeroDyn_Loc%\SharedTypes.f90"
SET AeroDyn_Files=%AeroDyn_Files% + "%AeroDyn_Loc%\AeroMods.f90"
SET AeroDyn_Files=%AeroDyn_Files% + "%AeroDyn_Loc%\GenSubs.f90"
SET AeroDyn_Files=%AeroDyn_Files% + "%AeroDyn_Loc%\AeroSubs.f90"
SET AeroDyn_Files=%AeroDyn_Files% + "%AeroDyn_Loc%\AeroDyn.f90"

SET Fixed_Files =
SET Fixed_Files=%Fixed_Files%   "%FAST_Loc%\fftpack.f"

SET FAST_Files=
SET FAST_Files=%FAST_Files%   "%FAST_Loc%\FFTMod.f90"
SET FAST_Files=%FAST_Files% + "%FAST_Loc%\HydroCalc.f90"
SET FAST_Files=%FAST_Files% + "%A2AD_Loc%\FAST_params.f90"

IF /I "%1"=="DLL" GOTO dllFiles
SET FAST_Files=%FAST_Files% + "%FAST_Loc%\UserSubs.f90"
SET FAST_Files=%FAST_Files% + "%FAST_Loc%\UserVSCont_KP.f90"
SET FAST_Files=%FAST_Files% + "%FAST_Loc%\PitchCntrl_ACH.f90"

GOTO endFASTfiles
:dllFiles
SET FAST_Files=%FAST_Files% + "%FAST_LOC%\UserSubs_forBladedDLL.f90"
SET FAST_Files=%FAST_Files% + "%FAST_LOC%\UserVSCont_KP_forBladedDLL.f90"
SET FAST_Files=%FAST_Files% + "%FAST_LOC%\BladedDLLInterface.f90"

REM NOTE: UserSubs_forBladedDLL.f90 is a copy of UserSubs.f90 with SUBROUTINES UserHSSBr() and UserYawCont() commented out
REM       UserVSCont_KP_forBladedDLL.f90 is a copy of UserVSCont_KP.f90 with SUBROUTINE UserVSCont() commented out

:endFASTfiles

SET A2AD_Files=
SET A2AD_Files=%A2AD_Files%   "%A2AD_Loc%\A2AD_Mod.f90"
SET A2AD_Files=%A2AD_Files% + "%A2AD_Loc%\Adams_subs.f90"

REM echo File list

REM ----------------------------------------------------------------------------
REM ----------- Concatenate them into one file for free-format -----------------
REM ----------- Fortran and one file for fixed-format Fortran  -----------------
REM ----------------------------------------------------------------------------

COPY %NWTC_Files% + %Wind_Files% + %AeroDyn_Files% + %FAST_Files% + %A2AD_Files%  %ROOT_NAME%.f90
COPY %Fixed_Files% %ROOT_NAME%.f

REM ----------------------------------------------------------------------------
REM ------- SET CREATE OBJECT FILE BASED ON SPECIFIED COMPILER -----------------
REM ----------------------------------------------------------------------------

REM ----------------------------------------------------------------------------
REM --------------------- Intel visual FORTRAN ---------------------------------
REM ---------------------   with Adams 2012R2  ---------------------------------
REM ----------------------------------------------------------------------------

REM ............................................................................
REM ..................... set compiler options .................................
REM ............................................................................

REM SET COPTS= /c /automatic /architecture:pn4 /Ob2 /MD /Gm /O1     /traceback /real_size:32 /assume:byterecl /stand:f95 /check:bounds
REM SET COPTS= /c /automatic /architecture:pn4 /Ob2 /MD /Gm /Ot /O3 /traceback /real_size:32 /assume:byterecl /stand:f95  /Qdiag-disable:5268   
SET COPTS= /c /automatic /Ob2 /MD /Gm /traceback /Qzero /Qsave /real_size:32 /assume:byterecl  /Qdiag-disable:5268

REM ............................................................................
REM ............................ compile .......................................
REM ............................................................................

ECHO.
ECHO Compiling ADAMS2AD and AeroDyn routines to create ADAMS.obj:
ifort %COPTS% /object:%ROOT_NAME%.obj %ROOT_NAME%.f90
ifort %COPTS% /object:%ROOT_NAME%f.obj %ROOT_NAME%.f

REM ............................................................................
REM ........................ link with Adams ...................................
REM ............................................................................

ECHO Linking ADAMS2AD and AeroDyn routines with ADAMS 2012r2:
SET DLLName=%ROOT_NAME%12r2
IF /I "%1"=="DLL" SET DLLName=%DLLName%_forBladedDLL

CALL C:\MSC.Software\Adams\2012\common\mdi.bat cr-user n %ROOT_NAME%.obj %ROOT_NAME%f.obj -n %DLLName%.dll exit < NewLine.txt

GOTO end

:end
REM ----------------------------------------------------------------------------
REM ------------------------- CLEAR MEMORY -------------------------------------
REM ------------- and delete all .mod and .obj files ---------------------------
REM ----------------------------------------------------------------------------
REM ECHO

DEL *.mod
DEL *.obj

SET MyCompiler=
SET DF_LOC=

SET IVF_LOC=
SET ROOT_NAME=
SET COPTS=

SET NWTC_Files=

SET Wind_Files=
SET AeroDyn_Files=
SET FAST_Files=
SET A2AD_Files=
SET Fixed_Files=

SET NWTC_Lib_Loc=
SET Wind_Loc=
SET AeroDyn_Loc=
SET A2AD_Loc=
SET FAST_Loc=   

SET DLLName=


But when I try to execute in the command window, I have several problems, so I can't create my .dll, so I can't simulate my model in ADAMS because I don't have the library .dll .

The command window displays:
(These are the last lines that appear after execution)

Code: Select all

ADAMS.f90(3758): error #8095: The name of the internal procedure conflicts with
a procedure name in the MODULE PROCEDURE statement.   [READLVAR]
   SUBROUTINE ReadLVar ( UnIn, Fil, LogVar, VarName, VarDescr, ErrStat )
--------------^
ADAMS.f90(4573): catastrophic error: Too many errors, exiting
compilation aborted for ADAMS.f90 (code 1)
Intel(R) Visual Fortran Compiler XE for applications running on IA-32, Version 1
3.1.1.171 Build 20130313
Copyright (C) 1985-2013 Intel Corporation.  All rights reserved.
ifort: command line remark #10010: option '/automatic' is deprecated and will be
 removed in a future release. See '/help deprecated'
ifort: command line warning #10121: overriding '/automatic' with '/Qsave'

Linking ADAMS2AD and AeroDyn routines with ADAMS 2012r2:

 *** Error:  File ADA not found.

 Enter name of next user object or source file (<CR>=none),  or EXIT:
forrtl: severe (24): end-of-file during read, unit -4, file CONIN$
Image              PC        Routine            Line        Source
libifcoremd.dll    100A581A  Unknown               Unknown  Unknown
libifcoremd.dll    1009FBC8  Unknown               Unknown  Unknown
libifcoremd.dll    1001C2AA  Unknown               Unknown  Unknown
libifcoremd.dll    1001B4AB  Unknown               Unknown  Unknown
libifcoremd.dll    1004D761  Unknown               Unknown  Unknown
cru.exe            00404EBD  Unknown               Unknown  Unknown
cru.exe            00407A23  Unknown               Unknown  Unknown
cru.exe            00405CA8  Unknown               Unknown  Unknown
kernel32.dll       7C81776F  Unknown               Unknown  Unknown


Could you help me, please?

Thanks

Bonnie.Jonkman
Posts: 566
Joined: Thu Nov 10, 2005 10:51 am
Organization: Envision Energy USA
Location: Colorado
Location: Boulder, CO
Contact:

Re: Instructions for Compiling FAST

Postby Bonnie.Jonkman » Wed May 15, 2013 11:41 am

Is there any way you can use Adams 2008 with IVF 10.1 or 11? I do not think you are going to be able to get our software to work with Adams 2013, which is significantly different than the Adams versions we developed the software for.
Bonnie Jonkman

Envision Energy USA, 2016-
National Renewable Energy Laboratory, 2003-2016

Lucia.RicoFdez
Posts: 12
Joined: Thu Apr 18, 2013 12:55 am
Organization: UC
Location: Spain

Re: Instructions for Compiling FAST

Postby Lucia.RicoFdez » Thu May 16, 2013 2:03 am

Hi,
Thanks for your reply.
I have the ADAMS 2005, and the ADAMS 2012. The fisrt one is that the university has for the students, and the other gave me one industial company from my city, trying to help me. My compiler is Intel Visual Fortran 2013. I try to find older versions but I don't find them. My project manager said me that could find me the ADAMS 2010, but I don't know if this version is compatible with the compiler, and with the Fast software.

Thanks


Return to “Computer-Aided Engineering Software Tools”

Who is online

Users browsing this forum: Baidu [Spider], Bitna.Seo and 1 guest