TUD tool Q3D tool specific input

[imcovangent]

This issue is about adding a node for tool specific input to run a Q3D analysis. Q3D (which stands for Quasi-3D) is an aerodynamic analysis tool of the TU Delft. The CPACS wrapping of Q3D is nearly finished. In order to run a Q3D analysis fully from CPACS (using an Optimus or RCE workflow) the following tool specific input needs to be defined in cpacs/toolspecific/q3D as elements:

1. typeOfRun = string => 'flightLoadCase' / 'aeroPerformanceMap'
2. wingUID = string => uID of the wing to be analyzed
3. flightLoadCaseUID = array of strings => the uIDs of the flightLoadCases to be analysed. Is this a possible element type? The array of strings might become very large.
4. n_afp = integer value => number of airfoil points to be used in the analysis.
5. n_wing = integer value => number of equidistant airfoil sections along the span for Q3D analysis.
6. VLM / nchord = integer value => number of vortices along chord in vortex lattice method.
7. VLM / nspan = integer value => number of vortices along span in vortex lattice method.

Other issues / questions:

• If Optimus and RCE workflows are being provided to run Q3D analyses on specific CPACS files, how should the name of the CPACS file be indicated? Is there a 'best practice' for this?
• In the aeroDataSetForLoads element one should specify the flightShapePoint and jigShapePoint when a strip result is added to a wing segment. How are these two points defined?
• I'd like to discuss reference and normalization of some of the coefficients.

The development of Q3D with CPACS is part of the AGILE project. I will discuss the above questions/issues at the AGILE WP2 - CPACS telco.

[DLR-LY]

Hi Imco, As I mentioned in an email it is not neccessary to define your toolspecifics in the CPACS schema. If you still want it to be added to the schema just post the structure and we will add it to the next release. Otherwise I'll close this issue.

Since we discussed the question in one of the telco I won't answer them here again.

[imcovangent]

Hi,

Indeed. I created this issue since I wasn't aware of that. So no need to add it to the next release. You can close the issue.

Imco