Closed MarAlder closed 1 year ago
I don't know if this serves any use case, but I was wondering: Would it make sense to have the duct elements on the same level as the ductAssemblys and have the ductAssemblys reference duct elements by uid? That way you could re-use a duct element in more than one duct assembly...
@CLiersch @rmaierl @AntonReiswich @sdeinert I just wanted to tag you guys here.
The proposal of @joergbrech sounds as a good idea to me. Imagine two engines sharing a <duct> element. Then, a <ductAssembly> can be made a continuous line of <duct> elements from intake to outlet for one engine, without specifying the double-used <duct> twice.
The proposal of @joergbrech sounds as a good idea to me. Imagine two engines sharing a
element. Then, a can be made a continuous line of elements from intake to outlet for one engine, without specifying the double-used twice.
We changed the definition in #774 accordingly and used this as a basis for our implementation in TiGL.
Implemented
I would like to announce that the TiGL development is currently fokusing on ducts (see https://github.com/DLR-SC/tigl/issues/881), i.e. fuselage-like bodies which are substracted from the aircraft fuselage and wings:
The work is currently based on the following XSD extension (see
duct
branch):Everyone is invited to contribute to this effort with comments, ideas or identification of possible problems, either here or at https://github.com/DLR-SC/tigl/issues/881.