FSI DEMO

146 views
Skip to first unread message

Mohammad Wasfi

unread,
Jun 18, 2023, 3:47:43 PM6/18/23
to ProjectChrono
Hi, 

I am trying to run one of the FSI demos (Single wheel test) and I get the following error: (Invalid JSON file!). I have looked through the forum and I have found that someone else have had a similar problem with some other FSI demo and the solution was mentioned to be a bug fix. 

I was wondering if you could take a look at that demo. Please let me know if more information is needed. 

Thank you, 
Mohammad A.

Luning Bakke

unread,
Jun 18, 2023, 7:58:40 PM6/18/23
to ProjectChrono
Hello Mohammad, 

I can run demo_FSI_SingleWheelTest, so I need more info. Which branch are you on? What's your operating system? Likely the the invalid JSON file error is because the program can not find the json file. 

Thank you,
Luning

Mohammad Wasfi

unread,
Jun 18, 2023, 9:18:27 PM6/18/23
to ProjectChrono
Hi Luning, 

Thank you so much for your help. 

I am using a Linux operating system. I have pulled from Release/8.0. When I built the package, I only turned the shown criteria on (Module FSI, Build Demos, and Build Testing). I have also attached my error and output files for your reference. 

Screenshot 2023-06-18 181321.png

Thank you, 
Mohammad
testCRM.e950516
testCRM.o950516

Luning Fang

unread,
Jun 19, 2023, 12:20:58 PM6/19/23
to ProjectChrono
I see. Try run ./demo_FSI_SingleWheelTest inside the bin folder, instead of the build folder. You can add "cd bin/" in your slurm script. 
The data directory is a relative one in the demo, which is "../data/fsi/", that's why you need to be in the bin folder to run the program.  For your own applications in the future, you can set the chrono data directory to an absolute one. 

Thank you,
Luning

Mohammad Wasfi

unread,
Jun 20, 2023, 2:10:19 AM6/20/23
to ProjectChrono
Hi Luning, 

Thank you so much. That worked and the demo had run. However, it still gave me some errors for some reason. Also, the DEMO_OUTPUT folder that is created when the demo is run is empty and I could not find anything in it. I have attached the error and output files for your reference.


Thank you so much for your help, 

testCRM.o952661
testCRM.e952661

Luning Bakke

unread,
Jun 20, 2023, 2:04:45 PM6/20/23
to ProjectChrono
Hello Mohammad,

From your error,

terminate called after throwing an instance of 'thrust::system::detail::bad_alloc'
  what():  std::bad_alloc: cudaErrorStubLibrary: CUDA driver is a stub library

I suspect cuda or cuda driver wasn't set up properly. I need more info. Can you share your CMakeCache.txt file (it's in the build directory), and type "nvidia-smi" in your terminal, and share with me the result? You can also put nvidia-smi in your slurm script.

Thank you,
Luning

Mohammad Wasfi

unread,
Jun 21, 2023, 10:05:00 AM6/21/23
to ProjectChrono
Hello Luning, 

I have attached the results for your reference. Please let me know if anything else is needed. 

Thank you,
Mohammad

testCRM.o954969
CMakeCache.txt
testCRM.e954969

Luning Bakke

unread,
Jun 22, 2023, 2:08:02 PM6/22/23
to ProjectChrono
I saw that your cuda driver can support 12.0, but from your CMakeCache, chrono is compiled using cuda 11.4 library. I suggest you try cuda 12 library when compiling Chrono::FSI. You can change "CUDA_TOOLKIT_ROOT_DIR:PATH=/opt/apps/cuda/11.4" to the path of cuda12, and cmake should pick up all the rest. Make sure to create a new folder when building so it's a clean.

I don't have cuda 11.4 on my cluster, but i can build and run chrono::fsi using 11.3, 11.6 and 12.0

Thank you,
Luning
Reply all
Reply to author
Forward
0 new messages