- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have any Aspen Plus users tried using Aspen Plus with the oneAPI version of the Fortran compiler?
Aspen Tech don't yet support this, but I suspect it is just a matter of adding some extensions to the config and batch files.
If you have managed this integration, would you mind sharing the changes you have made to the config and batch files.
Since I'm setting up a new Aspen Plus installation, and no longer have access to the supported 2019 and earlier versions of Fortran, I can only use oneAPI.
Thanks for any assistance anyone can provide
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just to close this in case someone else is looking in future
Even though the Aspen v12.0 install does not include the config file for the 2021 version of OneAPI Fortran, AspenTech provide an updated version of the config64.cfg file on their support website.
So quick solution is to always check for updates on the Aspen Tech support site.
Link Copied
- « Previous
-
- 1
- 2
- Next »
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Steve_Lionel Agree - it is becoming difficult to support all the changes since every version has a new wrinkle. I am sure, the developers in AspenTech are having a tough time keeping up with the changes, given that there are a shrinking number of Fortran developers and users. In regard to the runtime libraries, I refer @Steve_Lionel to the following post by you that helped solve many problems for me related to Fortran and its linkages to AspenPlus etc. Solved: PSA: Update the Runtime Library when you update the compiler! - Intel Community.
This is specifically related to the problems of another user with AspenPlus Fortran issues that I was trying to help which is under "Non compatible version of Fortran libifcore DLL was loaded to process address space" - Intel Community.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@lhp1 As confirmed by @Steve_Lionel, you do not need the missing folder. But since A+ is complaining about it, please try the following:
1. Install the file w_ifort_runtime_p_2024.0.2.49897.exe, which is found on the same location as the standalone version under Intel® oneAPI standalone component installation files Runtime Versions. Choose the .exe corresponding to your version or the latest one available.
2. If installing the above does not fix the problem, please post the following two lines from the Compilers64.cfg:
IFDir=
VCRVer=
for your version of IFORT and MSVSC. For example, IFDir and VCRVer= under "Begin IVF2024_VS17 "Intel Fortran 2024 and VS 2022 WITH C++ (and community)"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That 2022 post of mine is no longer valid. Unfortunately, I can no longer edit it to say so.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Steve_Lionel, @avinashs:
I have tried to build with a Fortran project from MSVS 2022 (see screenshot below). It gives me errors because I should compile from Aspen. However, I am not sure where MSVS gets Intel Fortran Compiler from, as the Intel Fortran Compiler that I installed is from oneAPI.
There is a weird thing, and from below IntelFortran seems to do the integration with VS2017, but I have VS2022 installed. However, IFORT.exe is in Intel\oneAPI\2024.2\bin
The latest version pointed by AspenTech Compilers64.png are MSVS2022 and Intel Fortran 2024, which are the versions I have installed on my computer.
Begin IVF2024_VS17 "Intel Fortran 2024 and VS 2022 WITH C++ (and community)"
IFDir=HKLM(SOFTWARE\WOW6432Node\Intel\Compilers\Fortran\192.###\ProductDir)
INTEL_TARGET_ARCH_IA32=
VS2022=$(ProgramFiles)\Microsoft Visual Studio\2022
VSDir=Exist($(VS2022)\Enterprise)||Exist($(VS2022)\Professional)||Exist($(VS2022)\Community)
# !!! Replace the line above with proper one below for A+ before V9 !!!
#VSDir=$(VS2022)\Enterprise
#VSDir=$(VS2022)\Professional
#VSDir=$(VS2022)\Community
KitDir=HKLM(SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows\v10.0\InstallationFolder)
KitVer=HKLM(SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows\v10.0\ProductVersion).0
VCRVer=GetVer($(VSDir)\VC\Tools\MSVC\14.??.*)
INCLUDE=$(IFDir)opt\compiler\include;$(VSDir)\VC\Tools\MSVC\$(VCRVer)\ATLMFC\INCLUDE;$(VSDir)\VC\Tools\MSVC\$(VCRVer)\INCLUDE;$(KitDir)\include\$(KitVer)\ucrt;$(KitDir)\include\$(KitVer)\shared;$(KitDir)\include\$(KitVer)\um;$(KitDir)\include\$(KitVer)\winrt
LIB=$(IFDir)lib;$(VSDir)\VC\Tools\MSVC\$(VCRVer)\ATLMFC\lib\x64;$(VSDir)\VC\Tools\MSVC\$(VCRVer)\lib\x64;$(KitDir)\lib\$(KitVer)\ucrt\x64;$(KitDir)\lib\$(KitVer)\um\x64
PATH=$(IFDir)bin;$(VSDir)\VC\Tools\MSVC\$(VCRVer)\bin\HostX64\x64;$(KitDir)\bin\x64;$(KitDir)\bin\$(KitVer)\x64;$(VSDir)\Common7\IDE;$(VSDir)\Common7\Tools;$(PATH)
USE_COMPAQ_FORTRAN=
IFDir=
VS2022=
VSDir=
KitDir=
KitVer=
VCRVer=
EndIn the Aspcomp.bat file, the "fortran command " is defined as "set comp_name=f77.exe" as seen below:
if .%USE_COMPAQ_FORTRAN% == .1 goto compaq
set comp_name=ifort.exe
...
:compaq
set comp_name=f77.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been away for a month.
The errors listed in your first screenshot suggest source errors or perhaps a missing /fpp option. Without seeing the source in question, I can't comment further. I see no evidence that the compiler was not found.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »