Any Aspen users integrated with oneAPI yet????

[DavidWhite]

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

[Steve_Lionel]

That 2022 post of mine is no longer valid. Unfortunately, I can no longer edit it to say so.

[lhp1]

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=
End

In 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

[Steve_Lionel]

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.