MarAlder

Usage of symmetry attributes

1

Hi, I'm working up some examples to enrich the [CPACS docs](https://www.cpacs.de/documentation/CPACS_development/html/89b6a288-0944-bd56-a1ef-8d3c8e48ad95.htm) (https://github.com/DLR-SL/CPACS/issues/733, https://github.com/DLR-SL/CPACS/issues/735) with some more detailed descriptions on the current symmetry concepts. In this context, I just want to...

Currently the computation of the wing aspect ratio returns `inf` for the `simpletest.cpacs.xml` case because [`GetReferenceArea`](https://github.com/DLR-SC/tigl/blob/76e1f1442a045e1b8b7954119ca6f9c883ea41e2/src/wing/CCPACSWing.cpp#L565) gets `TIGL_X_Z_PLANE` (symmetry axis) as input and consequently returns 0. - [example.zip](https://github.com/DLR-SC/tigl/files/3717457/Example.zip) Not sure...

Hi, I'm running in this error when building/serving the exampleSite with [Hugo 0.120.1](https://github.com/gohugoio/hugo/releases/tag/v0.120.1.) on Windows, running the [quick-start example](https://gohugo.io/getting-started/quick-start/). Any idea what goes wrong here? ```cmd >> hugo new site...

Maybe this relates partly to #134: We provide users of our CPACS data model with permanent links to XSD files via GitHub pages. Our domain [www.cpacs.de](www.cpacs.de) redirects to the corresponding...

Extension of configuration.i

1

The `python_internal` bindings are only extended occasionally and are often not complete. We should clean up the `configuration.i` and give Python users access to all generated and custom classes.

Attach xsd files when integrating CPACS tools

3

In [issue #484](https://github.com/DLR-SL/CPACS/issues/484) we plan to exclude the toolspecifics from CPACS. This is realized by the `xsd:any` element with `processContents=strict` attribute, i.e. the XML processor must obtain the schema for...

CPACS 3.5 has a new header node: [see docs](https://dlr-sl.github.io/cpacs-website/documentation/CPACS_3_5_0_Docs/html/a430c658-6111-6868-d855-201b284ca81e.htm) To allow TiGL to open CPACS 3.5 files the `` element is still available in the old location, although optional and...

Python wrapper returns SwigPyObject instead of CPACSWalls

3

I still can't figure out why the walls (CPACSWalls.h) are not being exported correctly with the Python bindings. Does anyone have an idea? Minimal test code: ```Python from tixi3.tixi3wrapper import...

TiGL should support the new CPACS systems definition (see [Burschyk et al.](https://elib.dlr.de/213952/1/aerospace-12-00373-v2.pdf); at least [genericSystems](https://dlr-sl.github.io/cpacs-website/documentation/CPACS_3_5_0_Docs/html/10dd09c4-322c-afab-95ac-4d0b73de8ccc.htm), maybe also evaluation methods for [systemArchitectures](https://dlr-sl.github.io/cpacs-website/documentation/CPACS_3_5_0_Docs/html/9220fe76-0de2-5833-bf0c-d50aed70ef32.htm)) introduced in CPACS v3.5, which are currently being refined...

Any idea where these artefacts come from? E.g., [D250-TFLH2-MHEP-2040.zip](https://github.com/user-attachments/files/21035363/D250-TFLH2-MHEP-2040.zip)   You can see it on some of the exports at the [digital hangar](https://www.digital-hangar.de/).