EDEM-Fluent coupling without GUI on Linux

Megan_21536

Hi,

I was trying to compile the EDEM-Fluent coupler using version 2.3.1 downloaded from here: Script & Model Library - Altair EDEM CFD Coupling for Ansys Fluent But ran into some errors with loading libpython3.10.so.1.0 (error while loading shared libraries: libpython3.10.so.1.0: cannot open shared object file: No such file or directory) despite checking that the path is correct and included in the PYTHONPATH and LD_LIBRARY_PATH when using the GUI to compile the coupler. May I find out what are the steps for coupling it without the GUI? 

Thanks!

Megan

 

RWood

Megan_21536 said:

Noted. Looking forward to your response soon.

Hi,

I've added a headless build to this post:

https://community.altair.com/community?id=kb_article&sysparm_article=KB0117663

I've managed to get that building fine. I haven't had chance to test it in a simulation, but I'm reasonably confident it'll load ok as I can't see any issues with the compilation.

As  I mention in the post, the README.Linux files in the subfolders explain the steps, but the only thing that's not explicit is setting the python path environment variable. Assuming you're on a RedHat / CentOS - based OS:

export PYTHONPATH=$(pwd) 

from within the /tools/  subfolder should work. If you don't have permissions to do this, just copy the fluent_utils.py file into the /lib_edem_coupling/ folder before running the second scons command.

Richard

RWood

Hi,

I've just uploaded an updated version of the EDEM-Fluent coupling but this still has the GUI with it. I did test this on a Linux machine without a GUI earlier this week but I don't have access to that machine currently and I couldn't tell you the exact steps without going through them again. 

For a tiny bit of background the coupling is maintained by myself and a developer at Ansys. I maintain the GUI as the majority of people can use that and it's much easier to work with, but the Ansys developer works in Linux without using a GUI. I've attached a version of the coupling exactly as I received it from Ansys last week. There are several README.Linux files in there that cover how to use it. I know I've used it like this in the past but I also can't test this right now as I don't have access to my Linux machine and won't do until the week after next. 

I'd suggest using the attached files and if you're still not managing to get anywhere I'll take another look in a couple of weeks when I can access the right machine.

Richard

Edit: I've had to remove the attachment, for reasons I won't go into. I'll get back to you

Megan_21536

Noted. Looking forward to your response soon.

RWood

Megan_21536 said:

Noted. Looking forward to your response soon.

Hi,

I've added a headless build to this post:

https://community.altair.com/community?id=kb_article&sysparm_article=KB0117663

I've managed to get that building fine. I haven't had chance to test it in a simulation, but I'm reasonably confident it'll load ok as I can't see any issues with the compilation.

As  I mention in the post, the README.Linux files in the subfolders explain the steps, but the only thing that's not explicit is setting the python path environment variable. Assuming you're on a RedHat / CentOS - based OS:

export PYTHONPATH=$(pwd) 

from within the /tools/  subfolder should work. If you don't have permissions to do this, just copy the fluent_utils.py file into the /lib_edem_coupling/ folder before running the second scons command.

Richard

Megan_21536

Richard Wood_20774 said:

Hi,

I've added a headless build to this post:

https://community.altair.com/community?id=kb_article&sysparm_article=KB0117663

I've managed to get that building fine. I haven't had chance to test it in a simulation, but I'm reasonably confident it'll load ok as I can't see any issues with the compilation.

As  I mention in the post, the README.Linux files in the subfolders explain the steps, but the only thing that's not explicit is setting the python path environment variable. Assuming you're on a RedHat / CentOS - based OS:

export PYTHONPATH=$(pwd) 

from within the /tools/  subfolder should work. If you don't have permissions to do this, just copy the fluent_utils.py file into the /lib_edem_coupling/ folder before running the second scons command.

Richard

Hi Richard,

I managed to run the second scon in /lib_edem_coupling/ folder but only managed to obtain 4 folders with 4 libudf.so files within the /lnamd64/ subfolder, rather than the 6 referenced in the documentation. Is this an error? I was unable to find any errors in the log other than a few warnings.

Thanks!

Megan

RWood

Megan_21536 said:

Hi Richard,

I managed to run the second scon in /lib_edem_coupling/ folder but only managed to obtain 4 folders with 4 libudf.so files within the /lnamd64/ subfolder, rather than the 6 referenced in the documentation. Is this an error? I was unable to find any errors in the log other than a few warnings.

Thanks!

Megan

Hi Megan,

No, there should be 4 nowadays so you're all good. If it mentions 6 then it's just old documentation that hasn't been updated. Parallelisation changed in Fluent a few releases back and the knock on effect was one of the folder types was no longer needed. You used to have folders for [3d, 3d_host, 3d_node] and the same for 3ddp (double precision). The 3d and 3ddp folders are no longer used due to these changes in how the parallel processing works, which is why we're now down to 4 folders. All being well that should work with and without double precision, for any of the coupling requirements (i.e. with/without species or combustion, if required).

To be honest the documentation is pretty dated now and does need updating. Really the whole compilation procedure does, but that's...one day.

Cheers,

Richard

Megan_21536

Richard Wood_20774 said:

Hi Megan,

No, there should be 4 nowadays so you're all good. If it mentions 6 then it's just old documentation that hasn't been updated. Parallelisation changed in Fluent a few releases back and the knock on effect was one of the folder types was no longer needed. You used to have folders for [3d, 3d_host, 3d_node] and the same for 3ddp (double precision). The 3d and 3ddp folders are no longer used due to these changes in how the parallel processing works, which is why we're now down to 4 folders. All being well that should work with and without double precision, for any of the coupling requirements (i.e. with/without species or combustion, if required).

To be honest the documentation is pretty dated now and does need updating. Really the whole compilation procedure does, but that's...one day.

Cheers,

Richard

Thanks, Richard, for your clarification. Have a great festive season ahead!

 

Enawgaw Assaye

Can I utilize EDEM ANSYS Fluent for friction stir welding? Is it possible? Please help me.

Rajani Kant Baro

Can you share the download links? I am not able to access the links.

RWood

Rajani Kant Baro said:

Can you share the download links? I am not able to access the links.

The EDEM-Fluent coupling is gated behind a customer login and is not publicly available. To gain access to the coupling you should create a customer account or ask whoever provides your Altair license to create one for you so you can access the customer Knowledge Base and access the link above.