turbomachinery in CS_3.2

Questions and remarks about code_saturne usage
Forum rules
Please read the forum usage recommendations before posting.
Brian Angel

Re: turbomachinery in CS_3.2

Post by Brian Angel »

Hello,

Can you please upload the following files so that I can download and take a look at them:

- xml file
- volume mesh file
- any user routines that you are using

Can you also upload some images of the geometry as well as the pump operating conditions (rotational speed, mass flow rate,...).

Best regards,

Brian Angel.
Rinat

Re: turbomachinery in CS_3.2

Post by Rinat »

Hello Spread file format IGS.Rotor and stator. velocity at the inlet to the rotor of 20 m/s output pressure 1 atmosphere. working body water.3000 rpm.If you please do a simple calculation example
Attachments
3D rotor.7z
(15.06 KiB) Downloaded 423 times
Rinat

Re: turbomachinery in CS_3.2

Post by Rinat »

also I put the med files
and hdf executed in Salome 7.3.
The grid is created
The geometry is broken into groups. entrance to a rotor rotor escaping, entrance to a casing and casing escaping. and also rotor and casing stacks.
Attachments
Stator hdf+med.7z
(1.17 MiB) Downloaded 383 times
Rinat

Re: turbomachinery in CS_3.2

Post by Rinat »

the hdf and med files of a rotor have large volume. I can personally report by e-mail.
Yvan Fournier
Posts: 4208
Joined: Mon Feb 20, 2012 3:25 pm

Re: turbomachinery in CS_3.2

Post by Yvan Fournier »

Hello,

If you use "dump study" in SALOME to export a Python script, you can simply post that script, which will be small. It's an auto-generated script, so a bit ugly and not very maintainable, but it will only be a few Kbytes, instead of Mbytes. It is not guaranteed to work, as SALOME sometimes has minor bugs with this, but it may be worth trying first.

I won't have time to check this before a few days, but other on this forum are welcome to do so (especially others who are also using the rotor-stator joining).

Did you look at the recent posts and threads on this forum from other users working with Rotor/Stator aspects ? As the documentation is still quite limited, reading those questions and answers may help you avoid pitfalls and save you quite of bit of time (and there are only a few threads, so it's quite a short read).

Best regards,

Yvan
Rinat

Re: turbomachinery in CS_3.2

Post by Rinat »

Good afternoon.
Yes I read others the message on it to the form, but didn't find the solution of the problem. How to set rotor rotation in GUI. and in documentation there isn't enough information on the job of a step of integration for each specific objective, and also to solver settings in relation to different tasks. On it it would be healthy if the masters of CODESaturne considered as an example simple as an example.
Yvan Fournier
Posts: 4208
Joined: Mon Feb 20, 2012 3:25 pm

Re: turbomachinery in CS_3.2

Post by Yvan Fournier »

Hello,

Here are a few points :
How to set rotor rotation in GUI.
The turbomachinery functionality is not yet available throught the GUI. You need to copy SRC/REFERENCE/cs_turbomachinery.c to SRC/ in a given case's setup, and adapt it. The comments you'll fid on the fourm refer mainly to this.
and in documentation there isn't enough information on the job of a step of integration for each specific objective
The reference documentation won't help you here, but tutorials should. Unfortunately, a turbomachinery tutorial is not yet ready, but planned...
and also to solver settings in relation to different tasks.
Ideally, you should not have to modify solver settings. Just following the best practice guidelines on this web site (http://code-saturne.org/cms/documentation/BPG) should be enough.
On it it would be healthy if the masters of CODESaturne considered as an example simple as an example.
Here again, a tutorial will help.

Remember that Code_Saturne version 3.2 (and upcoming version 3.3) is an intermediate "feature" version, and not a "long term support", "major" version, so the documentation; especially the tutorials, might be less up to date. Next major version will be 4.0, in Q1 2015.

Regards,

Yvan Fournier
Post Reply