ebouhoubeiny cpacs issues

ebouhoubeiny / cpacs

Automatically exported from code.google.com/p/cpacs

0 stars 5 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Maybe create a figure indicating cutout methods as applied by the standard method (i.e. full cutout from upper to lower skin) instead of showing the cutOutProfile picture and add a figure for leading edge device cutouts?

#274 GoogleCodeExporter closed 8 years ago
1
How to define slots at the sides of the controlSurfaces for material clearance purposes (required for controlSurface deflection)? Eta refers to control surface span here.

#273 GoogleCodeExporter closed 8 years ago
0
trailingEdge cutouts

#272 GoogleCodeExporter closed 8 years ago
0
The entry 'leadingEdgeDeviceCut' is present at both upper and lower skin cutOut definitions, although it should only be defined a single time for consistency

#271 GoogleCodeExporter closed 8 years ago
0
What happens if wing geometrical parameters change (e.g. relChord of cutOut or thickness), how does this influence the validity of cutOutProfiles? Does it scale along?

#270 GoogleCodeExporter closed 8 years ago
0
Where to define the cutOutProfiles? No possibility currently exists in general profiles definition (CPACS/profiles). How to define the cutOutProfiles (i.e. equivalent to TE->LE->TE ruling for airfoils)?

#269 GoogleCodeExporter closed 8 years ago
0
Why not define obligatory innerBorderCutOutProfile and outerBorderCutOutProfile here, exactly as is the case for controlSurface geometric definitions? This seems like an inconsistent method (the difference between the definition of a control surface and its corresponding cutout)

#268 GoogleCodeExporter closed 8 years ago
0
All wing profiles are defined as closed profiles (i.e. TE->LE->LE order, no gaps). Does this have to be the case for cutOutProfiles at the wing too? How to ensure the definitions are parametrically scalable with wing dimensions?

#267 GoogleCodeExporter closed 8 years ago
2
Maybe add another picture showing the definition of the aft part of a multiple-slotted TE device for extra clarification of the definition method?

#266 GoogleCodeExporter closed 8 years ago
1
Why is eta not definable for wing cutouts at trailing edge devices? Now one is obliged to make the cutout with exactly the same span as the controlSurface has and cannot change the cutout setting at controlSurface intermediate span positions

#265 GoogleCodeExporter closed 8 years ago
2
Around which point is rotZ defined? Is it fixed or is a rotationReference missing? Defaults to 90deg == flight direction, isn't it so that this is not always the case (due to sweep angle of control surface)?

#264 GoogleCodeExporter closed 8 years ago
1
Changes to controlSurfaces

#263 GoogleCodeExporter closed 8 years ago
0
Why are 'hollow', 'leadingEdgeShape' and 'relZLE' not put in a choice list? And what is the reasoning behind the large difference in variable naming?

#262 GoogleCodeExporter closed 8 years ago
0
Will CPACS be published before, or after these kind of lists are finished? Are external users allowed to program list entries themselves or should this be centrally managed (i.e. via inclusion at new releases of CPACS)?

#261 GoogleCodeExporter closed 8 years ago
0
For each track subtype, a picture is required indicating the various included parts like 'car', 'strut1', etc. At this moment this should be interpreted using the track description only and is thereby probably not unambiguously defined

#260 GoogleCodeExporter closed 8 years ago
0
Picture is inconsistent with defined variable names

#259 GoogleCodeExporter closed 8 years ago
1
Do the definitions of tracks need to be extended and actuator definitions need to be added before CPACS release (to ensure standardized methods are used)?

#258 GoogleCodeExporter closed 8 years ago
5
Only materials can be set here, probably still large developments needed. Maybe provide attention to this part, since it can show one of the most extensive and complicated descriptions of airplane parts in CPACS. I.e. showing the 'power' and reusability of the CPACS datadeck

#257 GoogleCodeExporter closed 8 years ago
2
How to set/modify track geometrical dimensions? Where to set the actual position of the incorporated actuator if it is somewhere in the track? For which end is the actuator used, since one preprovides an actual rotation angle to a hinge line to define deflections instead?

#256 GoogleCodeExporter closed 8 years ago
1
How to model tracks for multiple-slotted controlSurface systems?

#255 GoogleCodeExporter closed 8 years ago
0
Extension of track definitions

#254 GoogleCodeExporter closed 8 years ago
1
Variables are named 'parentXsi' and 'parentHeight', although have same function as 'xsi', 'relativeChord', 'relZ', 'relHeight', etc.. Define a single variable name for these kind of positional definitions

#253 GoogleCodeExporter closed 8 years ago
3
relZLE is not explained for spoilers (picture?)

#252 GoogleCodeExporter closed 8 years ago
1
For spoilers, according to the presentation, no translation is allowed during deflection. However, in CPACS this is still programmable. Suggestion: keep it that way to have consistency between LE devices, TE devices and spoilers

#251 GoogleCodeExporter closed 8 years ago
0
Unclear how the skin is to be cut for spoiler definitions, is the complete skin taken out or only the part where spoiler is present?

#250 GoogleCodeExporter closed 8 years ago
0
Spoiler Cutout

#249 GoogleCodeExporter closed 8 years ago
1
relZ (relZLE) definition is suddenly not a definition of a control point, but of an actual height (i.e. spoiler thickness), which is confusing

#248 GoogleCodeExporter closed 8 years ago
1
Description is unclear and contains the false picture of another description

#247 GoogleCodeExporter closed 8 years ago
1
Hingeline for flaps

#246 GoogleCodeExporter closed 8 years ago
1
Is this the only way in which a path can be described (via the hinges)? Should one see each step as a possible device setting (i.e. starting flaps, approach flaps, landing flaps)? Then maybe rename this branch to deflectionSettings instead of step.

#245 GoogleCodeExporter closed 8 years ago
1
The coordinate system defined here is not orthogonal (x from global CS, y in hingeline direction that can be swept, z perpendicular). Suggestion to keep all CS orthogonal.

#244 GoogleCodeExporter closed 8 years ago
1
Why are the hingepoints fixed to the borders of the controlSurface? Why not use the hinge definitions of the (outer) tracks instead or as an option to increase modelling flexibility?

#243 GoogleCodeExporter closed 8 years ago
0
Child of controlSurfacePolars is also called controlSurfacePolars, might this be confusing?

#242 GoogleCodeExporter closed 8 years ago
0
Why is this not part of the aircraft/rotorcraft? The contents seem quite vehicle-specific.

#241 GoogleCodeExporter closed 8 years ago
0
Why is composites not a subpart of materials?

#240 GoogleCodeExporter closed 8 years ago
0
xi (or ksi) instead of xsi?

#239 GoogleCodeExporter closed 8 years ago
0
This branch is not present in sample xml file

#238 GoogleCodeExporter closed 8 years ago
3
No documentation present

#237 GoogleCodeExporter closed 8 years ago
2
What is the use of this branch? Is the definition of aircraft systems aimed at (electricals, hydraulics, etc) or are flightDynamics meant? This is quite unclear at the moment

#236 GoogleCodeExporter closed 8 years ago
0
Not all entry possibilities are present in sample file (in fact only stringers present)

#235 GoogleCodeExporter closed 8 years ago
2
Gouping entries (currently the list is too long)

#234 GoogleCodeExporter closed 8 years ago
0
Remove the distinction between identically defined parts and group these under more general names.

#233 GoogleCodeExporter closed 8 years ago
0
Why are the globalBeamProperties and structuralProfileUID, sheetProperties entries not put in a choice list?

#232 GoogleCodeExporter closed 8 years ago
2
How to (parametrically) define the geometry of a single seat?

#231 GoogleCodeExporter closed 8 years ago
1
Why is there a ribsDefinitions entry in structuralElements part, but no sparDefinitions entry?

#230 GoogleCodeExporter closed 8 years ago
3
The ribsDefinitions branch exists twice in the CPACS datadeck and has separate functions. Suggestion: rename ribsDefinitions to ribElement at structuralElements branch.

#229 GoogleCodeExporter closed 8 years ago
2
structuralElements Question

#228 GoogleCodeExporter closed 8 years ago
3
No documentation present

#227 GoogleCodeExporter closed 8 years ago
2
Is there a rule on how to define airfoil datafiles (e.g. TE->LE->TE, upper to lower skin)?

#226 GoogleCodeExporter closed 8 years ago
1
Will it be possible to add other types of airfoil definitions instead of point clouds (e.g. CST definitions)?

#225 GoogleCodeExporter closed 8 years ago
6

Previous Next