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 On Wednesday, June 21, 2023 at 9:05:00 AM UTC-5 [email protected] wrote: > Hello Luning, > > I have attached the results for your reference. Please let me know if > anything else is needed. > > Thank you, > Mohammad > > On Tuesday, June 20, 2023 at 11:04:45 AM UTC-7 [email protected] wrote: > >> 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 >> >> On Tuesday, June 20, 2023 at 1:10:19 AM UTC-5 [email protected] wrote: >> >>> 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, >>> >>> On Monday, June 19, 2023 at 9:20:58 AM UTC-7 [email protected] wrote: >>> >>>> 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 >>>> On Sunday, June 18, 2023 at 8:18:27 PM UTC-5 [email protected] wrote: >>>> >>>>> 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. >>>>> >>>>> [image: Screenshot 2023-06-18 181321.png] >>>>> >>>>> Thank you, >>>>> Mohammad >>>>> On Sunday, June 18, 2023 at 4:58:40 PM UTC-7 [email protected] wrote: >>>>> >>>>>> 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 >>>>>> >>>>>> On Sunday, June 18, 2023 at 2:47:43 PM UTC-5 [email protected] >>>>>> wrote: >>>>>> >>>>>>> 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. >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/e1a505f3-02c4-424b-9904-86aa2b72bda6n%40googlegroups.com.
