Introduction
Two classical models are available in code_saturne
for rotor/stator interactions modelling in turbomachinery computations: the steady approach which is based on the so-called Frozen Rotor modelling and the transient rotor/stator approach which is based on a sliding mesh technique.
- Warning
- This page describes these functionalities based on a single
code_saturne
computation. An alternative rotor/stator coupling based on the code/code coupling of code_saturne
with itself is still possible (and briefly described in this page) but it is not recommended (will be highly modified soon).
Mesh requirements
Periodicity
The rotational periodicity treatment is possible only in Frozen Rotor. However, the interface plane between rotor and stator must match in the azimutal
direction:
for all z through the rotation axis direction.
Rotor/stator interface
- Transient rotor/stator: in the input mesh(es), the interface between rotor and stator domains has to be composed of boundary faces. Then the inteface boundary faces are joined during the computation and transformed into internal faces, as the preprocessing step can do in usual calculations. The classical way to fulfill this requirement is to provide separate meshes for each rotor or stator domains, but placing both sections in the same mesh is allowed, as long as they are topologically disjoint.
- Frozen Rotor: the interface can be composed of boundary faces (then the inteface boundary faces are joint at the beginning of the computation and turn into internal faces) or internal faces.
Data setting
The data setting is made through the GUI or through the cs_user_turbomachinery.c source file. Through the latter, the type of turbomachinery model can be first set in cs_user_turbomachinery function:
void cs_turbomachinery_set_model(cs_turbomachinery_model_t model)
Define rotor/stator model.
Definition: cs_turbomachinery.cpp:1372
@ CS_TURBOMACHINERY_TRANSIENT
Definition: cs_turbomachinery.h:60
Then, the rotor region and the rotor/stator interface boundaries has to be specified in cs_user_turbomachinery_rotor function. The rotor region is first specified, as follows:
{
double rotation_velocity = 2.;
double rotation_axis[3] = {0., 0., 1.};
double rotation_invariant[3] = {0., 0., 0.};
const char cell_criteria[] = "cylinder[0.0, 0.0, 0.0,"
" 0.0, 0.0, 1.0,"
" 2.0]";
rotation_velocity,
rotation_axis,
rotation_invariant);
}
void cs_turbomachinery_add_rotor(const char *cell_criteria, double rotation_velocity, const double rotation_axis[3], const double rotation_invariant[3])
Define a rotor by its axis and cell selection criteria.
Definition: cs_turbomachinery.cpp:1434
In this example, rotation_velocity refers to the rotation angular velocity of the rotor, in rad/s. The rotation axis can be normalized (it is eventually normalized afterwards by the code). Note that if a rotor is added, the code appends an instance of cs_rotation_t structure in the global list of rotors (see Basic operations section in the following).
Then the rotor/stator interface boundary is specified. This step is mandatory only for the CS_TURBOMACHINERY_TRANSIENT model. For the CS_TURBOMACHINERY_FROZEN model, this step is required only if the interface is made of boundary faces (see Rotor/stator interface subsection above).
{
const char faces_criteria[] = "rotor_interface or stator_interface";
int verbosity = 0;
int visualization = 0;
float fraction = 0.10, plane = 25.;
fraction,
plane,
verbosity,
visualization);
}
int cs_turbomachinery_join_add(const char *sel_criteria, float fraction, float plane, int verbosity, int visualization)
Add a cs_join_t structure to the list of rotor/stator joinings.
Definition: cs_turbomachinery.cpp:1478
The rotation velocity can be modified during the calculation. The following example shows how to set a linearly increasing rotation velocity in cs_user_turbomachinery_set_rotation_velocity function:
{
int rotor_num = 1;
double two_pi = 2. * acos(-1.);
double rotation_velocity = -1470. * two_pi / 60.;
double rotor_vel = rotation_velocity
rotor_vel);
}
static CS_F_HOST_DEVICE cs_real_t cs_math_fmin(cs_real_t x, cs_real_t y)
Compute the min value of two real values.
Definition: cs_math.h:484
const cs_time_step_t * cs_glob_time_step
void cs_turbomachinery_set_rotation_velocity(int rotor_num, double omega)
Set rotation velocity.
Definition: cs_turbomachinery.cpp:1924
double t_cur
Definition: cs_time_step.h:80
User recomandations
Meshing recomandations at interface
As mentioned above, when a rotor/stator inteface boundary exists (in particular for the CS_TURBOMACHINERY_TRANSIENT model), it is then joined by the solver during the computation. It is thus important to be aware that the success of a joining operation is strongly dependant on the quality of the mesh at the interface. More precisely, the refinement must be as similar as possible on both sides of the interface. Moreover, it is reminded that the tolerance parameter of a joining is a fraction of the shortest edge linked with a vertex to join. Consequently, cells where the refinement in the azimutal
direction is much coarser than those in one of the two others can also lead to a joining failure. In particular, the user should be wary of boundary layers.
Alternative rotor/stator coupling
If the meshes on both sides of the interface are very different and can not be modified, the user should turn to a rotor/stator coupling based on the code/code coupling of code_saturne
with itself. This simply requires replacing the definition of a face joining for an interface (using the GUI or a call to cs_turbomachinery_join_add by a call to cs_turbomachinery_coupling_add.
If a coupling is defined and the rotation is not null in at least one of the cases, icorio determines the type of rotor/stator coupling: icorio = 1 for a Frozen Rotor computation and icorio = 0 for a sliding mesh approach.
- Warning
- Contrary to the mesh joining approach, the code/code coupling approach is not fully conservative.
User operations
Basic operations
A specific rotor is identified by an integer value. The "default rotor" is actually the stator that is the fixed part of the domain, with identifier 0. Then the identifiers of the rotors are incremented as the user add rotors (cs_turbomachinery_add_rotor, see above).
Local definitions and initialization
const cs_lnum_t n_b_faces = domain->mesh->n_b_faces;
= (
const cs_real_3_t *)domain->mesh_quantities->cell_cen;
#define restrict
Definition: cs_defs.h:145
double cs_real_t
Floating-point value.
Definition: cs_defs.h:342
cs_real_t cs_real_3_t[3]
vector of 3 floating-point values
Definition: cs_defs.h:359
int cs_lnum_t
local mesh entity id
Definition: cs_defs.h:335
const cs_fluid_properties_t * cs_glob_fluid_properties
Definition: cs_physical_constants.cpp:465
real(c_double), pointer, save ro0
reference density.
Definition: cstphy.f90:153
double ro0
Definition: cs_physical_constants.h:74
Once the rotor identifier is known, access to its parameters as follows:
double omega = ref_rot->
omega;
cs_rotation_t * cs_glob_rotation
Subdomain rotation description.
Definition: cs_rotation.h:46
double axis[3]
Definition: cs_rotation.h:50
double omega
Definition: cs_rotation.h:48
Importantly, the rotor associated to each cell of the domain can be retrieved thanks to a rotor identifier list as follows:
const int *rotor_num = nullptr;
for (
cs_lnum_t cell_id = 0; cell_id < n_cells; cell_id++) {
const int * cs_turbomachinery_get_cell_rotor_num(void)
Return cell rotor number.
Definition: cs_turbomachinery.cpp:1876
Turbomachinery dedicated postprocessing functions
Useful postprocessing functions relative to the machinery characteristics are available: postprocessing of the couple on the rotor walls (cs_post_moment_of_force) and postprocessing of the head generated by the machinery (cs_post_turbomachinery_head). In the latter one, the mesh locations (CS_MESH_LOCATION_CELLS, CS_MESH_LOCATION_BOUNDARY_FACES or CS_MESH_LOCATION_INTERNAL_FACES) associated with the given selection criteria must be specified.
("inlet",
"z > 2.725 and z < 2.775",
#define BFT_FREE(_ptr)
Definition: bft_mem.h:90
#define BFT_MALLOC(_ptr, _ni, _type)
Definition: bft_mem.h:58
@ CS_MESH_LOCATION_CELLS
Definition: cs_mesh_location.h:63
@ CS_MESH_LOCATION_BOUNDARY_FACES
Definition: cs_mesh_location.h:65
cs_real_t cs_post_moment_of_force(cs_lnum_t n_b_faces, const cs_lnum_t b_face_ids[], cs_real_t axis[3])
Compute the magnitude of a moment of force torque) given an axis and the stress on a specific boundar...
Definition: cs_post_util.cpp:512
cs_real_t cs_post_turbomachinery_head(const char *criteria_in, cs_mesh_location_type_t location_in, const char *criteria_out, cs_mesh_location_type_t location_out)
Compute the head of a turbomachinery (total pressure increase)
Definition: cs_post_util.cpp:378
void cs_selector_get_b_face_list(const char *criteria, cs_lnum_t *n_b_faces, cs_lnum_t b_face_list[])
Fill a list of boundary faces verifying a given selection criteria.
Definition: cs_selector.cpp:213
Velocity profiles extraction in cylindrical coordinates
Below is another example showing how to extract velocity profile in cylindrical coordinates.
if (domain->time_step->nt_cur == domain->time_step->nt_max){
cs_field_t *f_mom_wr =
nullptr, *f_mom_wt =
nullptr;
}
FILE *
f1 =
nullptr, *
f2 =
nullptr;
f1 = fopen(
"Wr_mean.dat",
"w");
fprintf(
f1,
"# %17s%17s\n",
"angle",
"Wr");
f2 = fopen(
"Wt_mean.dat",
"w");
fprintf(
f2,
"# %17s%17s\n",
"angle",
"Wt");
}
int rank_id1 = -999;
for (
cs_lnum_t point_id = 0; point_id < npoint; point_id++) {
cs_real_3_t xyz = {radius*cos(xth0 - (
double)point_id/npoint*2.*_PI),
radius*sin(xth0 - (double)point_id/npoint*2.*_PI),
axicoo};
_findpt_r(domain, ref_rot, xyz, &cell_id, &rank_id);
if ((cell_id != cell_id1) || (rank_id != rank_id1)) {
cell_id1 = cell_id;
rank_id1 = rank_id;
xr = xc[0];
double xthet1, xthet2;
xthet1 = acos((cell_cen[cell_id][0] - ref_rot->
invariant[0])/xr);
xthet2 = asin((cell_cen[cell_id][1] - ref_rot->
invariant[1])/xr);
if (xthet2 > 0)
xtheta = xthet1;
else if (xthet1 < _PI/2.)
xtheta = 2.*_PI + xthet2;
else
xtheta = _PI - xthet2;
xvr = xvc[0];
xvt = xvc[1] - omega*xr;
}
else {
xvr = f_mom_wr->
val[cell_id];
xvt = f_mom_wt->val[cell_id];
}
} else {
xtheta = 0.;
xvr = 0.;
xvt = 0.;
}
xtheta = bp[0], xvr = bp[1], xvt = bp[2];
fprintf(
f1,
" %17.9e%17.9e\n", xtheta, xvr);
fprintf(
f2,
" %17.9e%17.9e\n", xtheta, xvt);
}
}
}
}
}
int cs_glob_rank_id
Definition: cs_defs.cpp:174
#define CS_REAL_TYPE
Definition: cs_defs.h:486
@ vel
Definition: cs_field_pointer.h:70
#define CS_F_(e)
Macro used to return a field pointer by its enumerated value.
Definition: cs_field_pointer.h:51
static void cs_parall_bcast(int root_rank, int n, cs_datatype_t datatype, void *val)
Broadcast values of a given datatype to all default communicator processes.
Definition: cs_parall.h:248
void cs_rotation_cyl_v(const cs_rotation_t *r, const cs_real_t coords[3], const cs_real_t v[3], cs_real_t vc[3])
Express a vector in the cyclindrical system associated to a rotation.
Definition: cs_rotation.cpp:376
cs_field_t * cs_time_moment_get_field(int moment_id)
Return pointer to field associated with a given moment.
Definition: cs_time_moment.cpp:1863
cs_turbomachinery_model_t cs_turbomachinery_get_model(void)
Return rotor/stator model.
Definition: cs_turbomachinery.cpp:1393
cs_turbomachinery_model_t
Definition: cs_turbomachinery.h:56
@ CS_TURBOMACHINERY_FROZEN
Definition: cs_turbomachinery.h:59
real(c_double), dimension(:), pointer, save f1
Definition: cpincl.f90:109
real(c_double), dimension(:), pointer, save f2
Definition: cpincl.f90:109
Field descriptor.
Definition: cs_field.h:131
cs_real_t * val
Definition: cs_field.h:152
double invariant[3]
Definition: cs_rotation.h:51
Fortran naming
Useful fortran variables and/or functions specific to turbomachinery computations are contained int the fortran module turbomachinery and rotation.