Tagged: fluent, hpc-cluster, udf-fluent
-
-
February 14, 2022 at 3:17 pm
friday.abolorunke
SubscriberHello All,
Whenever I try to run fluent simulation on my university HPC it fails to compile the UDF and refuse to run. I tried running without UDF and it worked perfectly but when I included the UDF I get the follow error message from the .out file.
"faxxx/Desktop/3D_NC_v1/3dsoln/3dsolnv1_files/dp0/FFF/Fluent/libudf) is not compiled for parallel use on the current platform (lnamd64).
Auto-compilation skipped. Could not find input files required for creating "C:/Users/faxxx/Desktop/3D_NC_v1/3dsoln/3dsolnv1_files/dp0/FFF/Fluent/libudf" library
i2cmp003.pax.tufts.edu: Opening library "/cluster/home/faxxx/3dsoln/C:/Users/faxxx/Desktop/3D_NC_v1/3dsoln/3dsolnv1_files/dp0/FFF/Fluent/libudf"...rcx: couldn't decode arguments (4124).
RPC RCX_SC_SET_ERR_MSG failed: RPC: Can't encode arguments
Error at host: The UDF library you are trying to load (C:/Users/faxxx/Desktop/3D_NC_v1/3dsoln/3dsolnv1_files/dp0/FFF/Fluent/libudf) is not compiled for parallel use on the current platform (lnamd64).
No such file or directory
/cluster/home/faxxx/3dsoln/C:/Users/faxxx/Desktop/3D_NC_v1/3dsoln/3dsolnv1_files/dp0/FFF/Fluent/libudf/lnamd64/3ddp_host/libudf.so"
Meanwhile, I have the UDF in the libudf folder. And the UDF has not issues because it works fine when i compile on my desktop. The issue only comes run I transfer the case, dat and all the other files to cluster.
I have gone through some of the suggestions related to these issues on the forum. I converted the udf from dos2unix, so that’s not the issue.
I have tried using expressions to define the density, viscosity, & mass diffusivity but it seems the option to do so is not available on version 21.1.
command file
February 15, 2022 at 1:40 pmdcollier
Ansys EmployeeHello, You would need to compile the UDF on Windows first. Then login to the Linux machine and compile it again.Make sure you delete any libudf folders first.
Make sure when you load you udf you are working in the same directory as the model is located it.
--------------------------
Once you have setup your case with a udf on your windows machine, you would still need to compile on your HPC cluster which is a Linux system (to be able to run that case on HPC).
So, if you need to compile on Linux without a GUI you can just use the following two lines in your journal file (as the first 2 lines before reading the case file). Please change test.c with your udf file name, and copy case, journal, and udf files to your HPC folder for running on HPC.
/define/user-defined/compiled-functions compile "libudf" yes "test.c" ""
/define/user-defined/compiled-functions load "libudf"
February 15, 2022 at 3:28 pmfriday.abolorunke
SubscriberHi dcollier
Thank you for your quick response. I will try this and let know you the outcome.
One more question, say I have 3 udfs should I do the following:
/define/user-defined/compiled-functions compile "libudf" yes "test1.c" "test2.c" "test3.c" ""
Regards Friday
February 16, 2022 at 3:17 amfriday.abolorunke
Subscriber
February 16, 2022 at 9:56 amfriday.abolorunke
Subscriber
I made changes according to your recommendations. Now i am getting the error below. Please could you tell me what could be the cause of the issue
# linking to ../../src/density_udf.c in lnamd64/3ddp_host
# linking to ../../src/makefile in lnamd64/3ddp_host
# building library in lnamd64/3ddp_host
make[1]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# Generating udf_names.c because of makefile density_udf.c
make[2]: Entering directory `/cluster/home/xx/3dsoln/libudf/lnamd64/3ddp_host'
make libudf.so "CFLAGS=-D_lnamd64 -D_GNU_SOURCE -fpic -shared -std=c99 -Wall -O -DPTR_RESTRICT= " "LDFLAGS=-shared -lm"
make[3]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[3]: *** No rule to make target `compiled-functions', needed by `udf_names.o'.
make[3]: *** No rule to make target `write-case-data', needed by `udf_names.o'.
make[3]: *** No rule to make target `dual-time-iterate', needed by `udf_names.o'.
make[3]: *** No rule to make target `time-step', needed by `udf_names.o'.
make[3]: *** No rule to make target `0.01', needed by `udf_names.o'.
make[3]: *** No rule to make target `10', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.cas', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.dat', needed by `udf_names.o'.
make[3]: *** No rule to make target `60000', needed by `udf_names.o'.
make[3]: *** No rule to make target `exit', needed by `udf_names.o'.
make[3]: *** No rule to make target `libudf', needed by `udf_names.o'.
make[3]: *** No rule to make target `load', needed by `udf_names.o'.
make[3]: *** No rule to make target `rc', needed by `udf_names.o'.
make[3]: Target `libudf.so' not remade because of errors.
make[3]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[2]: *** [lnamd64] Error 2
make[2]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# linking to ../../src/density_udf.c in lnamd64/3ddp_node
# linking to ../../src/makefile in lnamd64/3ddp_node
Regards
February 16, 2022 at 9:56 amfriday.abolorunke
Subscriber
Hi @dcoll I made changes according to your recommendations. Now i am getting the error below. Please could you tell me what could be the cause of the issue
# linking to ../../src/density_udf.c in lnamd64/3ddp_host
# linking to ../../src/makefile in lnamd64/3ddp_host
# building library in lnamd64/3ddp_host
make[1]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# Generating udf_names.c because of makefile density_udf.c
make[2]: Entering directory `/cluster/home/xx/3dsoln/libudf/lnamd64/3ddp_host'
make libudf.so "CFLAGS=-D_lnamd64 -D_GNU_SOURCE -fpic -shared -std=c99 -Wall -O -DPTR_RESTRICT= " "LDFLAGS=-shared -lm"
make[3]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[3]: *** No rule to make target `compiled-functions', needed by `udf_names.o'.
make[3]: *** No rule to make target `write-case-data', needed by `udf_names.o'.
make[3]: *** No rule to make target `dual-time-iterate', needed by `udf_names.o'.
make[3]: *** No rule to make target `time-step', needed by `udf_names.o'.
make[3]: *** No rule to make target `0.01', needed by `udf_names.o'.
make[3]: *** No rule to make target `10', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.cas', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.dat', needed by `udf_names.o'.
make[3]: *** No rule to make target `60000', needed by `udf_names.o'.
make[3]: *** No rule to make target `exit', needed by `udf_names.o'.
make[3]: *** No rule to make target `libudf', needed by `udf_names.o'.
make[3]: *** No rule to make target `load', needed by `udf_names.o'.
make[3]: *** No rule to make target `rc', needed by `udf_names.o'.
make[3]: Target `libudf.so' not remade because of errors.
make[3]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[2]: *** [lnamd64] Error 2
make[2]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# linking to ../../src/density_udf.c in lnamd64/3ddp_node
# linking to ../../src/makefile in lnamd64/3ddp_node
Regards Friday
February 16, 2022 at 9:56 amfriday.abolorunke
Subscriber
Hi @dcoll I made changes according to your recommendations. Now i am getting the error below. Please could you tell me what could be the cause of the issue
# linking to ../../src/density_udf.c in lnamd64/3ddp_host
# linking to ../../src/makefile in lnamd64/3ddp_host
# building library in lnamd64/3ddp_host
make[1]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# Generating udf_names.c because of makefile density_udf.c
make[2]: Entering directory `/cluster/home/xx/3dsoln/libudf/lnamd64/3ddp_host'
make libudf.so "CFLAGS=-D_lnamd64 -D_GNU_SOURCE -fpic -shared -std=c99 -Wall -O -DPTR_RESTRICT= " "LDFLAGS=-shared -lm"
make[3]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[3]: *** No rule to make target `compiled-functions', needed by `udf_names.o'.
make[3]: *** No rule to make target `write-case-data', needed by `udf_names.o'.
make[3]: *** No rule to make target `dual-time-iterate', needed by `udf_names.o'.
make[3]: *** No rule to make target `time-step', needed by `udf_names.o'.
make[3]: *** No rule to make target `0.01', needed by `udf_names.o'.
make[3]: *** No rule to make target `10', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.cas', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.dat', needed by `udf_names.o'.
make[3]: *** No rule to make target `60000', needed by `udf_names.o'.
make[3]: *** No rule to make target `exit', needed by `udf_names.o'.
make[3]: *** No rule to make target `libudf', needed by `udf_names.o'.
make[3]: *** No rule to make target `load', needed by `udf_names.o'.
make[3]: *** No rule to make target `rc', needed by `udf_names.o'.
make[3]: Target `libudf.so' not remade because of errors.
make[3]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[2]: *** [lnamd64] Error 2
make[2]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# linking to ../../src/density_udf.c in lnamd64/3ddp_node
# linking to ../../src/makefile in lnamd64/3ddp_node
Regards Friday
February 16, 2022 at 9:56 amfriday.abolorunke
Subscriber
Hi @dcoll I made changes according to your recommendations. Now i am getting the error below. Please could you tell me what could be the cause of the issue
# linking to ../../src/density_udf.c in lnamd64/3ddp_host
# linking to ../../src/makefile in lnamd64/3ddp_host
# building library in lnamd64/3ddp_host
make[1]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# Generating udf_names.c because of makefile density_udf.c
make[2]: Entering directory `/cluster/home/xx/3dsoln/libudf/lnamd64/3ddp_host'
make libudf.so "CFLAGS=-D_lnamd64 -D_GNU_SOURCE -fpic -shared -std=c99 -Wall -O -DPTR_RESTRICT= " "LDFLAGS=-shared -lm"
make[3]: Entering directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[3]: *** No rule to make target `compiled-functions', needed by `udf_names.o'.
make[3]: *** No rule to make target `write-case-data', needed by `udf_names.o'.
make[3]: *** No rule to make target `dual-time-iterate', needed by `udf_names.o'.
make[3]: *** No rule to make target `time-step', needed by `udf_names.o'.
make[3]: *** No rule to make target `0.01', needed by `udf_names.o'.
make[3]: *** No rule to make target `10', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.cas', needed by `udf_names.o'.
make[3]: *** No rule to make target `3dsolnv1.dat', needed by `udf_names.o'.
make[3]: *** No rule to make target `60000', needed by `udf_names.o'.
make[3]: *** No rule to make target `exit', needed by `udf_names.o'.
make[3]: *** No rule to make target `libudf', needed by `udf_names.o'.
make[3]: *** No rule to make target `load', needed by `udf_names.o'.
make[3]: *** No rule to make target `rc', needed by `udf_names.o'.
make[3]: Target `libudf.so' not remade because of errors.
make[3]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[2]: *** [lnamd64] Error 2
make[2]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/cluster/home/users/3dsoln/libudf/lnamd64/3ddp_host'
# linking to ../../src/density_udf.c in lnamd64/3ddp_node
# linking to ../../src/makefile in lnamd64/3ddp_node
Regards Friday
February 16, 2022 at 11:46 amfriday.abolorunke
Subscriber
I am so sorry. It seems that I spammed the platform. I was having network issues while trying to submit my response. I did not realize that they went through.
I woke up only to find out I can't deleted them. So sorry for that.
March 23, 2022 at 8:50 amprebenjs
Subscriberdid you find any solution to this ?
March 23, 2022 at 11:14 amfriday.abolorunke
Subscriber
No, I did not. But I figured it had nothing to do with my journal file. I sent my file to someone else and they were able to compile it with no issues on their HPC machine.
So, the issue was with my school's HPC. The configuration for ANSYS was not properly setup and they are yet to fix it.
Viewing 10 reply threads- You must be logged in to reply to this topic.
Ansys Innovation SpaceEarth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Ansys Blog
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
Trending discussions- unable to open files in ansys
- How to move duplicated ansys project position in workbench GUI
- Download MATLAB toolbox AnsysAAS
- An unknown error with memory occurred during solution.
- Desginpoints in Ansys 18.2 workbench got stuck at the stage of updating model in static structural
- Error: Unable to open some designs in this project – Corrupted project files
- Ansys solving system coupling problems on a remote cluster does not provide constant results.
- ANSYS Multi field 2-way FSI data coupling issue
- Material constant Damping calculation
- Different initial temperature conditions for two different object in transient-thermal
Top Contributors-
2656
-
2120
-
1347
-
1118
-
461
Top Rated Tags© 2023 Copyright ANSYS, Inc. All rights reserved.
Ansys does not support the usage of unauthorized Ansys software. Please visit www.ansys.com to obtain an official distribution.
-