Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Static Equilibrium Extension#201

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
h2o-DS wants to merge5 commits intonumpy:main
base:main
Choose a base branch
Loading
fromh2o-DS:master
Open

Conversation

h2o-DS
Copy link
Contributor

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

@bsipoczbsipocz added the contentIssues relevant to tutorial content labelDec 21, 2023
Copy link
Member

@bsipoczbsipocz 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.



![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 noreation torques.
Define distance*a* as 3 meters. The ball joint at A can apply reaction forces, but noreaction 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 thehstack-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!

@guan404ming
Copy link
Member

@rossbar@h2o-DS hi, it seems like this PR have been inactive for a while, could I help with this?

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@rossbarrossbarrossbar left review comments

@bsipoczbsipoczbsipocz left review comments

Assignees
No one assigned
Labels
contentIssues relevant to tutorial content
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

5 participants
@h2o-DS@guan404ming@rossbar@bsipocz@dansim-umich

[8]ページ先頭

©2009-2025 Movatter.jp