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

Static Equilibrium Extension #201

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Static Equilibrium Extension #201

wants to merge 5 commits into from

Conversation

h2o-DS
Copy link
Contributor

@h2o-DS h2o-DS commented Dec 21, 2023

Fixed some formatting and extended the static equilibrium tutorial to include np.linalg.solve()

@bsipocz bsipocz added the content Issues relevant to tutorial content label Dec 21, 2023
Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

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

Note to content reviewer: The site-building is known to be broken (#200) and should not block this.

Go ahead with the review and merging using the circleCI artifact, we'll fix the CI separately in #199.

content/tutorial-static_equilibrium.md Show resolved Hide resolved


![image.png](_static/problem4.png)

Define distance *a* as 3 meters
Define distance *a* as 3 meters. The ball joint at A can apply reaction forces, but no reation torques.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Define distance *a* as 3 meters. The ball joint at A can apply reaction forces, but no reation torques.
Define distance *a* as 3 meters. The ball joint at A can apply reaction forces, but no reaction torques.



As before, start by defining the location of each relevant point as an array.
As before, start by defining the location of each relevant point as an array. For this problem vertical arrays are more convenient.
Copy link
Collaborator

Choose a reason for hiding this comment

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

This is not obvious - in fact, I'd argue that carrying around the extra dimension in the shape makes it more difficult to interpret the arrays. AFAICT, the main reason for doing so is so that the hstack-ing works when constructing the system matrix. Instead of introducing the extra dimension at the beginning of the processing, I'd vote for simply adding a "dummy" dimension for the hstack, i.e. something like:

unknown_forces = np.hstack((Unit_BD[:, np.newaxis], Unit_BE[:, np.newaxis], np.eye(3)))

Copy link
Collaborator

Choose a reason for hiding this comment

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

Just a quick ping on this one @h2o-DS - WDYT? If you don't have the bandwidth to make these updates but are not opposed to them, I'd be happy to push them up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issues relevant to tutorial content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants