링크가 복사됨
Aditya,
It's most unfortunate to read about the problems experienced by you. Now I know nothing about Abaqus and I have no idea how one uses it with Fortran and that's why I've not posted any comments on your posts until now. However I'm noticing some barriers in communication and I strongly empathize with your problems, so I figured I'll offer some suggestions based on my general knowledge of having used user subroutines in Fortran with 3rd party software on Windows OS. My basic idea is to workaround the need to invoke Intel Fortran compiler from Abaqus but instead run the two independently. That is, compile your Fortran code separately and make the compilation output i.e., the object file (.o) available to Abaqus. This might alleviate your situation
As suggested by Steve and mecej4, please ignore the response you received from Roger Keene at the Abaqus forum; just to be clear, here's a snip of the message you are being asked to ignore: This person may have meant well, but his advice appears misleading.
A few questions next:
- Just to be on the safe side, can you confirm you are familiar with Fortran and using Fortran on Windows OS? And that you understand the concept of source file and object file? If not, please go through the user and reference guide for Intel Fortran thoroughly at https://software.intel.com/en-us/compiler_15.0_ug_f. If you are just starting off with Fortran, YouTube videos such as the one in the link provided in the next line may also be helpful. https://www.youtube.com/watch?v=GfCmiEbGtpE can you a general idea of how to work with Fortran even though this specific video is about another compiler and you'll need to extend the basic idea to Intel compiler.
- Other than the situation where you need to include user subroutines in Abaqus, does Abaqus run ok in your computing environment? That is, I assume you can create a simpler, non-Fortran test case in Abaqus and run it. Are you able to do so? If not, can you first reach a clean state by uninstalling your version of Abaqus?
- Are you able to successfully use the Fortran compiler that came with your Intel Parallel Studio XE 2015 version? That is, can you create a simple Hello World type of example (https://en.wikipedia.org/wiki/Fortran#.22Hello_world.22_example) in Fortran, compile, link, and run it? If not actually run such a program, can you at least compile the code? e.g., say you save your Fortran code in c:\temp\hello.f90: can you go to Start -> Intel Parallel Studio XE 2015 -> Compiler and Performance Libraries and select an option you might see listed under IA-32... mode. Then at the DOS-like prompt, change your folder to c:\temp, and type ifort -c hello.f90. Does this step complete without errors? If not, can you reach a clean state by uninstalling your Intel Parallel Studio XE 2015 version?
Now in steps 2 and 3, you ended up uninstalling software, reinstall them in the following order: first Microsoft Visual Studio, then Abaqus, and then Intel Parallel Studio XE 2015. Then confirm you can do the two simple tests indicated in steps 2 and 3 above. You can only proceed further if Abaqus runs for you at least when user Fortran subroutines are not involved and if you can compile Fortran code independent of Abaqus.
By the way, I suggested IA-32.. option for Intel Fortran command prompt assuming Abaqus is a 32-bit application, working with Intel IA-32 architecture; if it is a 64-bit program i.e, using the Intel 64 architecture, pick the Intel 64 option.
Now I see you're using Abaqus 6.14; even though I couldn't locate the user guide online for this version, it is available for version 6.12 here: http://www.maths.cam.ac.uk/computing/software/abaqus_docs/docs/v6.12/books/usb/default.htm. The user guide for 6.12 says you can include user subroutines in either source file form or in object form. I assume things have not changed in this regard in your 6.14 version. Assuming that to be the case, try the following: copy your exa_hydfracture.f file and aba_param.inc file (you may need to do a file search for this on your system to locate it in one of Abaqus folders) to c:\temp folder. Then follow the step as with hello.f above: go to the IA-32 command prompt for Intel Parallel Studio, type ifort -c exa_hydfracture.f to compile the file. It should create exa_hydfracture.o file; keep it handy.
Now notice in the Abaqus user guide, it says you can supply the user file is source or object form using the command such as "abaqus job=job-name user={source-file | object-file}". So instead of providing the exa_hydfracture.f file as in user=exa_hydfracture.f, try supplying the compiled exa_hydfracture.o file. This might help Abaqus figure out that no compilation is necessary and that it does not need to use ifort.exe, and bypass all the complications with PATH and ifort, and directly utilize exa_hydfracture.o file. And once Abaqus has the compiled object in the form of exa_hydfracture.o file, it should figure out how to make use of it and this stage, whether the object was created using Intel Composer 2011 or 2015 may not matter one bit. And this may allow your calculations to proceed. Would you mind giving this a shot and reporting back here?
Note if you encounter problems even with installation of Abaqus 6.14 and Intel Fortran Composer XE 2015 on the same Windows workstation, you can try installing Abaqus on one machine and Intel Parallel Studio on another, assuming you can access another station that has the same Windows OS as the first, even on a temporary basis. Then compile your exa_hydfracture.f file on the second station and simply copy over the exa_hydfracture.o file to the first station and see if you can get it to work with Abaqus.
Good luck,
