rotorBladesType More...
#include <CPACSRotorBlades.h>
Public Member Functions | |
virtual TIGL_EXPORT CCPACSWing & | AddRotorBlade () |
TIGL_EXPORT | CPACSRotorBlades (CCPACSRotorcraftModel *parent, CTiglUIDManager *uidMgr) |
virtual TIGL_EXPORT CTiglUIDObject * | GetNextUIDParent () |
virtual TIGL_EXPORT const CTiglUIDObject * | GetNextUIDParent () const |
TIGL_EXPORT CCPACSRotorcraftModel * | GetParent () |
TIGL_EXPORT const CCPACSRotorcraftModel * | GetParent () const |
virtual TIGL_EXPORT const std::vector< std::unique_ptr< CCPACSWing > > & | GetRotorBlades () const |
virtual TIGL_EXPORT std::vector< std::unique_ptr< CCPACSWing > > & | GetRotorBlades () |
TIGL_EXPORT CTiglUIDManager & | GetUIDManager () |
TIGL_EXPORT const CTiglUIDManager & | GetUIDManager () const |
virtual TIGL_EXPORT void | ReadCPACS (const TixiDocumentHandle &tixiHandle, const std::string &xpath) |
virtual TIGL_EXPORT void | RemoveRotorBlade (CCPACSWing &ref) |
virtual TIGL_EXPORT void | WriteCPACS (const TixiDocumentHandle &tixiHandle, const std::string &xpath) const |
virtual TIGL_EXPORT | ~CPACSRotorBlades () |
Protected Attributes | |
CCPACSRotorcraftModel * | m_parent |
std::vector< std::unique_ptr< CCPACSWing > > | m_rotorBlades |
Rotor blade geometries are defined using the same data structure as wings (wingType). But in order to be compatible with the other rotor blade related types (e.g. rotorType, rotorHubType, rotorHubHingeType) there are some additional conventions/requirements regarding the definition and orientation of rotorBlade geometries: see remarks. More... | |
CTiglUIDManager * | m_uidMgr |
Private Member Functions | |
CPACSRotorBlades (const CPACSRotorBlades &)=delete | |
CPACSRotorBlades (CPACSRotorBlades &&)=delete | |
CPACSRotorBlades & | operator= (const CPACSRotorBlades &)=delete |
CPACSRotorBlades & | operator= (CPACSRotorBlades &&)=delete |
rotorBladesType
RotorBlades type, containing all the rotor blade gometry definitions of an rotorcraft model. Rotor blade geometries are defined using the same data structure as wings (wingType). But in order to be compatible with the other rotor blade related types (e.g. rotorType, rotorHubType, rotorHubHingeType) there are some additional conventions/requirements regarding the definition and orientation of rotorBlade geometries: Rotor blades should be positioned relative to the global z-axis the way they will be positioned to the rotor shaft (when blade azimuth=0deg). The global x-axis should be used as radial axis (usually the quarter chord line of the rotor blade coincides to a great extent with the x-axis of the rotor blade coordinate system). All sections should be positioned in the positive x halfspace. Segments should connect sections with ascending x coordinates. Airfoils defined in the rotorAirfoils node should be used instead airfoils from the wingAirfoils node.
TIGL_EXPORT tigl::generated::CPACSRotorBlades::CPACSRotorBlades | ( | CCPACSRotorcraftModel * | parent, |
CTiglUIDManager * | uidMgr | ||
) |
|
virtual |
|
privatedelete |
|
privatedelete |
|
virtual |
|
virtual |
|
virtual |
TIGL_EXPORT CCPACSRotorcraftModel* tigl::generated::CPACSRotorBlades::GetParent | ( | ) |
TIGL_EXPORT const CCPACSRotorcraftModel* tigl::generated::CPACSRotorBlades::GetParent | ( | ) | const |
|
virtual |
|
virtual |
TIGL_EXPORT CTiglUIDManager& tigl::generated::CPACSRotorBlades::GetUIDManager | ( | ) |
TIGL_EXPORT const CTiglUIDManager& tigl::generated::CPACSRotorBlades::GetUIDManager | ( | ) | const |
|
privatedelete |
|
privatedelete |
|
virtual |
|
virtual |
|
virtual |
|
protected |
|
protected |
Rotor blade geometries are defined using the same data structure as wings (wingType). But in order to be compatible with the other rotor blade related types (e.g. rotorType, rotorHubType, rotorHubHingeType) there are some additional conventions/requirements regarding the definition and orientation of rotorBlade geometries: see remarks.
|
protected |