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

ball-bouncing-uneven-street-HC-method.ipynb #3

Open
moorepants opened this issue May 20, 2023 · 0 comments
Open

ball-bouncing-uneven-street-HC-method.ipynb #3

moorepants opened this issue May 20, 2023 · 0 comments

Comments

@moorepants
Copy link
Member

From Peter:

I tried to simulatel a homogenious ball dropping on an uneven street.
I noticed this:

Here building the model is fast, less than 100,000 operations in the force vektor, but numerical calculation takes a long time.
This is mostly so, because I had to set the parameter max_step in ivp_solve to a very small value, otherwise the integration misses the points of impact.

From the ball's perspective, the street is concave. I modeled this by simply making R_2, the osculating radius of the street to be negative. (This radius is needed in the Hunt-Crossley formula, given in the article you gave me a while back)

  • I have no idea, whether whether this is stretching the formula beyod its range.
  • to get the effective R_2, I simply averaged the osculating radii in the X and Z direction.

Getting the speed right before the impact (this is needed in formula of the article, I guess in your lecture, you encorporated this dependency into the collision factor) was tricky.
I can only get it during the numerical integration, and it took me a while to get it rght - I hope.

I got a system of nonlinear equations to numerically determine the point of contact. This has to be solved at each step of the integration, slowing it down further.

The numerical integration seems very sensitive to initial conditions.
I also observed this:
Running a cell, say to get the energy of the system, an error message would come that an invalid value was encountered, but it still finished running.
When I simply ran it again, ther would be no error message...
This sort of thing makes me believe this simulation is quite a challenge to numerical integration - at least the way I set it up.

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

No branches or pull requests

1 participant