Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update toolbox.adoc #117

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/toolboxes/modules/cfd/pages/toolbox.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -567,13 +567,18 @@ The user must define:


==== Forces
compute lift and drag
Compute lift and drag
Copy link
Member

Choose a reason for hiding this comment

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

drag and lift are misnamed, they would require having the direction of the flow and the direction of motion. Forces computes the surfacic forces (F_x, F_y) applied by the fluid to the object. It would be drag and lift if the flow or motion is aligned with the x-axis

Copy link
Member

Choose a reason for hiding this comment

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

@vincentchabannes probably a discussion on forces should be done in http://docs.feelpp.org/toolboxes/0.108/cfd/theory/


[source,json]
----
"Forces":["fsi-wall","fluid-cylinder"]
"Forces":["marker1","marker2"]
----
Where `markerX` are the markers of where we want to compute the forces. The results will be given in a csv file whith those columns :

- time
- drag_marker1
Copy link
Member

Choose a reason for hiding this comment

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

I think drag and lift should be removed here until we provide a direction of flow or motion

- lift_marker1
- idem with marker2...


=== Export user functions
Expand Down