Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component UID checks and matching #2

Open
aarondettmann opened this issue Oct 7, 2019 · 0 comments
Open

Component UID checks and matching #2

aarondettmann opened this issue Oct 7, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@aarondettmann
Copy link
Member

Loads and deformations are currently matched using case-sensitive UIDs. For instance, if an aeroelastic model of an aircraft has three components, say a "Wing", "VerticalTail" and "HorizonalTail", all three components must exist in the loads fields database and in the deformation field data base.

Potential problem [1]: The structure model may refer to the vertical tail assembly with UID "VerticalTail", but the CFD tool may refer to the same component with UID "vertical_tail". The effect is that loads and deformations cannot be matched properly.

Potential problem [2]: The structure model could contain structural components (e.g. fuselage or engines) for which there are no corresponding load fields. The fuselage or engine deformation fields should be ignored by the CFD tool. (Problem could potentially exist vice versa).

Potential problem [3]: The CFD tool might model a left and a right wing as two separate components, but the structure tool models both wing as one single component*. E.g. the CFD tools has UIDs "main_wing_left" and "main_wing_right" but the structure tool has a single full-span wing with UID "Wing".

Potential solution(s)

(a) [1, 2, 3] The AeroFrame settings file could contain a table to match UIDs from CFD and structure to handle special cases. For instance, to deal with problems described in [1], [2] or [3], the settings file might looks something like this:

    'components': [
        {
            'cfd': ['vertical_tail'],
            'structure' ['VerticalTail'],
        },
        {
            'cfd': ['main_wing_left', 'main_wing_right'],
            'structure' ['Wing'],
        },
        {
            'cfd': [],
            'structure' ['Fuselage', 'Engine1', 'Engine2'],
        }
    ]

To deal with problem 2, some kind merging of load and/or deformation fields must be implemented.

(b) Relax the UID naming system (could cause other problems).

  • (1) Match components case-insensitive.
  • (2) Strip leading/trailing whitespace in UIDs (fairly safe to do).
@aarondettmann aarondettmann added the enhancement New feature or request label Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant