Status file and Images not generated on a Linux Server about fluidx3d

[fabiodinatale]

Thanks @ProjectPhysX for your feedback.
The complete path where the images should be generated is: /home/iit.local/fdinatale/02.FluidX3D/FluidX3D/export/test_name/png, where test_name is a string composed by the date and time of the test itself.

Anyhow, I tried to give as input in both write_status and lbm.write_frame function the name of the files to be generated and now both the status file and the pictures are generated in /home/iit.local/fdinatale/02.FluidX3D/FluidX3D.

[fabiodinatale]

I think we can close this issue.

Thanks for your help @ProjectPhysX!

[ProjectPhysX]

Hi @fabiodinatale,

I can't reproduce this issue, neither on my Windows 10 system nor on my Linux system. I see the files forces.dat, torques.dat, the .png images, and the status files correctly generated on both systems.

I suspect this to be an issue with an old g++ compiler version, which might not correctly support <filesystem>. In this case, if the filesystem folder tree in which you want to write the files into is not present before writing files, C++ will not write the files at all. Which g++ --version do you have installed? Try updating, to at least g++-9.

Kind regards,
Moritz

[fabiodinatale]

Hi @ProjectPhysX, first of all, thanks for the tests you performed and for your reply.

Running the command g++ --version on the server, this is the result I get:

fdinatale@iitbmp014srv001:~$ g++ --version
g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

i.e. the system has the version 11.4.0 of g++.

I also tried to run the code in a conda environment and in this case the compiler is the following one:

(fluidx3d) fdinatale@iitbmp014srv001:~$ g++ --version
g++ (conda-forge gcc 12.3.0-5) 12.3.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

so it is even newer.

Actually, I discovered that pictures and status file are created but in my root directory. You can see them as they are the ones named 02.png and 02.txt respectively:

(fluidx3d) fdinatale@**********srv001:~$ ls -la
total 280
drwxr-xr-x 14 fdinatale domain users   4096 May  3 09:20 .
drwxr-xr-x 19 root      root           4096 Nov 29 09:46 ..
drwxr-xr-x  3 fdinatale domain users     22 Apr 10 12:58 02.FluidX3D
-rw-r--r--  1 fdinatale domain users 192494 Apr 29 15:27 02.png
-rw-r--r--  1 fdinatale domain users    337 Apr 29 15:26 02.txt
-rw-------  1 fdinatale domain users  25585 May  3 08:58 .bash_history
-rw-r--r--  1 fdinatale domain users    220 Oct 17  2023 .bash_logout
-rw-r--r--  1 fdinatale domain users   4667 Apr 10 12:42 .bashrc
drwx------  3 fdinatale domain users     59 Apr 10 12:46 .cache
drwxr-xr-x  2 fdinatale domain users     30 Apr 10 12:47 .conda
-rw-r--r--  1 fdinatale domain users     52 Apr 10 12:43 .condarc
drwx------  4 fdinatale domain users     70 Apr 19 15:29 .config
-rw-r--r--  1 fdinatale domain users   7571 Apr 19 17:21 .cxlayout.ini
drwxr-xr-x  3 fdinatale domain users     27 Oct 20  2023 .local
drwxr-xr-x 19 fdinatale domain users   4096 Apr 10 12:52 miniforge3
drwx------  3 fdinatale domain users     26 Oct 20  2023 .nv
-rw-r--r--  1 fdinatale domain users    807 Jan  8 14:35 .profile
drwx------  2 fdinatale domain users     60 Oct 20  2023 .ssh
-rw-------  1 fdinatale domain users    244 May  3 09:20 .Xauthority

I don't know if this information can help.

Thanks!

[ProjectPhysX]

The compiler is fine. Can you share your entire file path into which the images should be written, and is there any special characters in there? FluidX3D is doing some string manipulation on the file path, maybe this fails in your case.