code_saturne User's Forum

Not sure if it's relevant, but depending on the application, the ALE module could be used for a lot of similar applications to a shallow water equation solver. This works both with the CDO and legacy solvers. Having already validated this for some cases a few years back : https://doi.org/10.1016/j.c...

Seems to work, thanks!

Ok, thanks! I'll see how it goes. I can reproduce this error in Ubuntu 22.04, CS-7.3 alpha from github (7.2.0 does NOT have this problem). If you don't mind to have mpi support here is a possible workaround: (As I read from the start, I tried the first workaround proposed just to see, and this seeme...

Thanks for the continued suggestions. This is a new laptop that started with Ubuntu 20, upgraded to Ubuntu 22, then tried to install code_saturne. Can describe in more detail if useful. I attach the config.log file for now, I'll try the flag suggestion and redo from the beginning later this weekend.

If I understand correctly, I have not arrived at the point of having cs_solver, that is the next (and last?) step if everything would link, so I'm not sure how to reply. But if it's useful, I can see (I'm building in ~/CS/, source in ~/code_saturne/): ~/CS$ nm -D /usr/lib/x86_64-linux-gnu/libz.so | ...

Thanks for the feedback. Though I am a bit confused ; I tried both the LDFLAGS and the LD_LIBRARY_PATH addition already, and it changes nothing. And this is not from v7, but from the current master branch off github.

P.S. Now that there is a PyQt6, is there a plan for when this will be adapted into CS?

Although I've installed numerous versions of code_saturne on numerous computers, when doing a new setup, I've been stumped... after running the makefile, the relevant bit of error message is: Linking executable: cs_solver g++ -o cs_solver -lcs_solver -L/home/jcharris/CS/src/lagr -L/home/jcharris/CS/...

Okay, thanks for the info.

Same question... seeing how we're already in September, any news on when the 2022 User Meeting will/has/won't happen ?

Having been there for the 2016 / 2017 / 2018 / 2019 events, I would be very interested in attending again this very useful event.