Hello,
Could you provide an example of using new Launder-Sharma k-epsilon model in version CS 6.0? It would be great if you can provide wind tunnel with rough wall.
Best regards,
Konstantin
Search found 30 matches
- Thu Apr 04, 2019 3:55 pm
- Forum: code_saturne usage
- Topic: Wind tunnel by Launder-Sharma k-epsilon
- Replies: 4
- Views: 14251
- Fri Mar 08, 2019 3:29 pm
- Forum: code_saturne usage
- Topic: Exceeded memory limit
- Replies: 6
- Views: 4771
Re: Exceeded memory limit
Yvan, thank you for your help! You are right that was a problem of ATHOS. I were running these case on EOLE and it works really well.
Thanks again.
Bon weekend,
Konstantin
Thanks again.
Bon weekend,
Konstantin
- Fri Mar 01, 2019 7:10 pm
- Forum: code_saturne usage
- Topic: Exceeded memory limit
- Replies: 6
- Views: 4771
Re: Exceeded memory limit
Hello, Yvan, thank you for spending time for my case. I have checked this case with a smaller number of processors as you recomend. And anyway I have this error. If there is no memory leaks in there, I have only one guess that this case does not converge at some moment. Thank you again and bon weeke...
- Wed Feb 20, 2019 11:39 am
- Forum: code_saturne usage
- Topic: Rough wall and k-omega SST model
- Replies: 0
- Views: 37451
Rough wall and k-omega SST model
Hello!
Is that possible to simulate properly a flow over a very rough wall by k-omega SST model? I was trying a different tests and it does not gives me a proper velocity profile.
Best regards, Konstantin
Is that possible to simulate properly a flow over a very rough wall by k-omega SST model? I was trying a different tests and it does not gives me a proper velocity profile.
Best regards, Konstantin
- Wed Feb 06, 2019 8:16 pm
- Forum: code_saturne usage
- Topic: Exceeded memory limit
- Replies: 6
- Views: 4771
Re: Exceeded memory limit
Thank you for your reply, Yvan. I was trying the same test but with k-epsilon model and results gives me the same error "exceeded memory limit". So looks like problem not in the turbulence model. I attached zip archive with my setup files I was running on claster ATHOS usng 3 nodes. Best r...
- Tue Feb 05, 2019 11:14 am
- Forum: code_saturne usage
- Topic: Exceeded memory limit
- Replies: 6
- Views: 4771
Exceeded memory limit
Hello! I was running CS v5.3 and v5.2 with RSM LRR turbulence model, to calculate turbulent flow around cylinder. But this calculations are stopping after ~145000 timestep with error: slurmstepd-atcn451: error: Job 17541583 exceeded memory limit (61472984 > 61440000), being killed slurmstepd-atcn451...
- Thu Dec 13, 2018 5:36 pm
- Forum: code_saturne usage
- Topic: cs_user_postprocess.c for Rij model
- Replies: 2
- Views: 2485
Re: cs_user_postprocess.c for Rij model
Yes! You are right. Thanks for help Yvan!
Best regards,
Konstantin
Best regards,
Konstantin
- Wed Dec 12, 2018 5:29 pm
- Forum: code_saturne usage
- Topic: Import velocity profile
- Replies: 17
- Views: 44161
Re: Import velocity profile
Hello. I have a similar task. I was reading from GUI-defined csv-profile with velocity and turbulence statistics and use as boundary conditions. I was using C-version of files. You can find it here https://github.com/kikuznetsov/Code_Saturne-SRC . The source code is adapted for k-epsilon and Rij-eps...
- Wed Dec 12, 2018 4:43 pm
- Forum: code_saturne usage
- Topic: cs_user_postprocess.c for Rij model
- Replies: 2
- Views: 2485
cs_user_postprocess.c for Rij model
Hello ! I have a problem with saving profiles using cs_user_postprocess.c in case Rij-SSG turbulence model (for k-epsilon works well). For the moment I am using this approach to create a set of points in the profile: cs_probe_set_t *pset = cs_probe_set_create_from_segment("Prof1", // name ...
- Mon Oct 15, 2018 11:14 am
- Forum: code_saturne usage
- Topic: Regular malloc/free in CS
- Replies: 2
- Views: 2609
Re: Regular malloc/free in CS
Thanks a lot for your reply, Yvan.
At the end valgrind and your advice help me to find the memory leaks in my code.
Best regards,
Konstantin
At the end valgrind and your advice help me to find the memory leaks in my code.
Best regards,
Konstantin