From [email protected] on April 29, 2011 09:51:23

New function: get eta, xsi for a given point (x,y,z)

Original issue: http://code.google.com/p/tigl/issues/detail?id=25

From [email protected] on September 14, 2011 09:50:41

What steps will reproduce the problem? 1.a demo is attached to this issue #2. 3. What is the expected output?
expected is always the same value for the same fuselagegeometrie

What do you see instead?
after reinitialising tigl-library the function delivers a different hashcode What version of the product are you using? On what operating system? tigl v1.0
tixi v1.0
windows 7 Please provide any additional information below.

Attachment: 2011-09-14_tigl_error_componentGetHashCode.zip

Original issue: http://code.google.com/p/tigl/issues/detail?id=46

From [email protected] on August 09, 2011 18:04:17

Update the geometry when changing the wire algorithm

Original issue: http://code.google.com/p/tigl/issues/detail?id=31

From [email protected] on April 07, 2011 07:20:38

Migrate TIGL project files of visual studio to 2008. QT > 4.7 needs that.

Original issue: http://code.google.com/p/tigl/issues/detail?id=22

From [email protected] on August 26, 2011 14:13:21

use parent coordinate systems when building up parts

Original issue: http://code.google.com/p/tigl/issues/detail?id=40

From [email protected] on March 18, 2011 11:31:37

New function: getPoint on the overall fuselage and not only on basis of segments.

Original issue: http://code.google.com/p/tigl/issues/detail?id=19

From [email protected] on August 26, 2011 14:15:48

Wrong rotation of fuselage and wing profiles. They shouldn't turn from xy to xz by tigl

Original issue: http://code.google.com/p/tigl/issues/detail?id=42

From [email protected] on May 18, 2011 11:06:25

just compare the current version with the attached version to see the changes

Attachment: tiglwrapper_kh.py

Original issue: http://code.google.com/p/tigl/issues/detail?id=28

From [email protected] on November 25, 2011 11:06:34

In addition to the function "tiglFuselageWingSurfaceIntersectionPoint" it would be useful to have a function which returns a mean value for the wing-fuselage intersection. It seems best to me to calculate this point by getting the wing/fuselage intersection points at the leading edge and the trailing edge (middle between upper and lower side, if not identical) and then taking the middle between these two points ((x_LE + x_TE) / 2.); same for y and z.

I would suggest one function which gives back an x/y/z point, a second one which gives back the segment and the corresponding xi/eta on the wing and a third one like the second one, but on the fuselage.

Best regards,

Carsten

Original issue: http://code.google.com/p/tigl/issues/detail?id=50

From [email protected] on August 09, 2011 18:01:19

add algorithm checkboxes for the recent used wire algorithm

Original issue: http://code.google.com/p/tigl/issues/detail?id=30

From [email protected] on February 09, 2011 12:45:21

Support relative positioning of cpacs components

Original issue: http://code.google.com/p/tigl/issues/detail?id=12

From [email protected] on August 25, 2011 16:20:16

Implement a new function to re-read a configuration completly.

Original issue: http://code.google.com/p/tigl/issues/detail?id=38

From [email protected] on February 09, 2011 11:46:28

Add VTK export for complete geometry. Right now only fuselage and wing export are possible.

Original issue: http://code.google.com/p/tigl/issues/detail?id=4

From [email protected] on September 06, 2011 13:44:03

The are lots of API changes we need to think of.

Original issue: http://code.google.com/p/tigl/issues/detail?id=43

From [email protected] on July 29, 2011 09:57:57

A right click should give a popup menu with some options like erase element, change color, transparency and such.

Original issue: http://code.google.com/p/tigl/issues/detail?id=29

From [email protected] on April 27, 2011 16:01:03

Change getPoint functions for wings to use new way to determine eta. See picture below.

)

Attachment: 2011_04_20_CPACS eta-koordinate von componentsSegments.png

Original issue: http://code.google.com/p/tigl/issues/detail?id=23

From [email protected] on February 09, 2011 13:42:48

Cordline is not correct calculated. This could lead to wrong results in the tiglWingGetUpperPoint and tiglWingGetLowerPoint functions.

Original issue: http://code.google.com/p/tigl/issues/detail?id=15

From [email protected] on February 09, 2011 13:39:02

We need :

• axis on which the fuselage is rotated
• information how many degree the fuselage should be rotated

Original issue: http://code.google.com/p/tigl/issues/detail?id=14

From [email protected] on March 30, 2011 07:59:05

Bei dem beigefügten A320-artigen Datensatz mit symmetrischem VTP-Profil liefert mir die TIGL (ich glaube, letzte Version 2009) die folgenden Daten:
(Wing=3, Segment=1, Rel.Span=0., RelChord=0.875

-> tiglWingGetUpperPoint

yUpper=-0.079304600102030817

-> tiglWingGetLowerPoint

yLower=0.080959097782041758

yCamberLine=(yUpper+yLower)/2. müsste eigentlich 0. ergeben, tut es bei anderen Chord-Positionen auch ziemlich gut. Hier ist jedoch eine recht grosse Abweichung zu sehen, die mich bei dem exakt symmetrischen Profil etwas wundert. Kannst Du da bitte mal nachschauen, ob hier alles OK ist?

Stützstelle Rel. Chord yCamberLine Fehler
Profil
X 0. 0.00000000000000000
X 0.1 1.3877787807814457e-017
X 0.2 0.00000000000000000
X 0.25 0.00000000000000000
X 0.3 0.00000000000000000
0.35 -1.7301357044252619e-007 !!!
X 0.4 -2.7755575615628914e-017
X 0.5 0.00000000000000000
X 0.6 2.7755575615628914e-017
X 0.7 -2.7755575615628914e-017
0.75 -0.00019063426792897964 !!!
X 0.8 -5.5511151231257827e-017
0.825 0.00039044922838474966 !!!
0.85 0.00077287504227158826 !!!
0.875 0.00082724884000547061 !!!
X 0.9 1.3877787807814457e-017
X 0.95 6.9388939039072284e-018
X 1.0 0.00000000000000000

In der beigefügten Tabelle habe ich mal mehrere Punkte untersucht. Das Problem tritt offenbar immer zwischen den Stützstellen des Profils auf. Ich vermute also mal, dass hier der Spline zwischen den vorgegebenen Profilpunkten hin- und herschwingt.

Attachment: toolInput.xml

Original issue: http://code.google.com/p/tigl/issues/detail?id=20

From [email protected] on February 12, 2011 19:35:20

um die TIGL ansprechen zu können, braucht die TIGL ja die modelUID. Das bereitet mir immer ein paar Probleme. Die modelUID ist ein Parameter wie jeder andere bei mir. Und bei den Parametern kann (will) ich die Reihenfolge des Imports nicht explizit vorgeben. Wenn die Spannweite z.B. importiert werden soll, mache ich eine TIGL Instanz auf. Ist zu dem Zeitpunkt aber noch nicht die modelUID importiert klappt das natürlich nicht. Umgehen kann ich das Ganze mit ein paar Hotfixes.

Jetzt möchte ich TIXI und TIGL nur noch einmal öffnen und dann durch meine Componenten und Parameter durchreichen, um schneller zu werden. Das geht auch noch, aber nicht wirklich schön.

Da ich im InputMapping so oder so nur ein Model durchlasse, wäre die Frage, ob die TIGL, wenn sie nur ein Model findet, nicht einfach immer das eine Model öffnet? Ginge das? Ohne UID? Wäre ein Traum ;-)

Original issue: http://code.google.com/p/tigl/issues/detail?id=16

From [email protected] on August 26, 2011 14:14:34

Allow C0 - C2 steadiness grades for splining. The values should be defined (optional) in CPACS.

Original issue: http://code.google.com/p/tigl/issues/detail?id=41

From [email protected] on February 09, 2011 11:54:19

Add better logger to TIGL. It should be possible to have a logfile with detailed geometry/tigl informations.

Original issue: http://code.google.com/p/tigl/issues/detail?id=8

From [email protected] on March 17, 2011 11:08:43

TIGLViewer: possibillity to load a background picture and show in TIGLViewer. At best, this picture is dragable.

Original issue: http://code.google.com/p/tigl/issues/detail?id=18

From [email protected] on September 14, 2011 17:55:00

Remove some fuselage-getPoint functions. Over time there are many similar functions for GetPoint. The tiglGetPointTranslatedAngle does all we need.

Original issue: http://code.google.com/p/tigl/issues/detail?id=47

From [email protected] on May 18, 2011 11:03:59

just compare the current version with the attached version to see the changes

Attachment: tiglwrapper_kh.py

Original issue: http://code.google.com/p/tigl/issues/detail?id=27

From [email protected] on February 09, 2011 11:56:56

New functions for calculating the center of mass of volume bodies.

Original issue: http://code.google.com/p/tigl/issues/detail?id=11

From [email protected] on February 09, 2011 11:45:18

Add function that translates between segment and componentSegment.

Original issue: http://code.google.com/p/tigl/issues/detail?id=3

From [email protected] on August 09, 2011 18:53:44

Add a logger to the viewer.

Original issue: http://code.google.com/p/tigl/issues/detail?id=32

From [email protected] on February 09, 2011 12:47:11

Wings are now settled at point(0,0,0) and then transformed. Its necessary to hang a wing on a fuselage, so the origin is the fuselage instead of the coordinate origin.

Original issue: http://code.google.com/p/tigl/issues/detail?id=13

From [email protected] on February 09, 2011 11:40:39

Enable threading support with boost in TIGL. Opening a configuration could be much faster.

Be aware that threading of OCC functions may not possible :/

Original issue: http://code.google.com/p/tigl/issues/detail?id=1

From [email protected] on August 09, 2011 18:55:46

Add a live TIGL-console to the TIGLViewer

Original issue: http://code.google.com/p/tigl/issues/detail?id=33

From [email protected] on September 21, 2011 12:52:13

provide a console that could interactivly run tigl commands on the currently loaded data set and display results.

Original issue: http://code.google.com/p/tigl/issues/detail?id=48

From [email protected] on August 23, 2011 15:17:09

Provide external "getParent()" and "getChild()" functions.

Original issue: http://code.google.com/p/tigl/issues/detail?id=35

From [email protected] on February 28, 2011 13:32:11

Use TIXI to get the version of the CPACS data set. Implment a minumum and a maximum allowed cpacs version.

Original issue: http://code.google.com/p/tigl/issues/detail?id=17

From [email protected] on August 25, 2011 13:44:33

TIGLViewer: make coordinate systems viewable. Optionally they should be shown overlayed to the components.

Original issue: http://code.google.com/p/tigl/issues/detail?id=36

From [email protected] on February 09, 2011 11:47:28

Add material querying functions to TIGL.

Original issue: http://code.google.com/p/tigl/issues/detail?id=5

From [email protected] on February 09, 2011 11:43:10

Implement and test the implementation of the intersection calculation in TIGL. The algorithm were created before boolean fusing.

Original issue: http://code.google.com/p/tigl/issues/detail?id=2

From [email protected] on February 09, 2011 11:55:07

Enable TIGL to refresh when during runtime tixi changes the geometry. TIGL then has to re-read the geometry.

Original issue: http://code.google.com/p/tigl/issues/detail?id=9

From [email protected] on April 29, 2011 10:06:59

just a comma missing in

exportIGES
exportFusedWingFuselageIGES

Attachment: tiglwrapper.py

Original issue: http://code.google.com/p/tigl/issues/detail?id=26

From [email protected] on April 29, 2011 09:50:46

Function to get maximum ets for a given xsi.

Attachment: 2011_04_20_CPACS eta-koordinate von componentsSegments.png

Original issue: http://code.google.com/p/tigl/issues/detail?id=24

From [email protected] on September 09, 2011 10:16:44

Current Situation: The sweep angle parameter in the positioning does not lead to a rotation of the section in a wing. For fuselages the sweepangle DOES cause a rotation of the section.

For CPACS 2.0 no rotation of the section should occur. So the behavior for the fuselage should change.

Original issue: http://code.google.com/p/tigl/issues/detail?id=44

From [email protected] on August 25, 2011 16:15:00

TIGLViewer: update internal model when cpacs file has changed. Should be optional.

Original issue: http://code.google.com/p/tigl/issues/detail?id=37

From [email protected] on August 12, 2011 14:49:11

TIGL export functions should use UIDs instead of index.

Original issue: http://code.google.com/p/tigl/issues/detail?id=34

From [email protected] on February 09, 2011 11:51:24

Add support for symmetry informations in TIGL.
The normal routines should "know" that there is a symmetric component, but only when exporting to IGES/STL, the symmetric component should be generated/drawn.

Original issue: http://code.google.com/p/tigl/issues/detail?id=7

From [email protected] on February 09, 2011 11:49:49

Close wing profiles. Martin has made a suggestion.

Attachment: TIGL-Erweiterung-Schliessen von Profilen.pdf

Original issue: http://code.google.com/p/tigl/issues/detail?id=6

From [email protected] on February 09, 2011 11:56:06

Add new function to calculate the wetted area, additional to the surface area.

Original issue: http://code.google.com/p/tigl/issues/detail?id=10

From [email protected] on April 05, 2011 09:54:18

When calculating the area, respect differences detween upper and lower side of a wing. it should be possible to get only the upper-side-area or lower-side-area.

Original issue: http://code.google.com/p/tigl/issues/detail?id=21

From [email protected] on August 25, 2011 19:58:09

Alter transformation order.

1. scaling
2. rotation
3. translation

This should be equal in TIGL

Original issue: http://code.google.com/p/tigl/issues/detail?id=39

From [email protected] on October 13, 2011 15:05:37

Remove tiglAlgo functions.

Original issue: http://code.google.com/p/tigl/issues/detail?id=49

From [email protected] on September 12, 2011 21:03:14

Provide an GetPoint function that allows complete arrays of points to be calculated at once. This functions could use some more caching and might be much faster when calculating lots of points.

Original issue: http://code.google.com/p/tigl/issues/detail?id=45