Skip to content

Airfoil implementation#47

Merged
giovaniceotto merged 5 commits intoRocketPy-Team:masterfrom
brunosorban:master
Oct 3, 2020
Merged

Airfoil implementation#47
giovaniceotto merged 5 commits intoRocketPy-Team:masterfrom
brunosorban:master

Conversation

@brunosorban
Copy link
Copy Markdown
Collaborator

The commit brings the implementation to use airfoiled fins simulation using a .csv file as input for the lift coefficient. At Flight, two minor changes were made. The first was to move the access to lift coefficient at Flight class to the end because Udot() function initializes without the compAttackAngle variable. Lift force calculus were also changed because cLift is the lift coefficient and not the lift coefficient derivative anymore (the name were also changed).

At Rocket class there are major changes. addNonecone(), addTail() and AddFins() don’t return a derivative anymore at aerodynamicSurfaces[1][1]. Now, at the position, an object of Function class is returned instead with a function that describes the component’s lift by attack angle. At nosecone and tail, it is a linear function with derivative clalpha. At fins, it either be a linear function using previous implementation of clalpha, or be a function of the .csv input linearly interpolated. Minor changes at evaluateStaticMargin() and allInfo() were also made to make those functions compatible with the new lift coefficient implementation.

brunosorban and others added 3 commits September 23, 2020 12:39
The commit brings the implementation to use airfoiled fins simulation using a .csv file as input for the lift coefficient. At flight, two minor changes were made. The first was to move the access to lift coefficient at Flight class to the end because Udot function initializes without the compAttackAngle variable. Lift force calculus were also changed because cLift is the lift coefficient and not the lift coefficient derivative anymore (the name were also changed).

At Rocket class there were major changes. addNonecone, addTail and AddFins don’t return a derivative anymore at aerodynamicSurfaces[1][1]. Now, at the position, an object of Function class is returned instead with the function that describes the component’s lift by attack angle. At nosecone and tail, it is a linear function with derivative clalpha. At fins, it either be a linear function using previous implementation of clalpha, or be a function of the .csv input linearly interpolated. Minor changes at evaluateStaticMargin and allInfo were also made to make those functions compatible with the new lift coefficient implementation.
pseudoD calculation was accidentally altered, but now is equal to the previous implementation.
The variable was accidentally stored at Rocket class twice. It can already be found at aerodynamicSurfaces, besides it only stored the value of last component added.
Returns
-------
cldata : Function
Object of the Function class. Contains tail's lift data.
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now the cldata isn't stored anymore, should I remove it from Returns?

There was a mistake in the way the  Normal force coefficient were being calculated. Now it considers the input of a 2D airfoil data and calculates the 3D parameters to the fins.
Copy link
Copy Markdown
Member

@giovaniceotto giovaniceotto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent!

@giovaniceotto giovaniceotto merged commit e7aed9c into RocketPy-Team:master Oct 3, 2020
Lucas-KB added a commit that referenced this pull request Feb 3, 2022
The airfoil implementation from pull request #47 was removed and
will be readded after careful review and reimplementation. The
current implementation is buggy at best. This commit fixes
issue #115.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants