turbo_moc.deprecated.meshing.rotor_mesh_2d module#
2D blade-to-blade mesh of the sized axial rotor (hub section).
Not exposed on its own in the app: it is the section the swept 3D rotor mesh (turbo_moc.meshing.stator_mesh_3d.mesh_swept_passage) is built from.
Frame. The rotor blade (design_rotor_vortex_blade / rescale_rotor_blade) has x = chordwise (flow toward +x) and y = pitchwise. The app’s 3D rotor is the mirrored blade wrapped with flare “pitch_scale” (theta = -y / r_hub, z = -x), so the mesh is built in X = y, Y = -x: the stator mesh’s frame (X pitchwise, Y axial, flow toward -Y). section_coordinates then maps it onto exactly the exported rotor solid, and the 3D sweep is shared with the stator.
Passage. Periodic boundaries run along the middle of the channels on either side of the blade, (suction side of this blade + pressure side of the next) / 2, continued straight at the inlet/outlet relative flow angles, so the blade sits in the middle of a smooth periodic channel. Only the CAD differs from the stator: sizing, inflation, recombination, fold repair and checks are stator_mesh_2d’s (_generate_passage_mesh).
- turbo_moc.deprecated.meshing.rotor_mesh_2d.blade_sides(contour)[source]#
The two open sides between the leading edge (max Y) and trailing edge (min Y), each ordered LE -> TE, as (left, right) by mean X.
- turbo_moc.deprecated.meshing.rotor_mesh_2d.mesh_sized_rotor(scaled_blade, sizes, passage=None)[source]#
Unstructured (quad-dominant, inflation-layered) hub mesh of the sized rotor, in the same JSON-friendly layout as stator_mesh_2d.mesh_sized_stator (so it sweeps with stator_mesh_3d.mesh_swept_passage). sizes: blade_size, domain_size, first_height [mm], num_layers, growth_ratio, transition_ratio.