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

Gh result elements #123

Merged
merged 5 commits into from
Jul 18, 2023
Merged

Gh result elements #123

merged 5 commits into from
Jul 18, 2023

Conversation

GerhardHippmann
Copy link
Collaborator

No description provided.

- Add abstract type AbstractResultElement.
- Generate list of result element objects during MBS initialization stored in scene.
- Call basic result element functions:
  * initializeResultElement(model, result) once before simulation.
  * evaluateResultElement(model, scene, result, time) in every communication point evaluation.
  * terminateResultElement(result) once after simulation.
- Add result element for MPR contact results.
- Function `getElasticContactPair` based on implementation of [email protected].
- Add comments and documentation.
- Add test model BouncingSphereContactResults.jl.
- Improve comments in elasticCollisionResponse.jl.
- Improve plot definitions in BouncingSphereContactResults.jl.
Comment on lines +75 to +76
(contactPair, converse) = getElasticContactPair(scene, result.object1, result.object2)
if !isnothing(contactPair)
Copy link
Member

Choose a reason for hiding this comment

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

Did you check with code_warntype if the type of contactPair can be evaluated during runtime? If not, the types of contactPair.results. ... must be defined.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks, should be okay now.

@AndreaNeumayr AndreaNeumayr merged commit 4f200c3 into main Jul 18, 2023
@AndreaNeumayr AndreaNeumayr deleted the gh_resultElements branch November 15, 2023 14:57
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